Tolwyn

It's FAKE! (Now will Jeff Gordon pick ME up and take me for an awesome ride like that??)

Had fun giving this mission my best go. http://dangerdogz.com/forums/files/file/748-me-163-scramble-%E2%80%94-tolwyns-attempt/ This is the track.

Oh. I thought the triangle-ish clouds was from the edges. My polygon LOD theory I think isn't the answer, then.

If you don't see a decrease in performance using Antialiasing, then, of course, it's personal taste. And using nvidia control panel is the way to change your settings AS LONG as the extensions are enabled in conf.ini (do NOT use il2setup anymore, it's completely out of date). I find turning it off helps me not only in performance, but also seeing dots in the distance. In doing more research on the cloud issue, I've determined the following and I'll break it down very high-level. The game, to save CPU and GPU cycles will render polyobs with less detail that the game thinks you cannot SEE. Clouds are static objects in each map. They aren't dymanic. They are always the same. So their rendering algorhythm is likely static for programmatic reason. How they are drawn/rendered is by what the game assumes you can literally see. This is known as LOD. Polygon Face Occlusion, Hidden Surface Determination, etc. Now that being said, as you pan, clouds drawn in front of you that look normal, will likely "shift" into a lower LOD and looking full right, the clouds that were at your 12 o'clock that looked nice and fluffy, SHOULD look pointy and silly. Kinda like how you can focus on a plane in external view and zoom (move camera) slowly away from it, the LOD will change. In some cases, the LOD2, LOD3 for planes (the YAK comes to mind) actually appear LARGER than their LOD1 and LOD0 (highest detail) counterparts. You COULD try to force nvidia to a fixed LOD bias ( http://www.tweakguides.com/NVFORCE_6.html ) and see if that helps. Texture Filtering - Negative LOD Bias: LOD is the Level of Detail, and in some games you can alter the LOD Bias using various settings to sharpen details on screen. In such cases, you should set this setting to Allow, however note that altering LOD Bias can introduce aliasing (jaggedness to lines and edges) and shimmering. Since Anisotropic Filtering can also improve the sharpness of images without adding to aliasing, I recommend that you change this setting to Clamp for games in which you use any level of Anisotropic Filtering to give you better overall image quality. So, at the original code's max FOV of about 105 to 110 degrees, it assumes you can't see clouds outside of this range and will render them with less detail. YOU SHOULD SEE clouds in front of you, and within the 110 degrees normally... even if you use 3 monitors; but on the edges, the clouds will/may take on a more "simplistic" shape to save rendering work through the OpenGL API (and likely DirectX as well). Since you likely make up a small percentage of people using a 3rd-party application to render the game at a HUGE FOV across 3 monitors, they likely aren't going to address it (that's not saying you're a bad person, it's just not a priority... well, you may smell funny, but we still love you). Since I don't have access to the sourcecode, this is an pretty good educated guess as to why CLOUDS are rendered with the funkiness as they are. You can try to tweak with the SKY settings or whatever controls cloud detail, but my guess is each setting will still be slaved to the rendering "corner cutting".

Hi. I'm Tolwyn. I fly with you guys on Tuesdays and Thursdays.

Well, make a backup of your conf.ini and try these settings in the opengl section. Changes in Bold.

Yup, I have all those XWing Alliance model upgrades!

Janes F/A 18 MSFS 2004 (FS9) Doom (yes, Doom), Quake, Quake2, Quake3 Egosoft X2 TIE Fighter X-Wing Police Quest (currently)

So, my buddy Surly and I started these "Barf-o-Missions." Basically, they are "how fast can you make a mission" or, you have 1 hour to make a complete mission. They make no historical sense at all (or don't have to). Mine generally don't. Anyhoo... My Panther / B29 (yes, I changed it) mission, I discovered a few things. Taxi to take off (AI). Set the delay on the first taxi waypoint. You can't (shouldn't) use the STARTTIME parameter as they will form up on the runway, then spawn on the Stationary Aircraft when the STARTTIME value is reached. Expert Mode introduces some (non realistic) ground control weirdness (at least on carriers) when trying to get to the catapult. Augh. If you have rudder pedals, you're fine. If you don't, it's a challenge.

[DGEN] ; Remove ";" to activate. ; ";" is Forgotten Battle's Comment Character ; New as of version ; NoBadWeather NoAirfieldHighlight=0 AirIntensity=Medium ; Valid entries are: Low, Medium, High (Medium is default) GroundIntensity=Medium ; Valid entries are: Low, Medium, High (Medium is default) MissionDistance=125 ; Valid entries are any whole number between 0 and 300 RandomFlights=4 ; Valid entries are any whole number between 1 and 5 (3 is default) CampaignLength=Long ; Valid entries are: VeryShort, Short, Medium, Long, VeryLong (VeryLong is default) CampaignAI=Normal ; Valid entries are: Easy, Normal, Hard (Default is Normal) CampaignMissions=Normal ; Valid entries are: Easy, Normal, Hard (Default is Normal) ; BOE Specific Start ; ; MaxFLAK=50 ; Valid entries are any whole number between 0 and 100 (Default is 10) NoActiveFrontline=0 ; Comment out with a ; preceeding to disable ; ; BOE Specific End ; AEP Specific Follows ; MaxBomberSkill=3 ; Valid entries are any whole number between 0 and 3. (Unknown Default) ; Pacific Fighters Begin ; OperationVictory=100 OperationDefeat=-100 WarVictory=2000 WarDefeat=-2000 ; UseParachutes UseParkedPlanes=1 HistoricalRanks=1 SlowFire=10.0 ; ; Pacific Fighters End

I'm sorry. That's my bad. I have this forum as a link, and didn't even THINK about it being in the wrong spot. Sorry, guys. My bad. Please feel free to move it.

I assigned only two new commands. Open Bombay doors and Full screen map Optional: Reticle brightness There might be one or two more...

In all the usual locations. I bring it up because I've created a MOD that will bring you back to 4.11.1, if interested. All you really have to backup is: conf.ini (there are new entries with 4.12) users folder (your own, because there are many new key commands (they really won't interfere with anything, but it's always an anal-retentive thing to do) So, from 4.11.1, backup the following to restore 4.11.1 functionality: DT.dll fb_3do24.SFS fb_maps18.SFS files.SFS your 4.11.1 conf.ini * your 4.11.1 users folder ** * New 4.12 entries will be ignored by 4.11.1, but I'm anal retentive. ** New 4.12 key commands will be ignored by 4.11.1, but I'm anal retentive. The other new SFS files, etc., are ignored by the 4.11.1 engine, they can be left in-place... To restore back to 4.12, just reverse the files replaced above.