TOViper

I am world champion in disregarding things ...

You meant ".... requirements are NOT met." ???

Hi LiamK8! Thanks for offering your help despite not needed. Had no bigger problems so far, despite having some with the Viggen. Anyway, your work-around doesn't work, I set everything corretly but the folders are still created once every startup of VAICOM Software is bugged I guess.

Yup, but its written new once every startup of VAICOM

I had same issue last week. I worked around it for the moment by just saying both things a second time (or was it a third time? Can't remember) ... finally they have been removed I can remember.

Maybe someone experiences the same problem when updating the LUA scripts in the DCS user profile folder/scripts. My SavedGames folder for my DCS openbeta is c:\users\pilot\DCS.openbeta28x This is, because my DCS installation folder has a file called variant.txt in it, which holds the string "DCS.openbeta28x" This is, because I use more than one DCS installations on my computer. Unfortunately, VAICOM always updates the scripts in the folder DCS.openbeta (which I don't use at all, so it is created by VAICOM). I have to manually update the file export.lua in my DCS user profile by copy-pasting the respective line and then saving it, and then fire up DCS.

Thanks for that information Whisky! I hate to re-ask you again, sorry 1000 times for that, but in fact I have to: I re-sized PitchLines.tga and PitchLinesNegative.tga down to 1024x1024 pixels (no worries, just for testing it), and changed the lines 256 and 265 in the file HUD_indication_page.lua: local PositivePitchLinesHUD = Hud_Pitch_Lines2(HUD_POSITIVE_PITCH, 0, 0, 1024, 1024, 6.9) local NegativePitchLinesHUD = Hud_Pitch_Lines2(HUD_NEGATIVE_PITCH, 0, 0, 1024, 1024, 6.9) This had absolutely NO effect, despite the lines are not shown on the HUD (with which I really could live to be honest...). I used a very long update time (10 seconds!), and I really can't understand why the framerate is still as low as if I'd use e.g. 0.01. local update_time_step = 10.0 I give up on this.

Just an additional info, maybe it helps: I changed the line for the update in the file "HUD Device.lua" to the following: local update_time_step = 1.0 with the consequence that fps are still low. Only by de-activating the HUD device in the file "device_init.lua" the fps are high.

Just did another small performance test on my power rig (AMD, see signature): DSC OB 2.8.3.38090 ST, again 1 Screen, hot start on runway, single aircraft on Caucasus map. Again no rendering of landscape. Again LMFD, RMFD, CMFD are eating around 1fps, but the HUD eats now 70 fps!!! The frame issue is again caused by the HUD. Screen_230405_154349_without_Devices_with_MainPower.jpg Screen_230405_154356_without_Devices_without_MainPower.jpg Screen_230405_155130_with_LMFD_RMFD.jpg Screen_230405_155342_with_LMFD_RMFD_CMFD.jpg Screen_230405_155637_with_LMFD_RMFD_CMFD_HUD.jpg Kind regards, TOViper

I think so too. With MT everything seems .... don't know how to say ... a bit more widespread. Did you apply the same initial state of aircraft, same map, and same rendering settings, single aircraft on map, no mods other than Gripen? Maybe we can help to nail it down and help the crew ...

Just a small experience report on my power rig (AMD, see signature): DSC OB 2.8.3.38090 MT, 1 Screen, hot start on runway, single aircraft on Caucasus map. No rendering of landscape. LMFD, RMFD, CMFD are eating around 1fps each, but the HUD eats 40 fps!!! The frame issue is caused by the HUD. And by the way: the fps doesn't go up when the device is initialized in the LUA, with main power ON, and turned OFF in the cockpit with the rotary knob on the left lower side of the HUD. Screen_230404_194826_without_Devices_with_MainPower.jpg Screen_230404_194940_without_Devices_without_MainPower.jpg Screen_230404_195208_with_LMFD_RMFD.jpg Screen_230404_195413_mit_LMFD_RMFD_CMFD.jpg Screen_230404_195637_with_LMFD_RMFD_CMFD_HUD.jpg: I didn't test the other remaining devices like HMD/Indicator/ LCP/Indicator/ UCP/Indicator/ Maybe you want to dig into the HUD, which is causing the issue... Kind regards, TOViper P.S.: Im not in your team, but I am happy to help whenever I can, and you may log 1 hour of work

Copy, thank you for the advice! I will check once I am back on my lower spec rig.

Yes, I did. Note that I used my older rig for the flights and the postings above (which is not listed below in my signature). It was Intel i7-6700 @4.4GHz with GTX1070 and Oculus CV1 and OpenXR (optimized for high fps). Where do I change this setting?

Thanks whisky for your answer! In the meantime, I will try to figure out how I can increase the fps a bit. Maybe the Display Resolution setting affects the fps, or other settings. Once I find something out, I will post it here, maybe the one or the other can use this information.

I was confused by the thread about the issues, which states somewhere: "It's not a bug, its a problem with all SFM's. In the next update it will be fixed cuz they'll change it to a EFM." So I wished it was fixed / improved. Anyway, I don't fly it anymore since in VR I can't even get 45 fps (other modules like the F-16 at 65 fps, F-14 at 55 fps) which is very sadly far below ALL other modules I am currently owning. What can I do in terms of optimization on this module?

Hello! This relates to my rig as well, which is p.i.t.a. and I don't fly it currently because of this. Furthermore, since installation of the updated mod, the standard engine sound of the F-15 is also different (mod overwrites it?) Other issue: the nosewheel steering simulation is kind of weird. If I taxi at approx 1 m/s or slower, the aircraft starts rotating wild. Not the F-15 implementation?

Hey Flappie, I wish I could give you more info on this issue. I talked to Quigon (who was GUNNER), and he - like me - just watched another UH-1H behind us (another client) in that very moment, without performing actions in the cockpit (besides flying the bird). The trackfile is broken, just has 2MB (but we flew at least 10 to 15 minutes).

MT MP OB 2.8.3.38090 Caucasus Buddy Spike Blue Flag 80's Flying in the AH-64 as PILOT and having a my buddy as client as GUNNER, the flight from a farp to another farp ended in in the middle with a game freeze for both of us at the same time. Only the DCS.log has some information, there was no crashdump or whatsoever. Find the attached log, which is full of errors, warnings, etc. Last entry is the following: 2023-03-24 23:22:57.089 UNKNOWN UnitsLayer:: (Main): m_obj2ctl.find(obj) != m_obj2ctl.end() dcs_crash_2023-03-25.log

I am pretty sure you are right about that! In any case, I usually prefer hosting heavier missions on a dedicated server (e.g. I use an older notebook for that), and then fly the mission as client on my power rig. This releases my rig a bit, and gives some resources free with the aim for slightly better fps.

Welcome in the world of Viggen!

Most probably the DCS.log contains very useful information for the stuff, so I am pretty sure it would help. You find the DCS.log in your windows user profile folder / DCS / LOG folder. If you reply to the thread, just drop it into your posting and it will be uploaded. Same goes for the DXDIAG log file. Both files are small in size, so you may be allowed to upload them to your posting. But as said, for the problem you described above, it may make sense to open up a separate thread with some detailed description to keep this thread on topic (Hyperthreading ON/OFF experiences). Kind regards!

I think your issue may be worth a new separate thread with some more infos on your hardware (DXDIAG, DCS.log, etc...)?

MT OB 2.8.3.37845.1 SP Nevada VR Flying AH-64D as Pilot DCS freezes after flying for about 5 minutes in the hills on the way to waypoint 2. Attached find my DCS.log dcs.log DxDiag_new.txt

True. Once I disable Hyperthreading in BIOS the folling I tested: .) DCS (ST) runs super smooth when looking to the side in flight .) DCS MT runs with some stutter when looking to the side in flight My rig for tests: Intel i7-6700, 4.4 GHz, GTX 1070, 40GB RAM @3000MHz, RIFT CV1 Details & measurements: AH-64D, SP, single aircraft on map, Nellis ramp position H07, hot start, IHADSS off Scenario "A": NVIDIA: +200 MHz Clock / + 400 MHz Memory INTEL: 4 cores, 4.0 GHz, Hyperthreading OFF DCS: TERRAIN TEXTURES=HIGH No ASW: ST: 52 fps, mega stutter, unflyable MT: 65 fps, mega stutter, unflyable With ASW: ST: 45 fps, to be filled in later MT: 45 fps, to be filled in later Scenario "B": NVIDIA: +200 MHz Clock / + 400 MHz Memory INTEL: 4 cores, 4.0 GHz, Hyperthreading ON DCS: TERRAIN TEXTURES=HIGH No ASW: ST: 48 fps, mega stutter, unflyable MT: 66 fps, mega stutter, unflyable With ASW: ST: 45 fps, very light stutter when looking to the side, well flyable MT: 45 fps, heavy stutter when looking to the side, starting unflyable Scenario "C": NVIDIA: +200 MHz Clock / + 400 MHz Memory INTEL: 4 cores, 4.4 GHz, Hyperthreading OFF DCS: TERRAIN TEXTURES=LOW No ASW: ST: 61 fps, mega stutter, unflyable MT: 77 fps, mega stutter, unflyable With ASW: ST: 45 fps, no stutter when looking perpendicular to flight direction, super flyable MT: 45 fps, some stutter when looking perpendicular to flight direction, OK flyable Finally: Best solution for single aircraft on map is DCS ST with 4 cores and Hyperthreading OFF at TERRAIN TEXTURES LOW. Also: It seams that the VR implementation of DCS MT is not as good as DCS ST. Attached all my files, which releate to scenario "B". 2023-01-18_short_track_looking_perpendicularly_to_flight_direction.trk dcs.log DxDiag.txt