pchRage

Thanks for clarification!

Is the pilot body not (no longer?) modeled in the F16? I've hit the command, RShift + P but it doesn't load the model/texture. 2D or VR.. nothing...

Ugh! Well my Throttle just seems doomed. :surrender: The microstick is just cursed. :disgust: I got the last remaining spare in the universe from Habu_69 (thanks again!), brought it to a electronic shop to desolder and replace last week. Expected to pick it up and re-assemble cougar that day.. then I get a phone call... They had their iron on too high and burnt out the PCB board! :mad::mad::mad: :furious: Fast forward another week, and I get a call that they have repaired/retraced all the burned lines on the board. I reinstall/reassemble.. plug in... and go to calibrate... same poor results (probably exact same) as before. :confused: The Y and X axis are somewhat registering in TUSBA software, but only the X axis Forward is showing in Joy.cpl correctly. Center is off, Y axis no movement in Joy.cpl. The button depress is fine. Between the replaced Ant control, Elevation control, HAL throttle sensor, TUSBA R2, and Microstick + labor, I'm probably $250 into getting this thing refurbished. I guess the nostalgia is wearing off due to the time and frustration. :mad: Attached are five pictures of what the TUSBA reads vs joy.cpl as an example in case someone runs into this in the future too. I drew little Red arrow to indicate what each app is registering. Maybe its the main board, maybe its some wire issue, I'm at a loss.

Thanks for clarifying all that VpR81. Does anyone have both the WarBrd and the T50 base that can comment on their relative centering/cams?

thanks for the feedback. I see some recommend the warbrd, some the T50, some "virpil" and some VKB. hmmmm. :-) Something new I learned with that the Virpil bases require an adapter.

Its been a year since I posted this (https://forums.eagle.ru/showthread.php?t=225419), is there now perhaps a lua file, setting file, etc that will allow me to change the vertical position of just the JHMCS? Ie i want to move the projection of the HMCS down about 15-20 degrees to what my eyesight considers "in the middle" of the visible VR display. Tired to staring/straining "up" to use these in the F18/16. Again, seating position is just fine, hud fine, its only the helmet displays. If there isn't a setting file, could this please be added to the "Wish List"?

I've had my warthog stick for many years and its starting to develop some play, especially from a "yaw" perspective. I just put on the TM F-18 grip and re-using 7mm extension and its great...but... I center stick with the F18grip for flying the f18 (occasional p51 and f15), and move it to side stick for f16 with the original warthog grip (I may just get a force-based side stick...but not to derail this thread!) Ultimately, I like a strong center with zero play and no need for deadzones or curves in the axis tuning. No preference (I don't think) on either a linear or progression spring from 0 to full deflection. I've read a bit about the Warbrd, T50, and VKB offering, but unsure what direction to take, if any.

I'm in the same boat DataHawk. I refurbished my whole throttle (new ant, elev, and hal sensor, plus tubsa for direct usb usage without stick). I tried to get a replacement microstick and went a few rounds with their customer service to ultimately get the "no go" result. Here's my thread on it: https://forums.eagle.ru/showthread.php?t=246261 Net net, I ordered a few microsticks, but they didnt match the hat/cursor, and they do not use the board, so no way I could see to get it to "stay" in the proper slot/alignment. While Debolestis could probably make a new hat/cursor, I have no idea what to do about the board/connectors. I'm barely adequate with soldering wires onto the switches, so I'm hoping someone comes up with a ready-made solution :-)

100% same issue on MP with VR Index. 45FPS VR stable without DL page visible, toggle to it, dive down to 25 fps. FCR page has no affect on FPS, on the HSD/DL

thanks for the feedback, maybe i'll skip a gen and wait for the 30x

Do you think the firmware flash only affects the stick, or the throttle as well? I've put $$ into upgrading the throttle only, but the microstick is a fail.

With Cyber Monday coming up soon, I'm debating upgrading my video card to a 2080 (Super or TI), and the power supply to handle it (500w to 650w). An MSI 1080 OC'd (+110 core clock, +75 mem clock) is currently powering my Valve Index. I know we are cpu rate limited, but I'm wondering if the 2080 will allow me to start using MSAA, etc etc for better clarity (I know it won't change the 45fps ASW world we all live in). Upgrade Yes/No? If Yes, the Super with less ram but high clock rate? If Yes, the Ti with more ram but lower clock rate? ...Or wait another year for the inevitable NVidia 3080 :-)

I noticed that the HMCS is projecting in the LEFT eye instead of the RIGHT. I double checked the settings and it is the default, RIGHT eye. I also loaded the F-18 to cross check: it is showing properly in the RIGHT eye. Seems the F-16 is projecting the opposite... This is in VR, Valve Index...

