Droning_On

the G version of Bf109 sounds like an 'easier' solution tbh....... even if just AI

OK let me set the senario first. Huge WW2 dogfight in a single player mission (Reflected's The Big Show) 24 spits vs 20+ FW190 and we're defending LOTs of B19s so lots of assets in the air (not that that matters) After 5 or so minutes I reform my 3 spit wingmen as we seem to be a few miles from the main furball. A single FW190 meanders over our direction and I set the 3 AI spits to attack the 190, and off they go all happily filling him full of holes. Now, you would expect the 190, looking now more like a colander than a WW2 fighter, with 3 spits taking pot shots each to be ULTRA MEGA defensive, but no. It goes out its way to do a lazy loop around in my direction, oblivious to the spits behind and trys to get on my tail...... 3 spits STILL punching holes in it ..... ??? WHY? Some will probably state this a BUG but its more a Wish list for me tbh.....surely the AI should have some form of priority set for its behaviour and 'attacking the Player' should not be higher than defending it own 'life' ive now played this particular mission (coz its fun) multiple times and All 'axis' flights just seem to pinpoint me as the main target ignoring the rest of the AI spits even when im mashing engage bandits or defend me? my Wish would be for ED to TRY and tweak the rules/priorities to stop this cazyAIness Rant over Edit: just to point out that if its 2 groups of opossing AI's they seem to fight it out rather well, but if im in the mix its like flies round with the = me....

few issues i seen on a dusk flight 1. eternal exhuast flames....previously noted 2. spine underside landing light not working 3. gunsight lens is lit up like a light on external view....even with sight off

nice... I'll give this a try

If you seen no performance gain then yes. your cpu is limiting your performance…. Think you might need to upgrade the CPU

@HILOK yeah your processor might be an issue.... GPU is great though. Reading between the lines on the forums it looks like the ST version is nearing 'end of line' and at some point (probably still got a few years but who knows) ED will stop supporting it, the MT and ST versions seem to be diverging already with regards performance/graphics/features. From your comment on 'i fear my processor might not be able to take advantage of MT' you should try it in 2.8 If you haven't already... just run the DCS.exe file from the /bin-mt folder, and save your graphic settings so you can revert back if all goes a bit pear shaped. if the i5 4th gen struggles just go back to the ST mode and start saving pennies for a new Motherboard and CPU. The good news is a few $100 will give you a good upgrade path as that 2080ti is good for years yet. with regards ST 2.9 my processors single core speed is not hugely better tbh.... I'll underclock it and try on 2.9 tonight on ST & MT

Its good enough for me but don't expect miracles... i'm on an AMD PC and DLSS is by all accounts better than FSR2 so if your getting better than what i'm seeing then you should see a difference.... see below post i done on an AMD thread My GPU is a RX6700xt (R5 5600x) and the move to MT and now FSR2.0 is a game changer in most cases with this lower spec GPU... with FSR2.0 I now have all textures/distances/clouds etc set at high or ultra with shadows on high but left off all the other AA options off and its just amazing how this has transformed the 'majority' of visuals...crisp lines.. no edge shimmer etc I'm even getting a solid and smooth 75fps on my 2k monitor on a mod'd single player Battle of Britain.. with lots of fighters/bombers etc on the channel map. down side..... some really nasty artifacts on other aircraft when dogfighting ie ghosting as mentioned previously and sometimes the plane im chasing is a ghost biplane oh and I cant read the text in the cockpit without moving in closer.. but either way im happy... its Open Beta afterall and im sure it will get much better over time.... 2.8 - high textures, med/low shadows... MSAAx2 SLAAx1.5 = 57-65fps 2.9 - high textures, high shadows... FSR2 0.85/0.7 = solid 75fps (framerate capped at 75 on my monitor) other than the above it looks good.... slightly softer lines with FSR from native but i have read posts where people have had a small performance boost without the DLSS/FSR upscaling. but on a 4k monitor ?? i think you'll be pleasantly surprised. Edit: I'll post some screen shots later..... the above sounds worse than it actually is

Yep I agree looks fab............. TBA with some of the promo shots from ED I was expecting the outside to get a bit of TLC too.

Firstly thanks go to Eagle Dynamics, I was a bit down reading all the 'yes DLSS is coming' from the NVIDIA brigade and that FSR was a 'later' addition, felt like us AMDrs were an after thought so you can imagine my surprise and delight at seeing FSR2.0 in 2.9..... 2.9 is HUGE for me.... My GPU is a RX6700xt (R5 5600x) and the move to MT and now FSR2.0 is a game changer in most cases with this lower spec GPU... with FSR2.0 I now have all textures/distances/clouds etc set at high or ultra with shadows on high but left off all the other AA options off and its just amazing how this has transformed the 'majority' of visuals...crisp lines.. no edge shimmer etc I'm even getting a solid 75fps on my 2k monitor on a mod'd single player Battle of Brittain.. with lots of fighters/bombers etc on the channel map. down side..... some really nasty artifacts on other aircraft when dogfighting ie ghosting as mentioned previously and sometimes the plane im chasing is a ghost biplane oh and I cant read the text in the cockpit without moving in closer.. but either way im happy... its Open Beta afterall and im sure it will get much better over time.... other than that Im still playing with the render/Sharpness settings Current settings:- AMD FSR Scaling = 0.85 Sharpening = 0.7 need to try this

I downloaded the demo drivers to AFMF last night to have a play on my 6700XT….. I have MSAA at x2 and SSAA at x1.5…. in a heavy single player mission i get a solid 60fps -70fps with AFMF off. When I switch AFMF on the DCS framerates take a bit of a drop, 1 or 2 fps, but AMD performance monitor notes FPS up at to, and above 120fps !!!! Like whats been said before with AFMF on and a driver forced FPS at 120 it does stutter when head tracking and its not as smooth as you would expect. It also breaks Vsync so I got some screen tearing. Native GPU frame generation is the way to go for smoothness at the moment, but It should be noted that this is an AMD DEMO technology and has huge potential, but it’s not there yet for gaming. Link below if you want to try but only do so if your comfortable mucking about with AMDs drivers https://www.amd.com/en/support/kb/release-notes/rn-rad-win-23-30-afmf-tech-preview

thanks actualy like it this way

just to add my tuppence worth….. i have a button box with all the appropriate switches bound to the spit…. if I land and switch off the engine with my switches. Then restart hot on the runway the engine cuts because it reads the switch positions as off…. i need to move ALL my switches into a ‘running’ condition before reset then engine will tick over nicely on restart…. You must have something in the off position…. there is also a checkbox on the controls that will ignore the status of any switch/hotas etc on startup that might help you out

with your Sig spec... push your cash as high as you can ie above rx6800/6750xt... Im on 6700xt and get a good performance but just wish I had a little extra

Mostly play single player tbh, but when online its just a different level.... Last time online I jumped two 109's got a lucky first burst on one and got his engine, ran out of ammo in the fight that followed with no2 and got chased all the way back to Dover .... I though I was dead but he must have been out of ammo as he eventuly formed up, wagged his wings and vanished back over the channel....... DCS is just WOW when things like that happen......

Update... So been using these Cadetpedals for about 6 months now and they work.... the Pots I bought are maybe not the best and the toe brake design needs some revisions to make it a little more sturdy if you need them..... I have only used the brakes a handfull of times. So I've remixed this with some MK1 Spitfire Pedals (my design from Original pedals) and removed the toe brakes for now. Printed and all works great with the simple rudder only axis. The solid pedal makes these nearly perfect for warbirds. Next up... intend to make the swing arms a little longer and incorporate the Authentikit Maghall design.....

Late to this thread but its the Spit every time for me..... I have the P51, 109, both 190's and other than some free flights and looking about in the cockpit i have litteraly done nothing else with these birds Being from the UK its just a joy to get a fraction of the experience of the young lads that flew it in BofB/WW2, just to get in that cockpit.....formation flying looking at other spits....damn its just unexplainable. looking forward to the skin update

im finding it a jittery laggy mess since the normandy 2.0 refreash..........all other campaigns are great ?

Grass is tripe....agree.. cant get the .lua to work either

Dont think ive ever heard detonation cues in DCS and probably wouldnt know one if I heard it tbh ..... on the ENG0_ADVANCED_IGNITION_TIMING it just stopped.... anyways following @DD_Fenrir boost guide I've not blown up any more Merlins

I think in 4K videos i watched the grass seems shorter ! (im on 2K).... Might not be a performance hit as shorter grass doesnt need to be visable as far !!.....maybe....who knows....but i agree its annoying Edit:- Nope my 4K solution is nonsense..........grass doesnt change per resolution Edit 2: found the .lua time to play Original enabled = false, --if false - old grass will be drawn lodsCount = 6, --number of lods, the larger the number the thicker in front of the camera, maximum - 6 radiusMin = 0, --near lod radius radiusMax = 60, --far lod radius grassDiameter = 200,--grass circle diameter, m quadSize = 0.400, --grass cell size, m grassHalfWidth = 0.0015*6,-- half the width of a blade of grass, m grassHeight = 0.5, --maximum¤ average¤¤ height of a blade of grass, m bendDistMax = 0.25, --maximum projection of the blade of grass to the side, m pointSpread = 1.2, --scatter of blades of grass of one cell, like mete

Damn... well that explains everything. Thanks @DD_Fenrir& @grafspee Going to test

Dont recall.... at 2000RPM i probably cranked the boost lever fully forward wow didnt know that.... is that modeled ??? I was probaly only in low RPM for 5mins max hence why I thought it was weather related. I was on the french side of the Channel... noticed fuel was on the lower tank so set course for home,, reduce RPM, trimmed and after a very sort spell,,, dead stick.

I think this is my lack of engine managment skill rather than a bug conditions: winter and snowing, 0 deg C After mission im low fuel over channel, heading back on low RPM (2000) to maximise range with oil pressure fine@100 Oil Temp @60+ degC & rad temp 40/50deg C then this............... ["failure"] = "ENG0_ADVANCED_IGNITION_TIMING", ["failureDisplayName"] = "Engine #1 erroneous ignition timing induced damage", ["t"] = 2371.06, ["target"] = "SpitfireLFMkIX", ["targetMissionID"] = "116", ["target_coalition"] = 2, ["target_object_id"] = 16806656, ["target_unit_type"] = "SpitfireLFMkIX", ["target_ws_type1"] = 1, ["type"] = "failure", ["weapon"] = "Aw shoot.", }, [960] = { ["failure"] = "ENG0_DAMAGED_BEYOND_REPAIR", ["failureDisplayName"] = "Engine #1 damaged beyond repair", ["t"] = 2371.06, ["target"] = "SpitfireLFMkIX", ["targetMissionID"] = "116", ["target_coalition"] = 2, ["target_object_id"] = 16806656, ["target_unit_type"] = "SpitfireLFMkIX", ["target_ws_type1"] = 1, ["type"] = "failure", ["weapon"] = "Aw shoot.", }, Am i too low RPM for weather ?? Help

hmmmm 3d printing idea...... helmet... elastic cord.. stepper motors..... = brain tumor