Rainmaker

How exactly are you getting 21.3 AoA (HUD is CPU FWIW) and a VV still in the in plane view in the HUD? And horizon line has nothing to do with it.

Yeah, there is a lua config line that allows for exporting MFDs in VR. Something to the effect of ALLOW MFD EXPORT IN VR. Part of that is also enabling the repeater to match the combined screen res of it all, so they did something on the DCS end to allow it to extend to all screens in VR. Since you don’t use VR, that doesnt look to be the issue obviously, but that’s the only time I have seen it. When I was playing around with it, I found out how to change the config for the UFC and the MPCD, but unfortunately that made the backgound occlude the text on the MPDs. It is a bit strange that suddenly popped up for you. In non-VR, my screens still just go to a black background since as you say the game is not extended to those. Pretty sure it is something to do with the lack of the MFD background baked in, I just dunno how to fix it, at least not without causing other issues.

I have not. Hard to tell from the photo, but are they transparent? The time I have seen that issue is with full screen VR. The backgrounds are not black, they are transparent currently which makes it dependent on the 3D world not being projected on those monitors. Using the line in the monitors config to export displays in VR will cause that.

I think someone has said that it is a thing, but network hardline is the only alternative at the moment.

I have yet to beat the cable overall. My litmus test is usually flying down vegas blvd at 500 ft and looking out to the sides. Everything else thus far will give me missed frames, ghosting, etc. i wanna get MR going as there are some descent options available, but I don’t wanna give up quality. I know it somewhat defeats the bigger purpose, but I wish VD had a link cable option.

Well, without a track or anything, not much anyone can do to diagnose.

Well, the no scan thing is related to a DLL bug and the new year according to the devs. Someone just posted the same issue on discord earlier and was on a way out of date beta version. I would begin there. Process of elimination considering its certainly doesnt appear to be a wide-spread bug. Update, mods, etc.

Stable version bug. Known issue. Have to use Beta or wait for next patch.

IIRC, and don’t hold me to this 100%. Q3. Start VD, run the hand passthrough software which also starts steam, and then I think I started DCS via the desktop shortcut, which still had the OpenXR command in it. Like I say, not sure what the runtime was actually set to at the time as I was just playing around with it trying to see if I could get the passthrough working and not paying attention to much of anything else.

You think the lack of datalink stops combat? You’d be sadly mistaken. The jet spent over 15 years of its life in combat without it. Other jets went longer than that.

It continued in Discord. I think he’s sorted. There was a little more pieces to the puzzle that I think caused some secondary effects.

I gotcha. Yeah, I didnt have issue running both, but that’s just my experience which is only one person. I will easily admit I dunno what those applications do when it comes to what being used to open what and what is actually using openxr, etc. For me atleast, I can only say I started DCS from the desktop and have the openxr command still in the shortcut. Was that the proper way? Not a clue.

I havent tried that one, but I did try the freeware utility that just does the hands and it worked pretty much exactly like what was in his other video. The whole concept seems ro have a lot of promise once someone really starts to natively adopt some of this stuff so it doent require so many steps to get it running. If you are having stuttering, I would focus on troubleshooting the network connection or the graphics settings in VD/steam. Its been a week or two since I did it, so not sure which one ai actually had as the openxr runtime TBH. I did notice that the presets in VD makes everything run higher than what the Oculus app was running them when running the same frame rate setting.

The TGP knows true elevation, so something is not quite matching up with what you are saying in your post. The radar only knows what is loaded in as a ref altitude for the steerpoint In short…really need a track.

I use a USB HUB that has on/off buttons just beside the ports. Its not a perfect solution, but it works well for when I dont want to use them or have some other game that they cause issues with. Mine is a 7 port so it works for the displays and the controller side as well.

Its a caster wheel so there is some natural centering if going farward. Like above, the effects of doing such things aren't as bothersome as IRL as everything is perfectly balanced out. There is a dampener modeled, but its never going to fit everyone like with the stick and things like extension/no extension, curves are going to be your biggest friend.

Yeah….holding the paddle removes all centering hydraulic pressure from the nose wheel. Its definitely NOT what you are ‘supposed’ to do.

TF radar was turned on.

Yes, that’s actually what I did last night. That worked. Its a windows limitation of where it allows the mouse curser to move inside the display limits. I think I might have a work around if the NVIDIA control panel allows me to set a display group and give them really huge bezels and allows the mouse curser to pass along the bezels. I havent tried it yet, but I know it used to be a thing back when I had triple monitors and eyefinity years ago. Its a long shot, but that might work. Otherwise yeah, I might just be stuck moving displays to certain positions to allow the mouse curser to move there. The other option might be seeing if the UI allows hand controller use in the UI, been years since I have messed with that. I’ve git some ideas, just need some time to dedicate to playing with it.

Appreciate the help, but this one did not address the issue for me with my setup. For whatever reason, on my setup, it does not allow the mouse to travel down far enough to click in the lower right corner. It's not that it goes out of focus for me, it's that the render and the mouse cursor limits for whatever reason are different.

Pod is going to get reloaded during rearming. More like a DCS-ism I would say. Pretty sure all modules do this?

TOF of last weapon release. Last weapon equals closer to target/shorter flight time.

For the time being, you’ll likely have better luck giving them a manual impact angle instead of letting the bomb decide, use a default, or whatever the bomb does when you don’t tell it what to use.

Guiding a bomb apparently works beyond the old setting, but the ranging number on the MPD is still relegated to the 8. Whatever range.

IIRC, yes, once it sees the new spot, that now becomes the new target. If you cease the lase, it continues to that same spot. Don’t take that as gospel, but that’s how I remember it. The bomb necessarily always see the new spot though as it has ai seek FOV you need to abide by.