I have the Cougar Throttle and WH stick setup, but my microstick on the throttle I've been "dealing with" just up and died, the pots are just fried. Anyone have any drop-in replacements?

Timing is everything! Day before F16 module comes out, and I think the microstick just gave up the ghost! Anyone happen to hear of any news in last month as far as someone making a drop-in replacement?

Well I decided to move back to 4.8MHz instead of 4.9. The temps were still fine, rarely a spike over 80c, but running 1.4+ vcore just felt iffy. 4.8MHz takes me back to 1.3v and that 100MHz delta doesn't seem to make a perceptible difference. I'll prob jump on the 2080 Super or Ti bandwagon around Black Friday/Cyber Monday (plus a larger PSU), maybe by then the drivers will start to net out some cost/benefits.

thanks @Nagilem Yea in other thread I had a weeks-worth of troubles with WMR settings mucking with Index. What I did find last night is I missed 1 setting in DCS, the Terrain shadows! I had dropped my previous saved settings in DCS to wipe out WMR remnants and missed that one. I turned it off and immediate got back closer to spec. I then moved from 80hz to 90hz. A setting I found works better for me in SteamVR is to DISABLE (always off) the Motion smoothing. I saw Wicked.- great comment on removing Hyperthreading in bios, and will try that. I'm also testing my I-7700K from a default of 4.5mhz to 4.9mhz (100 more than the default MSI "game mode" of 4.8). So now I'm running 4 cores vs "8 HT", and 4.9... Will test a burn in with DCS and see if the temp exceed 80C (no watercooling...). EDIT: Regarding your comment "@ 90 hz you want the game to operate at >18-19ms for 45 fps." I check and when I'm in the weeds I see locked 45fps, and my ms is ~"13.1 of 11.1ms (90 Hz)"

well now that I've solved my 2x vision issue with that "raw" I'm now trying to dial in the perf...or serious lack thereof. with the O+, I am able to run 160% and hold 45fps 99% of time. With the Index, I have it at 100% only, and 80hz, and I can barely hold 40, often its jumped into 20s or 30s on MP. All the other settings are the same. Latest nvidia drivers, steamvr beta, etc. I didnt think the screen resolution was much larger in the Index...?

Baldrick33 you are a genius! I found that file: \Program Files (x86)\Steam\config\steamvr.vrsettings It did not have that renderCameraMode line at all. I put in the "raw" value, and spun up DCS. Immediately on the main menu I could tell it was better. Spent a few minutes on the ready ramp re-dialing IPD, Lens distance, and positioning HMD and I can see!!! Switched back to 90hz mode and lowered the scaling to keep 45fps and did a free flight. After that I dialed in a simple AA mission where an F14 hurtles Phoenixes at me. I CAN SEE..them slam into my plane! :-) Thank you and everyone else with your suggestions! Much appreciated! Now I can spend some time attempting to dial in the best fps/res options!!!

Well I tried that out... I don't think it affected it. I've even tried 80hz vs 90 vs 120 vs 144... i think its just those canted-lens + sweet spot are not behaving well with DCS. Such a bummer, everything else about this Index is amazing, but I cannot handle the double vision. I figure I have a week to solve it, else back it goes :-(

thanks Nagilem. Will try that out!

Good idea Nodak! I never made any adjustments, always X'd that thing, but it could have set some defaults somewhere. Any idea what/where that file(s) may be?

downloaded a few more free VR games and tested.. they are fine. sweet spot where expected, no double vision, etc. I've further uninstalled WMR, steamvr, cleared windows Environmental Data, deleted all SteamVR left over folder settings, and then reinstalled SteamVR. Tried with primary and beta version of steam vr...no diff. Its definitely something specific to DCS. Only next option I can think of is to delete DCS entirely and then reinstall and try. Other than the main program install location, and the saved games area.. are there any other areas to scrub (registry, appdata, etc)?? thanks!

Yes, button-hat == cap. That circuit board in the existing microstick helps "keep it in place" in the handle. Then there is this small black clip/shim that goes over it and further locks the stick into place. I think without that and just direct wires will mean the switch is floating around in there.

Thick8 I would see that same screen with my Odysssey, but now that I think of it, it does NOT show for the Index. Maybe its a WMR-only thing. I downloaded a few different free steam vr apps (google earth, msi shootem-something-or-other). For those, i see no issues, same with the "Window house". It only seems to be DCS... Edit: I also did a dcs repair/cleaned meta folders, no effect