Wood

EDIT: Your guess is as good as mine. I fly in VR and every other aircraft I fly with the settings is constant 50fps. As soon as I try this beast its a slide show. This is all stemming from the performance killers from the last few updates from ED. Every time, a update was released it killed the performance and you would have to find settings again that would work. When the initial release came out it was sweet and working great until the darn DSC updates. One of the many fixes from the updates was to tweak the max FPS down to 50 from originally where I had it set to 90FPS. That 90FPS would give me 45-70FPS consistently. When I changed it to max 50FPS, as indicated every AC was solid at 50 except for the F-4. Soooooo, saying that. Tonight, I decide to changed my max FPS back to 90 and thought Id try it again. No slide show and 30-40fps and other AC 50-70fps. Go figure.

You guys are able to fly this. For the past 3 months its been unplayable and single digits..

Yup agreed. You should not have to do that. You can see a lot of people getting tired of this and walking away from DCS, at least that's what it seems like. This is not good for for the SIM.

I totally agree on this comment.

Just installed it to check it out and all I can say is wow! What an incredible job these guys did on this mod. Haven’t really dived into it yet with adding it to our servers until more testing is done. Incredible mod on the D model that you for this. wood

Every single time it gets worse after each update. Seems like the product QA is not there.

So after some research and tweaking I found a happy medium for myself on this. I use to have my my FPS set to 75-90. Which would give me 70fps in the air on a good day and 99% of the time jumping between 70 to mid 30’s. My system is not good with an intel i7-6700 with 32 gigs on with 10 and 3080 RTX TI. Out dated to say the least. However, I have the mostly everything set to hi with the exception of shadows off and traffic off and clouds/ water set on high and medium. the past couple of days I tried various this and found that dropping the FPS slider down to a more realistic setting such as 50fps showed a vast improvement on stability towards my fps not varying so much. I would still. See the range from staying at 50fps for 85-90% of the time until I would land at an airbase with a lot of objects and found that it would fluctuate between 45 and 36 FPS. where previously I would see a drop to mid 20’s. I went an additional step for the hell of it and after watching jabbers vram video. We all know that the i7-6700 has only 4 cores and 8 threads so for the hell of it I added the —infinity= thing to see what would happen. Not sure why I saw the results I did but huge change in looking right or left near the ground I would see mini micro pauses prior. After no micro pauses whatsoever ever and an even more stable fps now 95% of the time until it would render multiple objects on the taxi in where I would then see mid 30s until all object rendered completely. Hope this helps. Wood

I tried tha virtual desktop and quite honestly the performance was worse on the initial trial. Very jerky. Granted , haven’t I spent the time tweeting but it’s come down to the attitude “ here we go again with this BS dance” just to make it work properly. One thing that surprised me was. I was always a believer in running DSC as an admin. Why? I don’t know or can’t remember (it’s been that long) but I read that most users are not running DCS as an admin and so I ended up changing it. Results were must smoother experience. Granted the FPS is jumping 72 to 36-40. When I was running DSC as an admin it gave more consistent FPS @ around 45-50 but with a lot of micro pauses and freezes with this last update. I rather have the smoothness than micro pauses. Saying that , it would be nice if Oculus users did not have to use the Gdamn tool tray every time to keep AWS off.

Guys thanks for the replies. definitely something porked hear. I'm at a loss hey John. Tried this and not as successful as you there. Thanks though. I agree with this as well at least that's what it seems like.

Since before the last update I was getting 45-50 FPS with the phantom after its release. After the latest update its a damn slide show. Using the BFM mission with the Mig23 as a baseline it will start off with 40-45 fps and within 1 minute I’m beginning to see it drop to 20-25 fps and during the engagement see a drop down to 15fps. On Final it a slide show. Really, I can actually have a sip of my coffee between each frame as I watch to see how this ends. unacceptable to say the least. Especially, any other module in similar bench missions or higher my fps will be sitting no lower the 55-60 fps. this is not only the phantom but the Tomcat as well. Clearly, the last update pooched a lot of items within the game itself and that ridiculous. This is now supposed to be a release and not open beta. So why are we dealing with these performance issues every single time there is an update. there’s no point in sending a log because it seems we’re consistently changing the settings just try to make it work. So as to the title, I can’t be the only one not seeing performance like this.

