Jump to content

Sr.

Members
  • Posts

    1703
  • Joined

  • Last visited

Everything posted by Sr.

  1. watching
  2. X-56 throttle is all I currently have of the set. I had to perform this reset a couple times in the past to get things untwisted. Also, I used to get bad ghosting with the throttle until I moved it to a powered USB hub. Word of caution: Throttle Axis calibration process for Throttle: 1.Move all axes to max and min twice. 2.Meanwhile make TGL4 down,TGL3 down,TGL2 up. 3.Calibration is completed when all lights go out. Clear axis calibration process for Throttle: 1.Meanwhile make TGL3 down,TGL2 up before device power on. 2.Meanwhile make TGL4 down,TGL3 up. 3.Clear calibration is completed when all lights go out. Stick Axis calibration process for Stick: 1.Move all axes except x/y axes to max and min twice. 2.Move the X axis to min and meanwhile press the buttons Trigger and B and D. 3.Calibration is completed when all lights go out. Clear axis calibration process for Stick:: 1.Meanwhile make button A down,HAT1 up,Flying Pinkie down,Mini stick button down. 2.Clear calibration is completed when all lights go out.
  3. Sheesh... I've spent the better half of an hour breaking things. Does anyone have a lua file that simply allows my LEFT 1920x1080 monitor to be my MAIN display, while the RIGHT 3440x1440 run DCS full screen. I really don't care to have my map, kneeboard or anything outside that display. I would love to be able to run a youtube tutorial video on my LEFT (MAIN) display to follow along in DCS while playing.
  4. Update. I would suggest finding a decent profile to build on. Took me about 20 minutes to polish mine up. It ain't VR, but damn smoother that I expected for a home-made head tracker and $10 PlayStation camera. Tried face tracker... it's close but nowhere near as smooth. I will try better face lighting later.
  5. I will tomorrow when my new monitor shows up Did some fiddling with it on my current monitor and looks promising. Using a home-built sensor.
  6. You should give the "newer" FacetrackNOIR a look. I just set mine up following "Juice" videos. Pay attention to the files he mentions in the description. And his follow up on adding 10 to the axis curves in DCS controls options.
  7. wow... I'm sitting here literally considering going back to pancake mode. I spend far too much $$, time and effort constantly jacking with VR settings. Seems 95% of my time has to go to optimizing, fiddling, testing, patching when I should be flying. And to be honest, by the time I'm doing doing ALL that, I've lost the mood... It's almost like "making it playable" has become "the game."
  8. Sorry to Hijack... I'm experimenting with FacetrackNOIR. set it up based on the videos by Juice. So far everything is great but for the shortcut keys I've set to 'center' and 'game zero' are having no effect IN DCS, only while the FTNIR screen is up.
  9. Did they add sandbars to the river next to Batumi airfield intentionally?
  10. Well, I can report my stuttering is gone and my frametimes are back to what I would expect them to be(having always run at 60HZ). No frame rate dips into the low 50's now. I gave 90HZ another try... looks amazing and while any stutter I had before (non MR) which was unplayable, is now best I can describe like motion blur, seen only if banking or rolling very hard. This was flying FA-18 free flight over Batumi. I will enable the record stats feature this evening and get some data with/without Turbo mode if anyone cares to see it. BTW, where are these logs stored? Is the OpenXR Tools For Windows Mixed Reality from the MS store the proper one?
  11. I noticed that while the aircraft ground shadow is gone, the vertical stabilizer shadows are still being cast onto the aircraft itself. FA-18 for example.
  12. While I was home for lunch, I clicked the update. It downloaded a patch I assume. I hoped in FA-18/Caucuses ready on the ramp mission real quick to check and, the over-lap/superimpose aircraft shadow bug had been fixed. So I re-enabled shadows low/default and performance was 'better', just still not 2.7 GPU frametimes... but better than it was last few days with same shadow settings.
  13. While I was home for lunch, I clicked the update. It downloaded a patch I assume. I hoped in FA-18/Caucuses ready on the ramp mission real quick to check and, the over-lap/superimpose aircraft shadow bug had been fixed. So I re-enabled shadows low/default and performance was 'better', just still not 2.7 GPU frametimes... but better than it was last few days with same shadow settings.
  14. Update: I have found turning Terrain Object Shadows OFF gives a little relief. I have also noticed the weird effect where the shadows of aircraft and other vehicles is "inverted" so to speak. Not being cast by the object, but onto the object depending on the view angle.
  15. It's perfect now. Before I was using the throttle joystick in axis mode. Crazy hard to fine tune.
  16. Curious if you ever applied the firmware update to address the early issue with the G2 wherein, the headset would crash if the system volume was too loud. (like over 55%)? Short of that, sounds like you have a cable malfunction. Probably near where it attaches to the port on the headset. The wires inside the bundle are tiny and not bend friendly.
  17. Yep. I run my G2 at 60Hz, counter shows 61fps 99.9% of the time, so there is rarely enough going on in a map that causes mine to even dip 1 or 2 ms. Even running high texture settings, full res in OXR. Since switching to 60 last year, I never see a "stutter", even flying inverted through Dubai. I can even run 90Hz if/when playing NTTC (Nevada) with the same performance. Last night, I hoped in to the FA-18, F-16 & A10-CII to check performance in Nevada... it was perfect as before until I grew near of anything casting a shadow, then immediately dipped to 47-49,50 fps and the stuttering kicked in.
  18. I've tried it, but haven't seen a noticeable difference. What % you recommend?
  19. I use it to slew cursor. Would love to slow it down a bunch. Something like this?
×
×
  • Create New...