TOViper
-
Posts
2498 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by TOViper
-
-
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?
-
After, looking at this thread, it would seems that the fix has been done. The thing is that even if this sim is very good, the lack of afterburner put a bit down the feeling of realism.
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 :)
-
In my opinion the best option to use VR today with currently available hardware: Get rid of AA, supersampling or pixel density adjustments to improve the image quality. There are only so much physical pixels on your display and while the rendering at 100% will surly look awful to you at first after a short adaption phase you will stop noticing the shimmering and the jaggies. What do you get in return? Smooth framerates, 60 FPS on the Reverb, 45/90 FPS (motion smoothing) on the Rift, at all times in single player, multiplayer and even on the channel map and on the deck of the suppercarrier (talking about a 1080Ti in my case). ... But I prefer smooth framerates over image quality every day. Much more enjoyable long hour sessions that way for me.
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?
-
The F-14 fuselage stations are a bit "special" in that they have different positions for the sparrows than for the rest of the stations while still calling them the same. On the real aircraft you can't use any of the forward 3 sparrow stations if you have anything on station 3 and 6 and if you have anything on 4 and 5 you can't use the two backmost sparrows.
The DCS loadout system isn't really set up for this but it is something we're looking at improving. If you use custom loadouts be aware that you can set up "illegal" loadouts and if you get stuff that clip you're most likely currently using a loadout that wouldn't be possible IRL.
A few days ago this load-out "happend" to my aircraft:
Can't remember how I did ... :noexpression:
-
-
Is there any testing whatsoever at all for new code before patch update, ...
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 ..
-
How do you set DCS to high priority? Process Lasso?
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
-
From the log it looks like its a seperate issue, and one I thought I solved or guarded against.
sorry for the bad news :noexpression:
-
-
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, -
If anyone from ED is reading this: whatever you guys are doing to improve VR performance, is working!
Based on what I've seen so far in 2.5.6.50726, my framerate is quite a bit smoother than in the previous builds (and they were in turn better than the ones before those).
Keep it up! :thumbup:
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:
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!!!
-
Sorry golden, it is just not possible. We would be doing nothing but tweaking lights between each patch, we cannot do that. :(
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
-
Not sure why the link doesn't work anymore, but we're waiting for things to settle down with the carriers until we fix this. We've already fixed it just to have it break again and want to avoid duplicate work. When you see it in the patch notes is how you will know it's been fixed.
Fully understandable.
Jester and me have been high ... but we didn't die ...
in DCS: F-14A & B
Posted
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.