I’ve tried this and no change on performance. I use the phantom mig23 BFM as a bench mark and fps tanks from constant 50 to 7fps. Frustrating to say the least.

Hey sorry. Just saw this. I’m out of town right now so as soon as I get back next week. I’ll post what I did to get it back. Wood

Happy boy now! Took a little work and some time fine tuning and now getting 45-55 fps in MP.

Damn pathetic if you ask me.

Don't use any AV software so that's not it for me anyway. Perhaps the problem then lies with the DCS Updater itself. That's a possibility. I'll try the repair but same after restarting it showed it was installed. Let me ask another question? The folder "DCS_F4E" that contains cache, jester and records folders where is it installed? Thanks for the help on this guys

FPS Performance on this beast is bad. My settings I use will always give me no less the 60FPS on any other airframe in VR except for this one. It will tank at 5 fps and unplayable.

Aww.. nice catch , so how is that fixed on our end when the shortcut is showing "J:\DCS\DCS World OpenBeta\bin-mt\DCS.exe"?

FYI Not sure why I received this during the install of the F-4E? 00002.942 --- Log file: C:\Users\Wood\AppData\Local\Temp\DCS.openbeta\autoupdate_templog.txt 00000.000 === Log opened UTC 2024-05-22 15:25:18 00000.021 INFO : DCS_Updater/2.16.3.18 (Windows NT 10.0.19045; Win64; en-CA) 00000.021 INFO : src-id: f697eb0b6959f621dddfde672932cdb00d183f23, lib-id: b88ea51ae2210987a3865f77cc1802548216d7a8 00000.022 INFO : cmdline: bin/dcs_updater.exe --run --waitpid 8996 install HEATBLUR_F-4E 00000.127 STATUS: Waiting for parent process to exit... 00002.937 STATUS: Initializing... 00002.940 INFO : basedir: J:\DCS\DCS World OpenBeta 00002.940 INFO : variant: openbeta 00002.940 INFO : DCS/2.9.5.55300 (x86_64; EN; WORLD,CA,A10C-REDFLAG_campaign,F15C-REDFLAG_campaign,NEVADA_terrain,FC3_video_EN,WWII-ARMOUR,NORMANDY_terrain,MAPLEFLAG_F5E_ACM_campaign,A10C-STONE_SHIELD_campaign,A10C-AAT_campaign,VEAO_HAWK,PERSIANGULF_terrain,SU-33,HEATBLUR_F-14,A-10C,RAZBAM_AV8BNA,FA-18C,F-16C,F-5E,FC3,P-51D,SPITFIRE-MKIX,UH-1H,POLYCHOPSIM_SA342,FW-190A8,F-86F,SUPERCARRIER,P47D30,SYRIA_terrain,BALTICDRAGON_FA18C_RAVEN_ONE_campaign,A-10C_2,NS430_SA342,DEKA_JF-17,RAZBAM_MIG19P,MAGNITUDE3_CHRISTEN_EAGLE-II,YAK-52,AJS37,RAZBAM_M-2000C,L-39,AVIODEV_C-101,MIG-15BIS,MIG-21BIS,BF-109K4,FW-190D9,MI-8MTV2,THECHANNEL_terrain,MARIANAISLANDS_terrain,MOSQUITO-FBMKVI,AH-64D,CAUCASUS_terrain,RAZBAM_F-15E,FALKLANDS_terrain,SINAIMAP_terrain) 00002.940 INFO : branch: openbeta 00002.943 STATUS: Checking for updates... 00003.641 INFO : Got reply from www.digitalcombatsimulator.com 00004.172 INFO : Got reply from www.digitalcombatsimulator.com 00004.176 STATUS: Waiting for operation to complete... 00107.243 INFO : DCS/2.9.5.55300 (x86_64; EN; WORLD,CA,A10C-REDFLAG_campaign,F15C-REDFLAG_campaign,NEVADA_terrain,FC3_video_EN,WWII-ARMOUR,NORMANDY_terrain,MAPLEFLAG_F5E_ACM_campaign,A10C-STONE_SHIELD_campaign,A10C-AAT_campaign,VEAO_HAWK,PERSIANGULF_terrain,SU-33,HEATBLUR_F-14,A-10C,RAZBAM_AV8BNA,FA-18C,F-16C,F-5E,FC3,P-51D,SPITFIRE-MKIX,UH-1H,POLYCHOPSIM_SA342,FW-190A8,F-86F,SUPERCARRIER,P47D30,SYRIA_terrain,BALTICDRAGON_FA18C_RAVEN_ONE_campaign,A-10C_2,NS430_SA342,DEKA_JF-17,RAZBAM_MIG19P,MAGNITUDE3_CHRISTEN_EAGLE-II,YAK-52,AJS37,RAZBAM_M-2000C,L-39,AVIODEV_C-101,MIG-15BIS,MIG-21BIS,BF-109K4,FW-190D9,MI-8MTV2,THECHANNEL_terrain,MARIANAISLANDS_terrain,MOSQUITO-FBMKVI,AH-64D,CAUCASUS_terrain,RAZBAM_F-15E,FALKLANDS_terrain,SINAIMAP_terrain,HEATBLUR_F-4E) 00107.243 INFO : branch: openbeta 00107.257 STATUS: Can't run J:\DCS\DCS World OpenBeta\bin-mt/DCS.exe: (740) The requested operation requires elevation. 00185.391 === Log closed. Started DCS after and the Phantom was there so not sure what this was all about Wood

