Jump to content

trigen

Members
  • Posts

    596
  • Joined

  • Last visited

Everything posted by trigen

  1. I see, that's a shame. I really prefer it to the warbird base. For my heli stick project the WB base isnt usable sadly.
  2. It will be restocked on the 19th but dont think the Mogoose base will be so i wont be ordering anything "All items will be restocked including the VPC WarBRD Base, VPC MongoosT-50 Throttle and VPC Constellation Delta Grip as well as all our accessories. Further news on the VPC MongoosT-50 Base will be coming in the near future." Its a bit hard to interpret this since they say all items will be restocked but mention further news on that. Hopefully the t50 base will be in too. In any case id pref getting a used deal though
  3. I have done all the obvious stuff of course. It's back on stable of settings now anyhow
  4. Believe me ive banged my head in the wall a few times.... Its restored trough a full (drivers installed etc) system image yes but there's no change. Would be looking at a full format which isnt a huge deal, just annoying.
  5. Hi there i7700k win 10 1803 1080 TI I had a rather fresh windows install and i had my DCS and X plane 11 running rock solid. CPU frametime was running 10-13ms Could do 300% SS in X plane and lots in DCS without any issue Decided my ram was bottlenecking those last CPU ms and tried to OC the ram to 3000 a little quick but had 3 crashes. Lost X plane settings completely (had to redo all) with only a desktop crash and never actually starting it, also had a samsung driver failure for the HD. After this ive tried every setting imaginable even reset windows to a fresh system image. No matter what i do now i get stutter regardless of the settings. Tried loading defaults in Bios, process lasso, all kinds of nvidia control panel settings. Basically nothing works. This mainly for X plane but i do get some stutter in DCS too Any ideas? I have no idea now.
  6. From 2400 to 4000 you can gain about 10-12fps or so depending on the game if I recall correctly. Your average will be higher. I tried going for 2666 to 3600 and there was a noticeable performance increase but if you are not doing VR I don't think its worth it. I got mine mainly cause I lacked a few fps in x plane to stay above 45 fps and it worked for that. I could also set my settings higher. But I sent it back cause I found out I could set texture quality to high performance in nvidia settings and gain it there instead. People say 3200 is the sweetspot though
  7. I'm generally busy looking elsewhere so I hardly ever notice. In fact I didn't until I startet looking for it. Everyone is different though. I'd say apart from the map of course that I wasn't aware of I would call it very minor issues that really does not impact visuals and the experience in any way compared to what you gain. Hopefully the map issue will be fixed.
  8. The Odyssey is more clear than the Rift there is no question about it. Its not as comfortable and has a smaller sweetspot but ive gone from having a hard time reading anything in the Huey to reading everything. Pixel density, well of course you cant run the same but you got more physical pixels which is better anyway. Their ASW tech is also top notch (close to 0 ghosting/distortion) so you can do 45fps and have it feel great. Ill be bying the Pimax 5k for its FOV later but might keep the Odyssey depending on the software side of Pimax. I could never go back to the Rift or Vive.
  9. Thats your computer not being up to the task im afraid. Going to have to lower your settings
  10. I would say so yes. Moving my head quickly from side to side on 45 fps with wmr solution on is one solid image. With the other options every second frame would look like a ghosting frame. Smooth but you will see it clearly. Edit I had to do a test with it on in DCS as ive been flying mainly helicopters. If i move my head really quickly from side to side in the cockpit you will notice some frame ghosting. Little slower and its more distortion on certain lines. In the spitfire i would see it on the glass but not in tbe things right in front of me. If you're not throwing your head around like a maniac you probably wont see it. Earlier ive been flying the Huey with everything set to high and i havent noticed it a single time before i actually did this test now. Never noticed anything flying the F18 either. Tried the Huey again now and nope, just noticed some slight distortion throwing my head around like crazy
  11. Ive forgotten how it was on the rift but i remember 45 fps asw = ghosting might have changed so do correct me. Then i tried VMR motion reproject motionvector stuff that feels like 90 fps, i cant tell the difference. I hope it will be that kind of quality. i just cant go back to anything else now.
  12. Edit steam\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings Make sure this line is set to motionvector and not auto and ofcourse remove the // infront of it. "motionReprojectionMode" : "motionvector", uncomment this one too"motionReprojectionTemporalEnabled" : true, I havent really done any testing with it but performance is fine so Feels just like 90 fps to me. I got it on in X plane too, amazing there as well. Can copy/paste { "driver_Holographic" : { "renderTargetScale" : 1.0 }, "driver_Holographic_Experimental" : { // Motion reprojection doubles framerate through motion vector extrapolation // motionvector = force application to always run at half framerate with motion vector reprojection // auto = automatically use motion reprojection when the application can not maintain native framerate "motionReprojectionMode" : "motionvector", // Automatic motion reprojection indicator to display the mode currently selected // green = off because application can render at full framerate // light blue = on because application is cpu bound // dark blue = on because application is gpu bound // red = off because application running at less than half framerate "motionReprojectionIndicatorEnabled" : true, // Use temporal history to get higher quality motion vectors. motionReprojectionMode must be set to 'auto' or // 'motionvector' for this setting to have an affect. "motionReprojectionTemporalEnabled" : true, // Some people may experience increased discomfort such as nausea, motion sickness, dizziness, // disorientation, headache, fatigue, or eye strain when using thumbstick controls in Windows Mixed Reality. "thumbstickControlsEnabled" : false, // true = use thumbsticks for artificial turn/move, false = default application thumbstick behavior "thumbstickControlsReversed" : false, "thumbstickTurnSmooth" : false, "thumbstickDeadzone" : 0.25 }, "NoInterEyeRotation" : { "DOOMVFRx64.exe" : true } }
  13. Yeah I don't get it. It just went mental on me for no apparent reason
  14. All hell broke loose for me. Apps hangs all the time. Sometimes I canctrl alt del and go back and I can click stuff again. Wmr app and steam vr hangs all the time. Complete chaos after Installing that shit. It just got worse and worse and reset windows 3 times. Couldn't revert. Had to reinstall 1803 after deleting my c drive cause it wasnt gtp and refused to install. Had no issues since. I'd wait a while before installing
  15. Interested in buying the Virpil T-50 stick and base. Preferably from Europe.
  16. I honestly dont notice any difference between a normal SSD and a m.2 nvme drive in load times for DCS or anything else for that matter. The rest of the system cant keep up and i got the top of the line stuff. Maybe 5 years from now. Im actually returning my m.2 and pick up SSD's instead so go with SSD if ur upgrading
  17. I find i need to force it on for it to work but the result is just amazing, 45 fps that feels like 90 with 0 ghosting
  18. Working after update
  19. Been getting this crash on startup. This is a fresh install of windows 10 pro Tried changing ram, disk repairs, DCS repair Windows 10 i7700k 16gb ram Nvidia driver 411.70 Dcs 2.5.2 (currently downloading 2.5.3) === Log opened UTC 2018-10-05 12:43:38 2018-10-05 12:43:38.536 INFO EDCORE: try to write dump information 2018-10-05 12:43:38.538 INFO EDCORE: # -------------- 20181005-124338 -------------- 2018-10-05 12:43:38.539 INFO EDCORE: C:\WINDOWS\SYSTEM32\ntdll.dll 2018-10-05 12:43:38.540 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 2FCB5EBD 00:00000000 2018-10-05 12:43:38.542 INFO EDCORE: 00000000 00000000 0000:00000000 2018-10-05 12:43:38.545 INFO EDCORE: 2FCB5EBD 00BEF580 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlEnterCriticalSection()+D 2018-10-05 12:43:38.547 INFO EDCORE: E9BE45AF 00BEF5B0 0000:00000000 C:\games\DCS World\bin\physfs.dll PHYSFS_setWriteDir()+1F 2018-10-05 12:43:38.548 INFO EDCORE: EC2C3D8D 00BEF5F0 0000:00000000 C:\games\DCS World\bin\edCore.dll ?init@InitPhysfs@core@ed@@UEAAXXZ()+2D 2018-10-05 12:43:38.549 INFO EDCORE: EC2C545F 00BEF630 0000:00000000 C:\games\DCS World\bin\edCore.dll ?init@Initializer@ed@@QEAAAEAV12@PEAVIInitObj@2@@Z()+3F 2018-10-05 12:43:38.550 INFO EDCORE: F31A48A2 00BEFE10 0000:00000000 C:\games\DCS World\bin\DCS.exe 2018-10-05 12:43:38.551 INFO EDCORE: F36D41E3 00BEFE50 0000:00000000 C:\games\DCS World\bin\DCS.exe 2018-10-05 12:43:38.551 INFO EDCORE: 2D947E94 00BEFE80 0000:00000000 C:\WINDOWS\System32\KERNEL32.DLL BaseThreadInitThunk()+14 2018-10-05 12:43:38.551 INFO EDCORE: 2FD07AD1 00BEFF00 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 2018-10-05 12:43:38.647 INFO EDCORE: Minidump created. Event viewer Faulting application name: DCS.exe, version: 2.5.2.20785, time stamp: 0x5b7bf6a7 Faulting module name: WorldGeneral.dll, version: 2.5.2.20785, time stamp: 0x5b76d3e7 Exception code: 0xc0000005 Fault offset: 0x00000000000564e4 Faulting process id: 0x2344 Faulting application start time: 0x01d45ca9099ec8f6 Faulting application path: C:\games\DCS World\bin\DCS.exe Faulting module path: C:\games\DCS World\bin\WorldGeneral.dll Report Id: ca2cc743-efad-4908-bff6-a6b6847db25c Faulting package full name: Faulting package-relative application ID: DxDiag.txt Logs.rar
  20. Forget the rift and get the odyssey. It might not be as comfortable and not the biggest sweet spot but the added clarity more than makes up for it. I can read 99% of the text in the Huey now. No chance with the rift. My 2 cents. I’ve had all the hmds. Also np with those specs
  21. set 3 screens instead of 1 screen in graphic options and you wont have any distortion. If you have done that already? and its on a odd angle, angle your physical screen and play with the zoom. Guessing you are still at one screen in the options though Now lets get back to the topic ;)
  22. From what i hear from this review currently the 5k+ has a better looking image/clarity than the 8k version. might change with later panels though. Its all really really promising Edit: I see its mentioned earler too. Ill probably go with the 5k
  23. Cheers, ill give that a try
  24. Will Deffo be checking this out. I'm mainly a whirly bird pilot and love sling loading and such. I'm just dying to get more fov even with some slight distortion. Try hovering looking straight down in a heli on the current stuff, it ain't easy! Would happily go with the Odyssey res with 170 or 210 like the starvr to use my peripheral vision.
  25. Sell both and get a Odyssey if you only do flightsims ;) Pros and cons with both but I went with the Rift in the end. For me it had better sweets spot and clarity. Slightly smaller pixels on the display than the vive that gives a minute better image. It's also lighter and better for extended use. God rays way worse though. Just use them both a bit and decide for yourself really. Both have a tech like asw but oculus is slightly smoother perhaps but nothing I really notice. Odyssey use steam vr and I can't say I have any issues with judder except when it tries to boost from 45 to 90 sometimes. Then it can go to 55 60 and back to 45 again. This you can lock to 45 with the Rift software if it does that there. Not 100% sure on steam but trying to find out. If ur doing rooms scale too then go with the vive. I'm on a i7700k 5ghz and a 1080ti
×
×
  • Create New...