VonS

Thank you for these many variations on the Elephant Crawford - I will copy over the changes to my modified FMs for the Elephants as soon as I find time. For those who have my FM realism pack loaded up, for FE2, by the way, the working fuel pump prop. mod that Crawford discovered has already been included on the FM-modded Sopwith Camel variants, a while back, as well as on the FM-modded Elephants - but I will eventually include Crawford's latest modifications to guns and cameras, to the Elephants, too. Great stuff and glad to see this thread revived. Von S

The best thing to do therefore is to make a copy of your user directory/folders for FE2 - store them somewhere safe - and then start FE2 without the user directory in its expected location. This will "build up" a stock user folder. Then, some quick flying to check if exhaust effects are present for such aircraft as the SPAD and Fokk. Dr.1 that come stock in FE2 - this will rule out any possible corruption with effects/files in your custom user directory for FE2. Hopefully we will be able to narrow down where the problem is. Keep us posted. Von S

The only other thing I can think of and that might help is to compare the relevant emitters listed in the particlesystem.ini file that resides in "Flight," with comparable emitter ini files that reside in "Effects." In the TW sims, as far as I remember, individual emitter ini files in "Effects" override the same emitter calls listed in particlesys - unless such ini files are missing from Effects - then the calls in particlesys take over. In my case, I don't have individual exhaust emitter inis in Effects, but I have some relevant calls in particlesys (also good is to check some of the smoke effects in particlesys too) - here's what I have in particlesys and that might be relevant checking over in your installs, if you're missing engine exhaust effects: [ExhaustMaterial] EffectShaderName=effectLightLevel.fx -----> forgot to include this previously (since I incorrectly copied over my old particlesys file for dx9 only) DepthBufferCheck=TRUE DepthBufferWrite=FALSE IgnoreRenderOrder=FALSE AlphaTestEnabled=FALSE LightEnabled=FALSE UseLightLevel=TRUE SpecularEnabled=FALSE EmissiveEnabled=FALSE AmbientColor=1.000000,1.000000,1.000000,1.000000 DiffuseColor=1.000000,1.000000,1.000000,1.000000 ZBufferOffset=0.000000 PriorityLevel=3 BlendOp=BLEND_SRC_ALPHA NumTextureStages=1 TextureStage[01].TextureName=smoke.tga TextureStage[01].MipMap=FALSE TextureStage[01].FilterEnabled=TRUE TextureStage[01].StageColorOp=TEXTURE_MODULATE_DIFFUSE TextureStage[01].StageAlphaOp=TEXTURE_MODULATE_DIFFUSE [EmitterType002] Name=DirtyExhaustEmitter EmissionType=POINT_EMITTER UpdateType=NON_MOVING MaxVisibleDistance=18000.000000 EmissionRate=0.2500000 ParticleUpdateType=RANDOM_MOVING ParticleRenderType=CONNECTED_SPRITE ParticleLifeTime=20.000000 ParticleWeight=0.00000 ParticleWindFactor=0.5 ParticleColorTableType=TABLE ParticleColor[01].Time=0.000000 ParticleColor[01].Value=0.400000,0.400000,0.400000,0.000000 ParticleColor[02].Time=0.008000 ParticleColor[02].Value=0.400000,0.400000,0.400000,0.200000 ParticleColor[03].Time=0.125000 ParticleColor[03].Value=0.500000,0.500000,0.500000,0.100000 ParticleColor[04].Time=1.000000 ParticleColor[04].Value=0.600000,0.600000,0.600000,0.000000 ParticleSizeTableType=TABLE ParticleSize[01].Time=0.000000 ParticleSize[01].Value=0.800000 ParticleSize[02].Time=0.01000 ParticleSize[02].Value=0.800000 ParticleSize[03].Time=0.500000 ParticleSize[03].Value=40.000000 ParticleSize[04].Time=1.000000 ParticleSize[04].Value=80.000000 TextureMaterial=SmokeTrailMaterial [EmitterType003] Name=CleanExhaustEmitter EmissionType=POINT_EMITTER UpdateType=NON_MOVING MaxVisibleDistance=8000.000000 EmissionRate=0.5000000 ParticleUpdateType=RANDOM_MOVING ParticleRenderType=CONNECTED_SPRITE ParticleLifeTime=6.000000 ParticleWeight=0.00000 ParticleWindFactor=0.9 ParticleColorTableType=TABLE ParticleColor[01].Time=0.000000 ParticleColor[01].Value=0.400000,0.400000,0.400000,0.000000 ParticleColor[02].Time=0.016000 ParticleColor[02].Value=0.400000,0.400000,0.400000,0.100000 ParticleColor[03].Time=0.250000 ParticleColor[03].Value=0.500000,0.500000,0.500000,0.050000 ParticleColor[04].Time=1.000000 ParticleColor[04].Value=0.600000,0.600000,0.600000,0.000000 ParticleSizeTableType=TABLE ParticleSize[01].Time=0.000000 ParticleSize[01].Value=0.800000 ParticleSize[02].Time=0.005000 ParticleSize[02].Value=0.400000 ParticleSize[03].Time=0.250000 ParticleSize[03].Value=10.000000 ParticleSize[04].Time=0.500000 ParticleSize[04].Value=20.000000 TextureMaterial=SmokeTrailMaterial Also, in the options.ini file, don't forget to toggle the following two values if using dx10 calls/shaders, such as available in the relevant folders of my FM update pack: UseAdvancedShaders=1 ForceDX9=FALSE Von S EDIT: Correct shader statement now included; a dx10-friendly particlesys file is included in the FM update pack, by the way.