For me it’s the opposites. cold start works much better. Getting 45-60 FPS. Until I turn the TADS on and then 5 FPS. Frustrated to say the least on the inconsistency from day to day. As long as I don’t turn on the TADS.

Forgive my ignorance here, but with Oculus users, is there no way to set a a line in the autoexec that will disable AWS altogether instead of using the hot keys or using the OculusDebugTool?

Yup thanks I realize that but there is a 5.0 that's been worked on. That's what I'm referring to.

Is it still in Beta?

Thanks for the update. Totally understandable and thank you all for what your dedication and passion on your products.

SAME issue autoupdate_log.txt

During the past while I've been noticing a large mount of errors in the logs. After a major clean up of my install I've noticed that only two remaining. 1st one coming from the Core mode 2024-02-24 13:03:22.258 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_R2}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-02-24 13:03:22.258 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_L2}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-02-24 13:03:22.258 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_R1}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-02-24 13:03:22.258 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_L1}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-02-24 13:03:22.258 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_R2_M}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-02-24 13:03:22.258 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_L2_M}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-02-24 13:03:22.258 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_R1_M}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" 2024-02-24 13:03:22.258 ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{HOT3_L1_M}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/HOT.lua" and the second coming from the mod HighDigitSAMs 2024-02-24 13:04:07.789 ERROR Scripting (Main): plugin: HighDigitSAMs unit replace S-300PS 30N6 TRAILER tr not allowed 2024-02-24 13:04:07.791 ERROR Scripting (Main): plugin: HighDigitSAMs unit replace S-300PS SA-10B 40B6M MAST tr not allowed 2024-02-24 13:04:07.792 ERROR Scripting (Main): plugin: HighDigitSAMs unit replace S-300PS SA-10B 40B6MD MAST sr not allowed 2024-02-24 13:04:07.794 ERROR Scripting (Main): plugin: HighDigitSAMs unit replace S-300PS 64H6E TRAILER sr not allowed Is it a possibility that the error for the Core mod a result of the HighDigitSAMs according to the log attached? dcs.log