Jump to content

Warthog_Farmer

Members
  • Posts

    146
  • Joined

  • Last visited

Everything posted by Warthog_Farmer

  1. Double vision tracking jitter is only resolved by rolling back nVidia drivers to 388.59 . This is the last set where it doesnt screw the tracking. Is this fix for you? Well - if you get tracking jitter in game and then come back to Oculus home and it is still jittering even there (until PC restart or Oculus services restart) then the driver rollback should fix it. Absolute pain in the butt.. But hey ho
  2. I think your problem might be running ASW off with <90fps. Supposedly the headset will only display 45fps as Vsync is hard coded to prevent tearing in VR. YOU MIGHT BE RENDERING 60fps but you are not displaying it. That is as far as I understand. With 8086k/1080Ti I can’t get 90fps in Rift. I hate ASW glitches so I must run a jagged sim until optimisation happens. I tend to play PUBG now because of this instead... which is a shame. Just re-read and realised you said you get 90fps. As long as they are constant I am not sure of your issue. I had the same issues before the driver issues and it was purely performance causing it. Run Oculus debug tool overlay and make sure your performance headroom is never below 0
  3. nVidia drivers 388.59 is the solution. Google it for the download. It's a fairly common problem. They are the latest version to not suffer from the jitter-bug. It's a shame cos the newest version seems to offer a better framerate - but the jitter is unplayable. Eagerly awaiting new drivers.
  4. It seems to be tied to frame rate right now I think, probably to prevent "jumping" and making you feel sick. I think I have strong enough VR legs now to deal with a little stutter for quicker zoom though. I'd like the option - or a file edit to try it out.
  5. Hey, Long time VR user here (since DK2). I am really struggling with DCS in recent times and kinda gave up on it for a while.. but the F18 has me back. I really dislike ASW and disable it every time I use DCS. Previously I would have an entirely unlocked frame rate and it suited me. I would normally sit in a variable range from 60-90 unless sh*t was hitting the fan in the server. Nowadays - regardless of the aircraft - I seem to get 45fps consistently unless I am very high/very out to sea where it will pick up to 90. Is there a lock on the frame rate even with FPS disabled to sit at half the max refresh rate? Is anyone else experiencing this? I run a 4790k at 4.5, 1080Ti, SSD, 32Gb RAM, Win 8.1. My system is kept in fairly good condition and lean as far as unncessery software goes.
  6. Hi! Just came up with an idea today... Is there any possibility the tooltip can be used to display the current active selection? For example - I own the Viggen but I can’t really use at as the small font on the rotary wheels used for weapons employment is too difficult to read. I have noticed some modules have a list on the tooltip which lists the selections. Off the top of my head the Harrier’s HUD symbology brightness selctor will show the switch ID in Tooltip and then show DAY/AUTO/NIGHT as these are the three selectable positions. I would like to see a box or a highlight put around the relevant option which reflects the switch position. Provided tooltips are updated across the board this would make every aircraft much more effective for VR users (IMO) Thanks!
  7. Perhaps gamma setting is the issue. I’ll try it when I finish work tonight. Mines is set at 1.5 iirc. Anything higher makes daylight ops a very washed out affair. As for my point about VR NVGs making the cockpit unusable - this will continue to be the case.
  8. In VR the NVGs are near useless as anything in cockpit (except HUD) is a blurry mess. It appears in VR the NVGs occupy 100% of the screen where as monitor users have the green circle but can see everything else around it unamplified/blurred. I am also wondering if VR users are the only ones suffering with NAVFLIR issues. Next time I’m on I plan on trying with and without my Rift on, and with and without Deferred Shading on. It’s pretty much unusable at night in VR in its current state due to not being granted ‘the green circle’. I’m not sure the blurring of the intstrument panel is intentional (perhaps too close to focus the HMD) or not - but either this effect needs removed for VR users or we are granted the circle.
  9. I meant the VR subforum on here. Many people are reporting this issue across various modules on my bug report. It's nothing for RAZBAM to worry about =] The reason you are not having problems in the F15 is that it is not a clickable cockpit and therefore there are no tooltips
  10. I assume you have checked the Input/Output // Virtual Reality section? You'll see that this is a bug of the OpenAlpha and not the Mirage module.
  11. Just swallow the bitter taste and turn down your settings. I'm on 4790k/1080Ti and I get 60-70 average, occasionally smooth runs at 90fps and the occasional dips as ever. The upgrade from 980Ti to 1080Ti allowed slightly higher settings - but not as much as I had hoped. Overall smoother with slightly improved visuals - but still a while to go to 'perfect' Remember it's DCS! There's been a 1080Ti thread on here talking about just these issues since launch - I think you should not be expecting so much (wishing, perhaps ;) )
  12. https://forums.eagle.ru/showthread.php?t=191310 If your Nevada/Normandy is crashing you out on the latest update then turn off mouse tooltips!
  13. Hmm... good work guys:thumbup: Looks like I'll be rolling back. I am in the process of learning a new module so the tool tips are very handy right now!
  14. Edit: If DCS in VR is crashing when you move the mouse over a switch then you can fix it by disabling tooltips in the menu. This bug is known to the developers. ------------------ Hey. Latest update (2.1.1.8244) crashes my OpenAlpha. Happens in a few aircraft I have tried and various free flights/missions. I run Oculus. Can fly, it seems, indefinitely if I don't touch the mouse. There are no issues if I spawn in, hit fly, and then don't touch the mouse again. I seem to be able to move the mouse in a non-clickable spot (Blue crosshair) without problem, but within seconds of my mouse transiting or hovering over a clickable area (yellow icon) then the game will crash. Windows says the fault module is "dxgui_edge_render.dll". I have tried repairing/removing this file and repairing and neither has fixed it. I have updated to the latest GeForce drivers (1080Ti) and still no fix. No crashes within the mission editor or the rest of the interface so far. I have to go to work so can't troubleshoot right now. Anyone else?
  15. Have to say I am impressed with the improvements to average FPS.. but unfortunately the lows are just as low. Single player testing was delightful - but jump on Blue Flag or a WWII server and it's just as much of a strain. I can't stand ASW so I disable it. Perhaps that is where we see things differently. Absolutely fresh windows, Oculus software and DCS install upon installing 1080Ti and it feels a bit 980Ti during the lows - but much smoother on the highs. This really is a coding issue. No matter how much hardware you throw at it... it's still gonna suffer at the low end. The current clouds issue is crippling on some servers =[
  16. Problem solved... Please delete :) I would report it but it says it isn't to be used for that
  17. Confirmed here too! I thought it was something I was doing wrong.
  18. Most likely you accidently activated AFK (Autothrottle). The control lever is at the very back left of the cockpit, just left of the landing gear lever. If this is bound to a button it only works as "ON" at the moment and not "ON/OFF" so if it is activated accidently you have no real chance of knowing what you just did. Perhaps you had assigned it to a button and pressed it by accident? Or a switch was in an "ON" position and so always activating AFK?
  19. I read this and skipped over it in the manual. However today I revisited the tutorials and I clicked on the emergency trim by accident. No matter how many times I cycled that CB I was unable to get the normal trim system moving. Will try and recreate tomorrow and see if I need to file a bug :)
  20. Guy on yesterday called Carbide (iirc, or Carbonite or something) in the late hours of GMT (try 11PM for the user ID) on red team getting shot up and quitting before kill/death registered and then instantly rejoining and taking off again. I noticed it... and then another guy mentioned it in chat and then another. Not the worst crime but when you guys keep a stat tracker for the server it skews the numbers a bit =] Keep up the great server guys =]
  21. I'm using I5 so not hyperthreading. TrackIR is no longer in my household so it isn't that :)
  22. Aside: I tried ASW for the first time earlier on... The multiplayer was unusually busy and unusually laggy tonight and the ASW couldn't keep up. The cockpit was a blurry artifacted mess at point :) I can see it's use though when the servers aren't acting so crummy so I'll leave it on for now. But I don't know if that or the stutters are preferable :)
  23. I have the issue with no other apps including Oculus Home, admittedly I don't use many other apps. The performance is not the cause as I can go up high level over the sea at 90fps and it still occurs. I am just wondering if the mod I thought I uninstalled is still present. It stopped your head pivoting on your shoulders which made looking behind (and looking at some awkward switches down the rear/side panels) more difficult than it ought to be. The mod caused your head to, instead of looking straight back, look back but offset it so you were effectively looking over your shoulder. I don't rememeber putting this into the OpenBeta install but perhaps it got copied over from the "normal" release when it searches for matching files to prevent re-downloading. Perhaps it's just time for a clean reinstall of DCS.. Maybe when 2.5 releases... I'm glad it's just my problem and I might have figured it out :')
  24. Hey folks... This has been a problem for a while for me but I have just decided to live with it. I mainly use Rift in DCS so it's refreshing going to any other app and it doesn't have the same "jump" in the tracking. Anyway, I find that when I am looking around 90+ degrees right or left theres a slight jump in the head tracking to a new position. It's roughly correct but the jump is a bit of a pain. I initially thought it was the Rift sensor losing a couple of the LEDs on the headband and not knowing what was going on but it only happens in DCS. Anyone else have this issue?
×
×
  • Create New...