I've uploaded a couple of short FE2 vids at this link, embedded on my RB3D on a Mac website. There is a subtle exhaust effect from the rotary on the M-S type N in one of the clips (no exhaust on the Nieup. 17 in the other clip, since it's using the rotaryexhaustemitter entry). Apologies beforehand to all for the slight vid. quality degradation - originally recorded in game bar on Win10, then slightly compressed when converted to H.264 format in VLC Player (yes VLC Player can do compressing/conversion) - and then uploaded. Several updated effects files that are now linked to and/or include correct "dx10" calls can be found in relevant folders in the ver. 9.9 FM update pack, by the way. If necessary I can double-check the files more specifically over the next couple of days and will post back if I find any helpful info. (currently trying to get the awful internal padlock view to work properly in my IL2-1946 vpmodpack install - unfortunately it doesn't seem to glue itself permanently to the chosen target - something that only FE2 and WOFF seem to be good at - and ROF so-so). EDIT: RB3D on a Mac website no longer online - no time to maintain that site anymore since I've moved over full time to FE2 and WOFF for my WWI flight sim. needs. Von S

I recommend tinkering with the following three entries for "ExhaustEmitterName" in the data inis of aircraft, installed in FE2: CleanExhaustEmitter (misleading name since this is the "dirtiest" emitter in FE2, gives a wide, thin stretch of greyish smoke behind the aircraft) InlineExhaustEmitter (usually gives a thin, white stream of smoke, as if from an exhaust stack, especially good for inline engines and a favorite of Geezer's if I remember correctly) RotaryExhaustEmitter (basically gives no exhaust effect) (If I can dig up my old, long post for correct order of install effects in FE2...I will re-link it here.) EDIT: Here is the link (to an old post) that suggests a good order for effects installation in FE2 - if certain effects are missing, etc. (https://combatace.com/forums/topic/88700-fe2-bad-framerates/?tab=comments#comment-716531). Von S

One can never have enough WWI sims, but this one always calls me back - great sensation of flight and much more exciting than ROF, I think. Representative screenies below. (Hope to tweak the FM for the Snipe and Stephen's Halb. CL.II soon - was busy with some WOFF fm tweaks over the last month or so.) Happy flying gents', Von S

Probably a discrepancy between the screen resolution and the FE2 sim resolution - that's causing such stretching - specifically an "aspect ratio" problem. I recommend the following tweak, if possible: Run screen resolution at your default widescreen setting of 2560 x 1080 but open up the "options.ini" file located in your FE2 user folder (in the main level of the user folder) - and under the "GraphicsOptions" section of that file, set the following numbers, and don't forget to save settings: DisplayWidth=2560 DisplayHeight=1080 DisplayDepth=32 AspectRatio=2.370370 The trick is to set the correct aspect ratio (the one above is for resolutions of 2560 x 1080). For resolutions of 1920 x 1080, also 1600 x 900 in the options.ini file, use an aspect ratio of 1.777778 (avoid setting your monitor's resolution to 1920 x 1080 or 1600 x 900, however, since everything will remain stretched because of the wrong aspect ratio then involved for your size of monitor - only fiddle with aspect ratios within the options.ini file - but I think the most natural settings for your FE2 install, in options.ini, are the ones suggested above since then you can leave your monitor's resolution at its best/default settings too). In short, always maintain the same aspect ratios between the monitor's resolution that has been chosen and the in-sim resolution set in the options.ini file, and also make sure that the aspect ratio in options.ini corresponds with the displaywidth and displayheight values set there. Formula for getting aspect ratios is displaywidth divided by displayheight, rounded to the sixth decimal place in FE2 (and SF2). Happy flying, Von S

The only thing I can think of, which I may have mentioned in the previous posts, is to run the FE exe in Win7 compatibility mode - although my advice applies to FE2 (and SF2). Hopefully someone who runs the 1st gen. of FE on Win10 will be able to give some suggestions. Von S

Yes the un-jam command is good for our sometimes unreliable machine guns in FE2 - also good is the reload command for the Hotchkiss, Lewis, etc., when exchanging drums or belts. In FE2 it adds rather than takes away from the realism. I'll have to check out that "re-arm" command one of these days though - dropping down to the 'drome, re-arming with a fresh 200-ammo belt on the Eindecker, and going up again opens all sorts of possibilities (although it might not be realistic in FE2, given primitive maintenance and overhaul rates, especially for rotary engines, in the good old days). Von S

There's a fine Deperdussin Racer of 1913 that I remember seeing several years ago, in FlightGear - would be nice to import that one into FE2. Also the Santos-Dumont Demoiselle comes to mind too. Happy flying, Von S

Hopefully some of our SF1/SF2 specialists will have constructive advice regarding lods/framerates/loadouts etc. I'm assuming that it's possible to carry over some aircraft from SF2 to SF1, in the same way that some of our FE2 flyers have managed to get aircraft from FE2 running in FE1. Crawford and others may have more info. on this since they fly some second-gen. aircraft in the first-gen. TW sims. I wouldn't know anything about that since I've done the opposite - carried over some data inis and aircraft that were made for FE1 into FE2, and also carried over some aircraft from FE2 to SF2. To chat privately with CombatAce members, you should be able to click on the message tab/option near the top of their profiles, unless they've turned off the private messaging feature. Von S

I've heard good things about the DBW (and CUPS) mods - one of these days I might try installing those since I can then try out the standalone WW1 modpacks for IL2-1946. BAT is thorough but from what I've read you have to install all-or-nothing with it (DBW/CUPS was more modular since you could get only the era you want for it). If I find some free time I might try out WW1 just for kicks in IL2-1946. There is a much better Pfalz (made by Geezer) and available on pages 17 and 18 of the "New Aircraft" thread here on the FE2 forums (direct links to the Pfalzes, and skins for them, follow below): https://combatace.com/forums/topic/91066-new-aircraft/?page=17&tab=comments#comment-746182 https://combatace.com/forums/topic/91066-new-aircraft/?page=18&tab=comments#comment-747022 Also check over the other great aircraft models that Geezer made, and that are available on those two pages of that thread (freely available and they work well in FE2). Happy flying, Von S

IL2-1946 works fine, providing you go into the control panels settings first (for Win10), and, under the "system" settings, make sure to select "DEP enabled for essential programs only" or something to that effect, then reboot, and "46" should fly fine. Also recommended is running the IL2 exe, also the IL2 launcher exe (if you are running one of the modpacks), in Win7 compatibility mode. Speaking of modding packs, I recommend the "VP Modpack" since it seems to have the best graphics of the various modpacks available - yes, there is "BAT" but that thing is huge, and (in my humble opinion) WW1 flight fans are better off looking into running fully modded FE2, modded ROF, and of course the wonderful WOFF (ultimate and platinum editions). Happy flying, Von S P.S. Disable "complex engine management" and "wing flutter" in the IL2-46 sim menu for more flight physics realism, since those two don't seem to be modeled all that well - and besides, the AI is then less at an "uber" advantage - and more competitive with you.

I can't comment specifically on FE1/gold, but I'm sure some flyers of FE1 will pitch in soon with helpful tips. I wouldn't be surprised if similar tips that work for FE2 will also work well for FE1. FE2, for example, works fine on Win10 - I do however recommend running it, and SF2, in Win7 compatibility mode. Also, for FE2, I recommend checking over my post linked to below, in case you get poor frame rates in Win10: https://combatace.com/forums/topic/92932-windows-10/?tab=comments#comment-752183 Happy flying, Von S

I have ave. fps in IL2-1946 of about 100 - graphics are acceptable with the vp modpack installed - but as indicated in one of my other posts here on the FE2 threads, I don't like the padlock views in IL2-1946 as much as in the ThirdWire and OBD sims. ROF padlock views are so-so. In "46" on the other hand, once a locked target is out of your front field of view for a few seconds, padlock automatically disengages - and then it's mouse-view or external aircraft-to-target view before you find the bandit again (cumbersome and sometimes it breaks immersion). Also I find high-density forests strange in "46" - with those spring coil effects, and then a downed aircraft disappears below the "spring-coil" forest ceiling. Maybe I'm just too nit-picky but I prefer how forests are done in the TW and OBD sims (better than in ROF). One thing I'll give to "46" is that there's subtle movement of trees (very subtle but can be spotted, would be nice to introduce such an effect into the TW/OBD sims). Also, feel free to turn off "complex engine management" and "wing flutter" in "46" since they don't seem to be modeled correctly - you'll get more FM realism with those options turned off. Happy flying, Von S

Yes, even though I'm a Mac guy, I have a soft spot for Win7 (Ultimate ed. in my case) - smooth-sailing system and very tweakable too - as I mentioned in my previous posts, I think Win7 is/was the high point of Windows operating systems. I now run FE2/SF2/WOFF/WOTR/ROF/IL2-1946 (vp modpack) on Windows 10 Pro (ver. 1809) on the BootCamp side of my Mac Pro - so far it's been a good system since I've tried to lock down/avoid excessive updates...chose to postpone big updates by 365 days and security updates by one month. I don't know if I'll upgrade to ver. 1909 anytime soon, in BootCamp, since my primary use for Win10 is simming and FM tweaking - my work stuff is on the Mac side. The primary deciding factors will be: a) if ver. 1909 has fps in the sims as good as, if not better, than in ver. 1809 of Win10 - lower fps will be a no-go b) if it will be even possible to do a "normal" upgrade in BootCamp from one ver. of Win10 to another I might as well expand this post slightly since it may be of use to Windows users, and those interested in sticking with Windows 7 for the next few (more) years. If you want to remain on a "fixed" ver. of Win10 or if you want to maintain Win7 on your rigs, not only for ThirdWire sim compatibility but other reasons too, I recommend: 1. use a browser other than IE or Edge (I like Firefox loaded up with AdBlockPlus and PrivacyBadger - also good is the Pale Moon Browser, a fork of the slightly older Firefox before Quantum, with the AdBlockLatitude plugin) 2. for email, use a desktop program that doesn't support html - I like Sylpheed (not Sylpheed Claws but the plain old Sylpheed - works well enough and html emails can easily be opened in your web browser if you click on such emails) 3. on Win7, install MSE (Microsoft Security Essentials) and set it to work as your malware "wall," instead of the old Windows Defender that comes with Win7, since definitions in the old Defender only go up to about 2012 - on Win10, the baked-in newer ver. of Defender is fine as your malware wall 4. look into downloading "ClamWin" (free, barebones antivirus program - it can be scheduled to run weekly, daily, etc. - has no "real-time" scanning but I like that since it doesn't bog down system resources) - ClamWin is simply a graphical front end to ClamAV and is updated regularly 5. on both Win10 and Win7, go into the "system" settings in the control panels window, and make sure to "enable DEP for all programs" and reboot to take effect (you will have to toggle this to "DEP for essential programs only" if you want to run IL2-1946 however) 6. set up a "standard user" account on Win7 and use that for regular computing, instead of an administrative account (a good tip for Win10 as well, if you are running an unsupported ver. of Win10) 7. for Win7 only, since official support has ended, download and install what's referred to as the "0patch" app - this patches vulnerabilities on the fly, only while you are running vulnerable programs, on Win7, and comes in a free edition - seems legit. from what I've been able to test on my Win7 installs (0patch is available at the following link https://0patch.com/) 8. download OSArmor for Win7 (and Win10), and enable it using the default settings that are already selected in it - the program blocks various connections to your computer (available here https://www.novirusthanks.org/products/osarmor/) 9. go into your firewall settings and select "block all incoming connections" for all profiles available, including public, home, etc. 10. go into your wireless/ethernet adapter settings (available under the advanced tab in "networking"), and disable, in the properties section of the adapter, "IPv6," if you're not using it and only relying on IPv4 for network connections Happy flying (and computing), Von S

Tinkering further with the ver. 9.9 FM update pack and decided to post a few more pics caught during testing. Von S Testing out "STOL" characteristics with the Nieu. 17 in the Italian theater Pleased to see that I was eventually blown off of the hill by the wind, and went for a short glide (wind effects really do work in FE2 but are best when treated subtly, light wind, occasional gusts, etc.) Couldn't resist doing some sight-seeing again with gTerl's maps Making sure that post-damage effects work well (I can be spotted in the far background on the pic.) One of the best dogfights I've ever had in any sim (the AI on this earlier Austrian Alby. was superb, we both got shots into one another but the fight was inconclusive, lasted for about 20 mins. I think) The Spad 13 200hp can do limited turn fighting, but keep your speed up and take advantage of acceleration in dives (good turn speeds are around 160-170 kph) - also good is rudder and opposite aileron for tighter turns and skids but watch your speed And we went our separate ways eventually (the Spad 200 hp can slowly outrun this variant of the Alb. D.III)

I set up my single missions using the in-sim menu in FE2 - the great thing about it is that (as in WW1) you don't know what type of enemy aircraft you will encounter, or the number of aircraft - although congestion settings can be controlled to some extent via the in-sim menu, and further congestion files (the "formation.ini" file that goes into the Flight folder of the user folder for FE2 - some of those are included with my FM update packs for FE2). For recommended flight congestion settings in the in-sim menu, for those who like to fly historically, I recommend point no. 7 under my "Rules for DiD Style Single Missions in FE2" available at the link below (where I attempted to imitate the DiD campaigns/missions that are constantly going on at the WOFF forum on the SimHQ website - in my opinion FE2 is excellent for DiD, "dead is dead," style missions and campaigns): https://combatace.com/forums/topic/92423-did-style-single-missions-for-fe2/ Happy flying, Von S

For aircraft that seem to be missing engine sounds (if you are using the data inis from my FM update packs), I recommend the two links called "List of My Engine Sound Names and Original Engine Sound Names" and "Engine Sounds Pack," from the following post: https://combatace.com/forums/topic/91337-problems-with-my-fe2/?tab=comments#comment-738368 In terms of Caporetto campaign questions, hopefully someone with more experience with campaigns will pitch in with helpful info. (I have the terrain installed but usually fly single missions over it). Von S

Also, it doesn't hurt to run SF2 (and FE2) in Win7 compatibility mode too - on Win10. I run them that way and I've had no CTDs at all. Same advice applies to the OBD sims (WOFF/WOTR), as well as IL2-1946.** For ROF I haven't noticed any benefits to running in Win7 comp. mode. **For IL2-1946, don't forget also to enable "DEP protection" only for essential programs (in the relevant setting in the control panels, "system"), otherwise it doesn't load on Win10. Happy flying, Von S

Here's another looker I've been tweaking the FM for - will include this one also with an update to the early WW2 SF2 FM package. An "early" Tony - Ki-60 and/or very early Ki-61 - model is by A-team and it took a while to rework the FM but I like the results - top speed about 560 kph @ 4500 m alt. Best climb around 350 kph, 13 m/s or so. Ailerons are okay above about 300 kph but horribly ineffective below 250 kph. Rudder is ok. Also avoid loops if your speed is less than about 300 kph, tends to spin out. Other peculiarities on the type - tends to "sink" if flying too slowly - rather than entering a typical stall. No wonder pilots didn't really like the Ki-60 prototypes and early Ki-61 batch, compared to the more pleasant Ki-43 ("Army Zero"). Having said that, it's a fast type for the early war and works just fine if you avoid tight dogfights with it. Good for slash-and-dash attacks. Von S

Busy with FM tweaks for Stephen's Polikarpov I-15 (gull wing variant) to fit it into the early WW2 SF2 package. Top speed around 350 kph at 3000 m alt. (with the earlier M22 engine variant), very maneuverable and good climb rate of about 15 m/s if you maintain about 200 kph. Also improved environsys and flightengine ini files - will include the atmospherics tweaks either with my ver. 9.9 FM update pack for FE2 or the early WW2 SF2 package. Next up is an early Ki-61 or the prototype Ki-60, also for the early WW2 package, then to circle back to further FE2 tweaks. (The PTO theater used a small number of gull-wing I-15's as trainers so it doesn't hurt to include them since we're missing the 15bis variant.) Von S

Hello gents', The relevant info. I have in the data ini for the "Spider" (located in the ver. 9.7 folder of my update pack, see the eastern front and Italian front folders) - is as follows: GunTypeName=8MM_SCHWARZLOSE_M0712unsync InputName=FIRE_PRIMARY_GUN GunGroup=1 MuzzlePosition=0.00,1.19,1.215 LightPosition=0.00,1.19,1.215 AimAngles=0.0,4.0,-0.1 MaxAmmo=250 EjectShells=TRUE I've been liberal with the max ammo setting (250) but may reduce this further to about 150-200. Also take note that the rate of fire is slightly faster on the unsynchronized than the early synchronized versions of the 07/12 Schwarzlose. I've therefore linked the Spider's gun type name with the un-synced variant of the early Schwarzlose. The relevant folder can be found in the "Guns" folder available in the larger ver. 9.5 consolidated update pack folder that's also available in the ver. 9.7 download. My general ini files for FE2 have shadows set to false on my rig, to preserve frame rates, but I will eventually get to setting them to "medium" - eventually - in SF2 I have them at medium settings and they work fine on the Mac Pro (2013). Hopefully setting them to medium in FE2 won't shave off too many fps. Happy flying, Von S

Yes indeed, the TW sims have some of the best views in the business (padlock, hat switches, panoramic views, etc.) - I'm always impressed by the precision of the padlock view in dogfights in both FE2 and also in the high-speed prop aircraft in my 40s/50s SF2 installs - a great sense of immersion and neck craning to see your opponent. ROF and WOFF/WOTR also have good view systems but the views/toggling only feels fully organic (and the most precise) to me in the TW sims. Also picked up IL2-1946 for two dollars recently on Steam, largely as a novelty, and while the graphics look acceptable for a mid-2000s sim (with the "vp modpack" installed) - the padlock view leaves something to be desired and is often hit-or-miss, while toggling between cockpit and external aircraft-to-target view during dogfights really breaks immersion in that sim. Obligatory FE2 screenies below. Von S

More testing of the ver. 9.9 FM update pack...FE2 always delivers with tight, white-knuckle dogfights, and with the 4GB patch applied to the FE2 exe, I think I'm getting even smoother fps and better viewing distances. Representative pics. below - a rare encounter with some single-bay Fokker D.II (B.II) variants used by Austria, Sept. 1916. (Have now removed armor from the pilot and nose area on the B.II, for more realistic damage chances - didn't spot that before today's flights.) Von S Looks like something out of the books. Enjoying the better mesh views. Let's go up higher and admire the maps. Time for some higher-alt. action. Managed to put a few shots into this fellow. He then went into a spin and never recovered (great variety of AI response). Had part of a wing knocked off by this other fellow who came too close - but I still had some flying surfaces left for another try (didn't end successfully).