

SpeedStick
Members-
Posts
362 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by SpeedStick
-
So I tried both of your suggestions. Playing with deferred shading too. More visual bugs with it on, but it seems a bit smoother actually. But, suttering and ghosting still there in MP. WOrks flawlessly 70% of the time in empty mission. Still dont know how to get rid of it. Thanks for all the ideas so far though.
-
Finally some more people with the ghosting/stuttering when moving head in 388. I also wanna go back to 385 but again, Core 2.0 probably wont work then... Ill try your advice Quadg
-
Ive got a i7 4790K, GTX 1070, 16GB Ram on a SSD. Before I could go High on textures and VisibRange, 4xAA and PD 1.4 with ASW On and no ghosting. With the new drivers I cant even run 1.2 PD and most settings on medium, no shadows or AA. It runs ok in an empty Free flight but in MP I get around 30 fps but mostly less. And constant ghosting with ASW on and small jumps every few seconds and lag with it off. The only thing that seemed to work was 385 drivers. No one else experiencing anything similar?
-
What settings are you running? I cant get it running with out ghosting or extreme lag
-
Yeah had an old version of OTT so I updated. I can verify its off now at least, but Im still very disappointed with performance after 385. I've seen people with way worse rigs than me running at higher settings and dont mention this problem, ASW on or off. Dont know what the magic thing with 385 is, but cant go back now that Core 2.0 is out.
-
Yeah its ASW. Been fiddeling with it but its borked on the newer drivers for me it seems.
-
No you are right, something is different. In a good way. Now it does drops and stalls if you go below speed. You can do the high G turns and bleed speed like you expect in Deltas. Haven't done any test but at least it feels better.
-
So again, to clarify, is fm/engine fixed so its not a ufo-glider and closer to irl stats/behavior? Edit: or just the new fm with all its flaws? Edit2: Nvm, https://forums.eagle.ru/showpost.php?p=3319865&postcount=293
-
Yep. I'm still getting ghosting/lag, but the symptom for me seems to have at least been cut in half intensity. If the ghost image before would be produced every 0.5 seconds it looks blurry and laggy. Now it does it every 2-4 seconds which is more of a laggy feeling. If you are satill on 385 and dont want Core 2.0. I would not recommend it. If you want the new rift interface you have too update. To be clear, I'm not sure if its new rift or driver update that has made it slightly better.
-
Second this. Want to know.
-
Improved frame rates with new Nvidia driver 388.43
SpeedStick replied to crowebar's topic in Virtual Reality
Thx for the tip but it did not seem to make any difference. Always starts to ghost/lag after a while. Back to 385 for me I guess. -
Improved frame rates with new Nvidia driver 388.43
SpeedStick replied to crowebar's topic in Virtual Reality
Just FYI: installed and tried out .43 and the ghosting/lag came back, unfortunately. -
Improved frame rates with new Nvidia driver 388.43
SpeedStick replied to crowebar's topic in Virtual Reality
So just to clarify, the new nvidia drivers (.43?) eliminates the ghosting or lag issues in earlier ones? Just as good as 385? -
Check your drivers again. Mine kept updating back to 388 without even me noticing. Extremly annoying.
-
Monitoring. Nice finds if accurate.
-
Thanks for the info CptSmiley. Fits good with how I understood with how it seems to be designedm like how the AP standby controls on the stick are grip activated. The new FM feels a lot more like how it looks to fly when seeing real videos. Again no pilot but this feels more intuitive and correct. Love it.
-
This is the post of the year, if not century, for me. I've been bitching a lot about my disappointments, especially in fm, lately. Not just here, but quite a few others aircrafts as well. Fm being (functionally) as close to IRL as possible is the most important thing for me. Its a sim, and hence a core feature after all. And hearing that its intended and that you have reasoning behind it warms my cold bitter heart. I like the mentality behind heavy AP use. Disclaimer: I'm just a random worthless random internet person and claim no special knowledge nor to be a Mirage pilot. TL;DR: Cant wait to read your reasoning and try out the fm changes! Thx.
-
link for the reddit post about update? EDIT: Nvm I found it.
-
Let him be excited... And let Temp89 express his views. Frankly I'm with Temp89.
-
I had exactly the same problem. Role back gpu drivers to 385.xx. That worked for me.
-
Ive tried different modules, both in 1.5 and 2.1. Also tried different settings as I wrote before. Someting I notice is, that it seems to reset the problem when the HMD is in standby or whatever, when you remove it. That usually last for a couple of seconds or a minute then its back again. Its very strange indeed.
-
Hmm this is strange. Redid sensors setup and calibration Updated usb drivers. Rolled back gpu drivers to known stable version with DDU and clean install. Went back from Oculus Home Beta branch to stable. Installed Dcs Beta to check difference with Alpha. Checked DCS and switched settings, same with rift. Also checked OTT was good. Still, anywhere from 30 sec to 3 or 4 minutes it will start to produce the weird "lag" or ghost image. Again, it doesnt seem to be depicted in the FPS or rendered objects or any of that stuff. I cant see it at least.
-
No thats all fine. Its like I can fly for like a minute, then it starts to lag. But it doesnt show in fps counter, but very clearly stuttering when looking around and stuff. Very weird.
-
Sorry. Just got so frustrated that I forgot to mention. Yes CV1. Yeah sure can try it, but that doesnt ussualy effect lag/tracking in this extreme.
-
I suddenly got a new annoying issue the last week. When flying after about 30 sec to a minnute tracking gets really jerky or laggy. But fps counter doesnt seem to be effected. Altough it feels very laggy. Dont know how to fix it. Anybody had anything similar? Sorry dont mean to hijack the thread.