Fubar512

I thought stuff like this only happens to Indiana Jones or Lara Croft: NEWARK, NJ, 31/07/09 Two sewer workers were swept away by a torrent of storm water underneath the streets of Newark this afternoon, authorities said. The incident occurred at 12th Avenue and 6th Street, around 4 p.m. when workers were realigning a sewer line underground , said Fire Chief Michael Lalor. Supervisors ordered the crew to get out when they heard a storm was coming, but two workers never received the news. When storm water flooded the space where the workers were located, they were washed away for a block before a net safely caught them, Lalor added. The workers, who were covered in solvent from their labors, were decontaminated and transported to University Hospital, Lalor said. They appeared to be in good condition, he added. Further information on the incident was not immediately available. I'm sure that they were covered in much more than "solvent", after that ride....

Did you even bother to read the knowledge base, like I've asked you?

It depends on which OS you're running. Either way it's all spelled out in the knowledge base, in detail.

Not since the SP3 days. Download my my 5 year old "megapack" and read the "mega readme" file

No FPS hit? I guess it's sort of hard to tell the difference between 9 and 10 FPS.

OK, a "frame buffer" is another way of defining graphics memory. So, 512 MB frame buffer = 512 MB of graphics memory. The minimum specs for the series is 128 MB, and that may not be enough to run anything other than the lowest settings. I'd say that with the latest patches or the lastest TW titles, 128 MB of video memory = minimal specs. 256 = low end. 512 MB = mid range. 896 -1024 MB = high end.

Did you recently load any software that may be making demands on the unit's shared memory? From experience, I can tell you, that given 2-3 GB of system memory, WoI or SF2 will use 1-1.25 GB of it. And,that's assuming that you have a separate video card, with a healthy (at least 512 MB) frame buffer. With an IGP that shares system memory, well, I can easily see it coming up short at some point.

It's a laptop, and the fact that uses an Intel IGP, means that it's not a gaming laptop. You may be asking a bit more of it, than it can deliver.

In my experience, a sub-par PSU simply causes reboots when it can't meet a video card's power demands. Usaully, it occurs only when the card's attempting to render 3D, or under DVD playback.

Judging by the screen shots, its definitely not a monitor issue. I've seen that sort of anomaly before...on a card that was dying. Check the cooling fan on your video card.

Then you're either not editing the right data.ini (the one called out in the Su-15.ini), or there's a typo somewhere.

Did you install the latest DirectX user runtime? http://www.microsoft.com/downloads/details...;displaylang=en

Doesn't need to be. AFAIK, you can treat it exactly as one would a radar display. I have a feeling that our avionics mod-god extraordinaire (Crusader), will chime in and set everyone straight as to what is, and what isn't possible, in this situation.

Which terrain, and did you modify that terrain? In short, it sounds as if you've got an airfield as the first item in that terrain's targets.ini file, which is a big no-no.

http://area51specialprojects.com/video/hav...ut_tactical.swf http://area51specialprojects.com/video/hav...t_technical.swf

Reference Area = Total wing surface area in square meters Reference Span = Wing span, in meters Reference Chord = Average wing chord....very impotant, as it helps average out the effects of the Xmac table between inner and outer wing surfaces.

The corner speed value, as it applies to a Strike Fighters model, is simply there for the benefit of the AI, and has little (if any) effect on the player's aircraft.

CLmax = Maximmum lift as a multiple, for the surface in question. The rest of the value definitions are as follows: CL0 Lift coefficient at zero angle of attack (AOA) CLa Lift coefficient due to AOA CD0 Zero-lift drag coefficient CDL Drag coefficient due to lift (induced drag effect) Cmq Pitching moment due to pitch rate (pitch damping) Cmad Pitching moment due to AOA rate (aero interaction between wings and horiz tail) Cyb Side force due to sideslip Cyp Side force due to roll rate Cyr Side force due to yaw rate Clb Roll moment due to sideslip Clp Roll moment due to roll rate (roll damping) Clr Roll moment due to yaw rate Cnb Yaw moment due to sideslip Cnp Yaw moment due to roll rate Cnr Yaw moment due to yaw rate (yaw damping) CLiftdc Lift due to control surface deflection CDdc Drag due to control surface deflection Cydc Side force due to control surface deflection Cldc Roll moment due to control surface deflection Cmdc Pitch moment due to control surface deflection Cndc Yaw moment due to control surface deflection DeltaStallAlpha Increase in max angle-of-attack before stall Xac X-location of aerodynamic center So what's involved in properly defining values for an FM? The following should provide some insight: http://adg.stanford.edu/aa241/highlift/clmaxest.html

Its not that simple. Flight models are almost algabraic in that what you do to one value, must be offset by the appropraite changes to another. That being said, the default Thirdwire model is pretty accurate, with the exception of its stall values. The '21 should begin to experience the onset of stall at between 17 and 20 degrees of AoA. Thus: Inner Wing Panel Values (L & R): CLmax=0.2915 AlphaStall=19.00 AlphaMax=22.00 AlphaDepart=28.00 Outer Wing Panel Values (L & R): CLmax=0.2054 AlphaStall=17.00 AlphaMax=21.00 AlphaDepart=26.00 These will ensure that a '21, under hard settings, will stall when it should, assusming that you're flying above its rated, flaps up stall speed. Just use the AoA guage in the cockpit to verify this.

What video card? Have you recently updated the display driver?

Open up your options.ini file, and make sure it's using 1280x800.

That feature's been there from the onset. I once recall seeing a lone MiG-21 flying alone, after my flight intercepted a group of them, I was out of heaters, and out of gun ammo. As I flew alongside, I noticed that it lacked a canopy...and that was back in the SP2 days.

You need to ensure that your aspect ratio is set to 'Wide Screen Display, 16 x10". Secondly, in the Graphics setting of your flightengine.ini, set the aspect ratio to "1.6" (by default, it'll still show 1.333, even if you have the aspect ratio set correctly in your options screen). The second one should not be necessary, though I believe that I've noticed that the game runs smoother if you perform that edit.

He set the projectiles up as missiles.

Helmut, The AI will let know when you're approaching bingo fuel, by saying to you "Request you check joker" :yes: