TOViper

Since I am using this weapon often, I would love to have it work again. The flare disappears after a few hundred meters, and the weapon is then somehow "lost". Using VR. HB, can you check it and take care of this please?

We were very high and without canopy, but we didn't die due to the missing air pressure. Thought I should post it and let you know. In case of loss of canopy above 50000 feet you won't die. :smartass: Its good to have Jester check the airspace above the aircraft ... Unintentionally got rid of the canopy by accidentally pulling on this little nice yellow black thing ... while fiddling around with the freaking comms menu.

I have both of them, but I love this idea. Hopefully a friend of mine will try out (and buy) the Viggen.

Just found this: Can some programmer please repair this?

It does for me as well. I'm happy with the current status of other systems in the beast, but the afterburner is like ... :cry:

This topic relates to "New afterburners & features", so ... the question remains: Is there a new afterburner visual quality to expect very soon? Until today (2.5.6.50979) the afterburner looks super-poor, not like the ass of a beast should look like! Please Cobra, give the beast the ass it deserves! Please! :helpsmilie:

Can confirm this behaviour, had this problem at least hundreds of times. Had this when buddy lasing using the F-18 and the F-16. I never posted the problem, since I never had a short track. Currently I concentrate much more on enjoying the sim than testing & bug hunting. Thats ED's job :D

Feedback after using it for about a month: works fine, no hardware crashes or similar. But of course I am carefully watching temperatures ... 4.4 GHz seems good for winter usage, but now summer is on the way approaching the middle of Europe ... damn :D

Seems to be back now :)

True for me, I love to have 90fps over Nevada, and don't care about small details. The fluidness of the picture is what I love so much, and it gives me the feeling of beeing there. Sometimes, especially in Nellis and having many static aircraft placed there, the framerate drops significantly. Currently this is true for my config and the selfmade MP mission I fly very often (never on official servers): = 90fps 90% of time = 45fps 8% of time (near ground) < 45fps 2% of time (near statics in Nellis) For details, see https://forums.eagle.ru/showpost.php?p=4384335&postcount=11

