Helios1138
-
Posts
50 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Helios1138
-
-
2 hours ago, Flappie said:
Hi. If you don't own the A-10C module, it's very easy to fix: launch DCS, go in the module manager (upper icons), disable A-10C module (refuse to restart) then click the bin icon on the same line. The game will restart and the message will be no more.
I'm on Steam version, so there's no module manager in-game. In Steam A-10C is not in the list of DLCs
-
Ever since the last free play event, I keep getting this error message interrupting every game startup. What can I do to get rid of this?
-
My usual gamma setting for VR for the previous stable version was 1.6. For the current OB I have to set it to 1.4
That would be fine, however it looks like the brightness is not stable, it fluctuates between mission restarts. When I launch the game for the first time, it's too bright, so I have to bring the gamma down to like 1.1 or even 1. But then with the subsequent mission restarts the game gets darker, until after 2 or 3 restarts settling back to being comfortable at 1.4
Same mission, same time of day, weather etc., obviously
-
Try delete metashader2 and fxo folder, after that your problem solved cheers!
I'm aware of this trick and I've been doing this after every version update anyway, so this does not solve my issue, unfortunately.
Things to try.Test with a lower pixel density 1.0 see if you notice a frame increase.
try with shadows off, shadows and terrain object shadows, or just terrain object shadows. Note if there is any difference.
try disabling bloom effect - any change?
Let us know how you get on.
thank you
Things I've tried: updated to the latest OB, switched to Oculus Tray Tool for pixel density, and removed (set to 1) "VR pre-rendered frames" setting in Nvidia control panel. It does appear to be running smoother, however, it still stutters from time to time (especially during rolls, for some reason). I can no longer compare with Stable since Stable has since been updated with the latest OB (with this performance degradation).
As for the things you mentioned, I'm not sure what would be the point. Even if the game will run smooth with 1.0 PD and no shadows, this isn't how I would want to run the game on my machine. Besides, the issue was the difference in performance between the previous Stable and OB, not between the game on different settings. Maybe I misunderstood something?
-
Can you post your
nvidia settings
DCS settings
steamVR settings / oculus settings
system spec
and what version of windows you are on.
thanks
System specs
Windows 10 Pro
i7-9700K @ 3.60GHz
32 GB
2080 Ti
SSD
Oculus Rift S
Nvidia - everything on default, except
Power management mode: Prefer maximum performanceVirtual reality pre-rendered frames: 4
DCS
I'm not using SteamVR, and I'm not sure what settings are there on Oculus, I didn't modify anything there. Is this it?
I'm launching the game like this
-
Tried the latest open beta version. Unfortunately, the issue is still present - VR performance is still much worse than stable.
-
same. can’t change livery in multiplayer because of this and obviously no radio comms :(
-
I've done one quick video
Thanks for that! Now at least I know that the flight model is capable of this, I will attempt to correct things on my end :)
-
Why do you keep the trim neutral?
That’s what the instructor on my flight did. Also, it’s what the manual says to do when 2 pilots are present
The statement in the manual doesn't mean you physically get the nose gear off the ground at 90 Kmh. The idea is to reduce the load on the nosewheel by applying some bacstick.Possibly. Although looking at
for example, you can see that the nose is actually starting to rise at 90 to 100 and at 120 he’s already airborne. In DCS it seems the nose only starts rising at 120. -
The official manual says that you have to raise the nose at 90kph. I flew in the real Yak (pilot seat but the takeoff was done by the instructor) and watched a bunch of cockpit videos that basically show it behaving as described. In DCS, however, the nosewheel cannot be raised at 90kph no matter how much I pull on the stick. It only comes up at something like 120kph it seems. It also sometimes does this very violently, so I even have to apply a forward stick to keep the angle manageable. The trim is kept neutral during this.
Am I doing something wrong or is this an issue with DCS flight model?
-
If I replay a VR track in a non-VR mode, the head movement disappears as soon as I try to zoom out. Is there a way to avoid that?
-
What the title says. Same for both FW-190 modules
-
just to make sure I downgraded to stable (which AFAIK is the latest 2.5.6 before the last update) and under the same conditions, I'm getting ~60% GPU load and solid 45 fps. So this issue is definitely from the last update
-
I'm getting 100% GPU load on the menu / in mission editor screen and 95-100% in-game. Settings did not change. Tried removing fxo/metashaders. In-game tested on empty Caucasus map with F-16 at midday.
2080ti / Rift S
-
@BIGNEWY
and all DCS World War II products for freeIs I-16 considered a Wolrd War II product? Because it's not available for me in Steam :(
-
I saw a Play button on JF-17 and it did install successfully, but I can't see the Play button on any other module that I don't already own.
-
-
Camera jiggle keyboard mapping is gone and is impossible to set (the cell is greyed out). Anyone else seen this issue?
-
To be honest, I've had it for a long time, this isn't 2.5.6 specific.
-
Is it possible to make "Record AVI" feature to work with ReShade? Currently, if you enable ReShade, the resulting video will still be unaffected even though the effects do seem to apply during rendering. Is it using a different rendering pipeline somehow?
-
basically what the title says. empty mission, single plane, cold startup, takeoff, flying around, as soon as I touch down and start taxiing, FPS drops to something like 10-15. Only in F/A-18.
-
You can also remove the gun sights/camera in the L-39C for a cleaner view. I believe its in Special - L-39 - and choose 'dismounted' for gun camera.
oh, awesome, didn't know that
-
Please report any issue (related with this mod) or feedback here
Is it possible to adjust the lighting that afterburner casts on the ground? When a/b is blue, the light is still yellow on the ground.
-
I get this very regular pattern of lost frames every half a second or so (especially noticeable if you slow down the gameplay to like 1/16th)
I'm running 9700K/2080ti/32GB/SSD so usually the settings are quite high, but just for testing purposes I tried switching to lowest settings possible and lowering the resolution and the same behavior is reproducible. In fact, the rate of dropped frames is still exactly the same.
Neither CPU (the single core of it) nor GPU is 100% loaded.
I even tried limiting the framerate to 30fps in Nvidia Control Panel, but the stuttering is there regardless, even though the game otherwise runs perfectly in the 70-80fps range even on the highest settings for me, so how it still stutters on 30fps lock with lowest settings - I don't understand.
It's not a game-breaking issue for me, but I'm trying to record videos in-game and I'm looking for a way to get a constant smooth framerate.
Error message interrupting game startup
in General Bugs
Posted · Edited by Helios1138
I tried starting up with firewall disabled, it didn't help. And I don't think this is actually similar to that situation. Like I said, it's only since the last free to play even, it's only for a single module (that I don't own). So I doubt it's something on my end.