Hammer1-1

I did the same thing but like 8 months ago. I tried a zip tie first but I didnt care for the scratches. My next VR set will NOT be an HP; Ive went through a G1, 2 G2's, and 3 cables between the last 2. All in honesty though, finding that VR isnt really worth the aggravation, so when this headset dies Im headed back to TIR.

On the TSD screen, upper row, youll have a SHOW button. Click on that, click on CPG cursor on the left. That will show his cursor on the screen. If you are looking to see where the TADS is looking at on the map itself, I believe you have to make the GHS as the acquisition source, but I dont believe it shows up on the map display. You will only see it in your IHADSS afaik.

You can adjust your view with the rctrl rshift and numpad digits and make it more natural, and your alignment will still be way off, and Ive yet to see snapviews work in VR. Not saying it doesnt, just never seen it work.

OBS records from SteamVR, not WMR. Wish there was a fix for that myself as I would love to start streaming in VR but until its better optimized...

Looks like you're right; I thought I had uninstalled that aircraft since I never use it and I didnt see it in my mods folder until you said something. Never even used the mod!

Yeah theres a lot of errors in this log for some reason, but dont really see anything regarding C-130 sounds. dcs.log

Did a repair, did an update, and still sounds like a turbojet. No change.

Nope, I dont get any sound really. Ill get a video capture of it later today, but its a barely audible turbofan sound. Also, no sound mods.

Hearing the C-130 engines, there are no propeller sounds and the engines sound straight up like a turbofan instead of turboprop.

Believe I may have corrected my training missions. Went into the ME, campaign options, unticked show labels and saved. The game mode tick box was unticked already, thinking they TRIED to fix it already but it got bugged somehow.

Same here, but I read there was a fix you can make with notepad++ and you can edit the mission from there.

I just flew for an hour in the SA map in the Hornet. Average fps was around 35, dipped to 23 in some areas and as low as 15 around ushuaia. Wasnt all that stuttery though, but I only toured the south end of Argentina. Some of the airports still gave me some serious stuttering, but just around the airports. This map still has a long way to go...

Ill do some trial runs this afternoon too and report back.

I kinda like not having to deal with a sine wave on the drogue system; I can think of many good reasons why I dont wish to rip my joystick from the mount and throw it through my monitor because I paid a lot of money for these.

Ive flown with a VKB MCE Ultimate, Virpil T-50CM3, TM Warthog, Saitek X56 and some old school Saitek X45 joysticks with aerial refueling. Never used a curve to do it. If you've never used a curve, dont. What you SHOULD learn is how to finesse your joystick with micro adjustments; the trick is to make your joystick as comfortable as possible and that means positioning it in a natural position. Sitting it on the side of your chair isnt going to help things UNLESS its an FSSB joystick and you're flying an F-16. It should be between your thighs at waist height where you can put both hands on it and fly with your fingertips like its meant to be flown. Finesse is flying in formation with fingertips, not dampening movements with curves. It just takes time and patience.

ok, ummm...not to be that guy, but can I get a petition started to change the title of this thread to its correct spelling?

The F-111 is closer to a B-1A than an F-14 IMO.

I get the point not to fly in lockout...but when I did, I got those results: a 2000'/min climb rate past 10,000' with a full load. Thats my issue at the moment. Is that how its supposed to work? I understand not to do that...but...

Approaching 10k' altitude and heavy loadout (2x fuel bags, 8 AGM-114, full fuel), pushing the throttle past the lockout position gave me a 2000'/min climb rate. Basically had too much power to make a landing at that altitude, but when backing the throttle down below the lockout I kept getting an engine rpm low warning. I couldnt safely land with it engaged as I kept ballooning and I couldnt safely land without it engaged because I didnt have enough power. https://drive.google.com/file/d/1xM-dt28JUrZg994jnuB7VrTqzjlId2md/view?usp=sharing

should look like this Yeah but out of all the people who used it, does the vast majority actually perfer it or say anything? I dont know, maybe something was updated recently that makes it more user friendly but the first method was practically fail proof - and still works 100% of the time. If its simple, fail proof, and even an idiot can do it the first time around (like myself) then IMHO thats perfect. So whats the actual difference between the first iteration and the newest with regards to performance? Im just curious, thats all.

openVR stuff.rar Here. Read the first post and accomplish steps 1-6 EXCEPT #3 + 4. Then drag and drop these files into your DCS main directory. Dont bother with the OpenComposite file in here (honeslty you just really need to drop d3dCompiler_47, opencomposite.ini and openvr_api into the bin directory) , just leave it alone for now. Start DCS normally and let it open up WMR and see if that works. And to be bluntly honest, this method should have been left alone as everything newer than this just got complicated for no reason. Not sure if the shaders I have in this file still work, but thats an easy fix.

Id like to point out that you dont really need sky spaces to get it to work. However, its a bonus. All it does is free up an extra gigabyte of vram and that allows a little bit more leeway which causes the GPU frametime to spike. If you installed OpenXR correctly, all you would need to do is start DCS in VR with WMR running in the background...and even then if you launch in DCS, it will automatically deploy anyways. All you really need to do is make sure that Open Composite is installed, your PD is set to 1.0 within DCS, OpenXR tools installed and a custom render scale at 90% or lower, and that your d3dcompiler_47.dll was deleted. You dont really need the OpenXR toolkit for VR to work. You also dont have to delete the shaders; its preferable that you do, but not really. Thats been the norm for many months now, but it used to be mandatory. Be prepared to wait if you do though... If you have WMR to run without starting steam, all you need to do is just load DCS and the rest is automatic.

well each option has its own quirks, so its going to be whatevever you like the best out of the options. However, it hovers just fine and rock solid if you trim it up right and hit the altitude and heading hold.

Well it kinda looks like to me you started DCS from within the WMR desktop app and not the other way around. The only time Ive ever done something like this was when I just randomly tried to play grand theft auto online in VR using the desktop app and thats exactly what it looked like. Go into the VR tab in DCS settings and make sure that VR enable is ticked. You launch DCS in VR, let it automatically load WMR for you and itll take you straight into VR.

So its not running in VR, its running on desktop THROUGH WMR.