Update for OB 2.5.6.50726 (2020-06-13). Summary of changes (bold are changed): .) Shadows now on LOW .) Textures now on HIGH BIOS: HT off, all 4 cores running at 4400 MHz. DCS.exe: set to "HIGH" processor priority NVidia: Game Ready Driver: v442.47 Texture Filterring Quality: HIGH QUALITY Negative LOD bias: CLAMP Virtual Reality pre-rendered frames: 1 options.lua: options = { ["VR"] = { ["bloom"] = false, ["box_mouse_cursor"] = false, ["custom_IPD"] = 63.5, ["custom_IPD_enable"] = false, ["enable"] = true, ["hand_controllers"] = false, ["interaction_with_grip_only"] = false, ["msaaMaskSize"] = 0.1, ["pixel_density"] = 1.0, ["prefer_built_in_audio"] = false, ["use_mouse"] = true, }, ["difficulty"] = { ["RBDAI"] = false, ["avionicsLanguage"] = "english", ["birds"] = 0, ["cockpitStatusBarAllowed"] = false, ["cockpitVisualRM"] = false, ["controlsIndicator"] = false, ["easyCommunication"] = false, ["easyFlight"] = false, ["easyRadar"] = false, ["externalViews"] = true, ["fuel"] = false, ["geffect"] = "realistic", ["hideStick"] = false, ["iconsTheme"] = "nato", ["immortal"] = false, ["labels"] = 0, ["map"] = true, ["miniHUD"] = false, ["optionsView"] = "optview_all", ["padlock"] = false, ["permitCrash"] = false, ["radio"] = false, ["reports"] = true, ["setGlobal"] = true, ["spectatorExternalViews"] = true, ["tips"] = false, ["units"] = "metric", ["unrestrictedSATNAV"] = false, ["userMarks"] = true, ["userSnapView"] = false, ["wakeTurbulence"] = true, ["weapons"] = false, }, ["format"] = 1, ["graphics"] = { ["DOF"] = 0, ["LensEffects"] = 2, ["MSAA"] = 0, ["SSAA"] = 0, ["SSAO"] = 0, ["SSLR"] = 0, ["anisotropy"] = 3, ["aspect"] = 1.7777777777778, ["chimneySmokeDensity"] = 0, ["civTraffic"] = "low", ["clouds"] = 1, ["clutterMaxDistance"] = 700, ["cockpitGI"] = 0, ["effects"] = 3, ["flatTerrainShadows"] = 2, ["forestDistanceFactor"] = 0.7, ["fullScreen"] = false, ["heatBlr"] = 1, ["height"] = 1080, ["lights"] = 2, ["messagesFontScale"] = 1, ["motionBlur"] = 0, ["multiMonitorSetup"] = "1camera", ["outputGamma"] = 1.8, ["preloadRadius"] = 70000, ["rainDroplets"] = true, ["scaleGui"] = 1, ["shadowTree"] = false, ["shadows"] = 2, ["sync"] = false, ["terrainTextures"] = "min", ["textures"] = 2, ["treesVisibility"] = 6000, ["useDeferredShading"] = 1, ["visibRange"] = "Medium", ["water"] = 0, ["width"] = 1920,

Good words, and they too reflect my thoughts about the situation. Regarding performance, and to stay on topic, I would love to learn what the OB updates really change (code or just configs), which I wasn't able to read anywhere in the update logs. You know, performance is a matter of "good" configs (the many lua files in the game directory) too. Tuning them (don't know if ED does) might increase performance, but thereby maybe degrading quality. Can someone point me to the direction where to find information about this please?

A few days ago this load-out "happend" to my aircraft: Can't remember how I did ... :noexpression:

See pic: OB 2.5.6

It doesn't seem so, otherwise this all would not happen IMHO. We customers are the testers for OB obviously :) It seems they do not have any standard mission for each aircraft which they can test all systems after patching them. I have a few mission for testing the Viggen, but stopped testing for ED, since they don't pay :D But I do reports here and then ..

Add to your registry, in order to never click again in the task manager. Remember to use this tip at own risk: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\DCS.exe\PerfOptions] "CpuPriorityClass"=dword:00000003

Had a new freeze. After flying in Nevada, I accidentally landed in the desert, and was standing there (was immortal). Then I tried to put away my Warthog for leaving DCS, but hit the HÖJD (altitude hold) button. Nevada, MP, single client, using VR. Log is here: dcs_2020-06-10_Viggen.zip

sorry for the bad news :noexpression:

https://forums.eagle.ru/showpost.php?p=4379868&postcount=4

Update for OB 2.5.6.50726 (2020-06-10). Summary: Shadows now on HIGH, 90fps are back on most aircraft I own (not in the F-14). BIOS: HT off, all 4 cores running at 4400 MHz. DCS.exe: set to "HIGH" processor priority NVidia: Game Ready Driver: v442.47 Texture Filterring Quality: QUALITY Negative LOD bias: CLAMP Virtual Reality pre-rendered frames: 1 options.lua: options = { ["VR"] = { ["bloom"] = false, ["box_mouse_cursor"] = false, ["custom_IPD"] = 63.5, ["custom_IPD_enable"] = false, ["enable"] = true, ["hand_controllers"] = false, ["interaction_with_grip_only"] = false, ["msaaMaskSize"] = 0.1, ["pixel_density"] = 1.0, ["prefer_built_in_audio"] = false, ["use_mouse"] = true, }, ["difficulty"] = { ["RBDAI"] = false, ["avionicsLanguage"] = "english", ["birds"] = 0, ["cockpitStatusBarAllowed"] = false, ["cockpitVisualRM"] = false, ["controlsIndicator"] = false, ["easyCommunication"] = false, ["easyFlight"] = false, ["easyRadar"] = false, ["externalViews"] = true, ["fuel"] = false, ["geffect"] = "realistic", ["hideStick"] = false, ["iconsTheme"] = "nato", ["immortal"] = false, ["labels"] = 0, ["map"] = true, ["miniHUD"] = false, ["optionsView"] = "optview_all", ["padlock"] = false, ["permitCrash"] = false, ["radio"] = false, ["reports"] = true, ["setGlobal"] = true, ["spectatorExternalViews"] = true, ["tips"] = false, ["units"] = "metric", ["unrestrictedSATNAV"] = false, ["userMarks"] = true, ["userSnapView"] = false, ["wakeTurbulence"] = true, ["weapons"] = false, }, ["format"] = 1, ["graphics"] = { ["DOF"] = 0, ["LensEffects"] = 2, ["MSAA"] = 0, ["SSAA"] = 0, ["SSAO"] = 0, ["SSLR"] = 0, ["anisotropy"] = 3, ["aspect"] = 1.7777777777778, ["chimneySmokeDensity"] = 0, ["civTraffic"] = "low", ["clouds"] = 1, ["clutterMaxDistance"] = 700, ["cockpitGI"] = 0, ["effects"] = 3, ["flatTerrainShadows"] = 2, ["forestDistanceFactor"] = 0.7, ["fullScreen"] = false, ["heatBlr"] = 1, ["height"] = 1080, ["lights"] = 2, ["messagesFontScale"] = 1, ["motionBlur"] = 0, ["multiMonitorSetup"] = "1camera", ["outputGamma"] = 1.8, ["preloadRadius"] = 70000, ["rainDroplets"] = true, ["scaleGui"] = 1, ["shadowTree"] = false, ["shadows"] = 2, ["sync"] = false, ["terrainTextures"] = "min", ["textures"] = 1, ["treesVisibility"] = 6000, ["useDeferredShading"] = 1, ["visibRange"] = "Medium", ["water"] = 0, ["width"] = 1920,

Same for me. Never seen stable 90 fps before while flying in Nevada with shadows set to HIGH. I will now start figuring out how far I can go with pixel density, but I got used to use 1.0, so every increase is a bonus for me. Hopefully this will be the same when flying with friends on the same server. Loading time when starting up DCS is also reduced, which is now very nice again. Keep it up ED, at least for my computer this update makes a difference! Im slowly getting happy again. :thumbup:

DCS freeze immediately after switching ON the ACM dogfight mode. Happend with an earlier version ob OB 2.5.6. (maybe 2 weeks ago) in flight, and today in newest OB on ground. Using VR, mission in Nevada ran in MP, I was the one and only flying client today. Event 2 weeks ago was same setup, but with two clients. RAM usage was about 11GB of 24GB at the time the freeze happend. Attached is the LOG: dcs_2020-06-10.zip P.S.: Track file does not exist, would be about 40 MB after flying for approx 1 hour.

Again I got a freeze with the Viggen after touching the ground on a runway and coming to full stop in the desert with retracted gear (but aircraft was set to "immortal"). Using 2.5.6.50321, MP, single client See DCS.log: dcs_2020-06-09.zip Memory usage was 11.2 GB of 24 GB, no RAM issue.

I would. 50 bucks for a "VR module", with improvements which gave me stable frame rate at 90Hz would be OK (this is the frame rate I usually get when using a normal computer screen with 2560x1440 with medium detail settings). The other solution would be to buy a super computer to even have 45 fps with a simple Rift CV1, which costs about 3000 bucks, so ... more supercomputers need more power, need resources, old computers produce waste ... all this shit comes up all the time. Better solution: optimize code. AND to ED: never stop improving DCS!!!

Understandable. Hm ... just thinking ... a way ED fishes for pilots in the pool of HB customers in order to have them buying THEIR modules instead of HB modules? No, that is a stupid idea, and pure speculation ... "God da.n Maverick!". Maybe its just bad comms or bad programming on ED's side, or shifting priorities because every single location in ED's code is currently under construction :music_whistling: We'll have to wait I guess ... so let's be patient folks. Me saying ... :D