RealDCSpilot

I'm also surprised and disappointed of the 3D model quality and textures in 2024. This is max. 40-50 bucks territory. Also when it comes to system complexity and weapon variety. It's not that much. Premium price makes me expect premium quality. When i look down, out the window in VR and see the texture resolution of the skids... It shows.

VPforce Rhino here and it works as expected. You can even switch off force trim with the cockpit switch and the spring forces get disabled.

Yeah, needing to revert the force setting for Y axis on certain modules is something i remember from my old G940 back in the days...

@KomandorAdam Are all settings correct? F-4E special options -> the first two checkboxes need to be unchecked! (stick deflection limit and stick force blending). These are for spring-centered sticks to mimic the real behaviour. Globally in DCS Force Feedback must be checked of course. Works perfectly well on my end. The Phantom has one of the best FFB implementations for planes in DCS. And i read the team is getting hands on a Rhino soon, makes it even more interesting what will come out of this later.

Oh, i'm only talking about DT delivering mode and Pave Spike operation. Air to Air radar is another problem... Getting locks is like playing a lottery. There is still a lot of work to do for HB.

@JNelson I tried to replicate the problem with unticking the full screen setting, without success. The erratic behaviour seems to be gone for good on my end. That's not really good news i guess. All i can tell is the conditions before and after i ticked the full screen option. I've been playing VR since more than 6 years now. Never used full screen mode, so this option was unused since years or at least since my latest re-install of DCS on this machine 1.5 years ago. I was testing the DT mode and Pave Spike since release of the F-4 and actually gave up on it until i found this thread. And i really tried hundreds of variations delivering bombs in those modes in the past days seeing all kinds of strange reactions of the radar ground lock, jester callouts and failed automatic release timings. I even tried to manipulate the pattern table to force a huge release advance to prevent the overshoot of the bombs. With the Pave Spike it only worked with a good amount of lead in front of the target and manually moving the crosshair back on the target once the bombs are in the air. I can only conclude that something deep in the bowels of DCS got triggered by switching to full screen in the system options. I hope you can find cause.

This also greatly improves the handling and tracking of the Pave Spike and dropping GBU with laser targeting. The bombs are released at the right moment now. Just had a 100% hit rate with dropping all sorts of GBU.

@FusRoPotato @JNelson FusRo... you need to get nominated for the Nobel Price for finding that DCS bug deep in it's bowels with out-of-the-box thinking! You actually only need to set this. In VR my desktop mirror is still a small window, but all of a sudden my bombs hit exactly where i want them and i can also pull the stick before the drop to make a toss release!

On my end, testing GBU with the Pave Spike seems to have the same problem. The calculated automatic release is always a bit to late. The bomb overshoots and can't catch the laser. My workaround is to aim with the Pave Spike something like hundred meters in front of the target, let the WRCS do the drop and manually move the Pave Spike slowly onto the actual target after that. Then the bomb catches the laser guidance and hits.

It's not recorded in VR, this is the 2D IHADSS used with TrackIR. The IHADSS in VR is rendered differently. In 2D it's just a simple overlay.

@Kronstadt Well, in your video you forgot to at least give Target Altitude and Dive Angle some numbers. So that the Drag Coefficient could be calculated and gets a value ~1.01. This is crucial as far as i've been told, but altitude and angle don't need to be achieved with the actual DT drop.

Tested a little further. On the bombing range in singleplayer. If i keep the pipper steady on the target until the bombs release i can actually hit something. What never works is pulling up until automatic release (the "toss"), here the bombs always go way to long or elsewhere... as if they are released to late.

Maybe unrelated, but i have also never any successful DT drop in VR. (It's kinda multi-monitor, a screen for each eye...) Double checked each step of the procedure, does never end up like seen in certain youtube tutorials. Sometimes Jester also reacts very late to the context action command, or screams "not able" or the reticle is strangely wandering off the target i point it at. I do all my weapon tests in multiplayer.

The "auto hover" is only a "ingame" software helper. The real machine doesn't have this functionality. IRL pilot and weapons officer have to work together. Normally, the pilot brings the Gazelle in a stable hover, hands over the tail rotor control to the weapons officer's sight (Viviane) but still keeps control of collective and cyclic. The autohover feature is basically the same as the autopilot in the Huey. It's a virtual AI pilot stepping in, but you have to meet his conditions. On my end, i never use it. It's very easy to control everything manually. The doctrine of becoming a stationary target in the air is also outdated since anti-air weapon ranges increased. Keep moving - keep surviving.

Yeah, having to bind extra buttons, which are a rare ressource, is not the ideal solution. Especially where smart software logic could do wonders. --- Please don't derail the thread. Of course, the help of Zabuzard is very welcome. But we are here to make the F-4E a better product.

Issue: My trim is not working on the ground, the stick is either full forward or full back and when I trim it does not change position. Fix: This is correct as is on the ground. The bellows system pulls at the stick with increasing airspeed, while the bobweight system pushes the stick forward with increasing G. In flight and when you are trimmed out well, these forces roughly balance each other out naturally. On ground however, the bellows measure airspeed 0 and hence do not add any force that would counter the bobweight system pushing the stick forward. You also will not see trim doing anything in that situation, since the trimming merely changes the length of the lever to which the bellows can apply force to the stick and do not move the stick around directly.

@Zabuzard I'll try to be more precise, i hope it makes it more clear. Most throttles have this one little analog stick, right? Very practical for radar cursor slewing, weapon sensor slewing etc. right? Right now i can bind this only to Jester UI X/Y or weapon slew X/Y. I can't bind both. So my suggestion is to make it usable for both functionalities(!). If the Jester UI is open it works as Jester UI X/Y and if the Jester UI is not open it works as weapon slew X/Y. Should not be a big problem to code.

THIS! (also a problem in the F-14) It would be so much better if it worked in every direction you are looking at the moment you are pressing the menu button. Another QoL option would be to be able to temporary use the analog axis of the weapon axis stick to navigate the circle menu and to use the jester context button to choose the targeted option. At the moment the control via head movement is very unreliable.

Is that "realistic" and intended?

I have all modules, mainly going for helicopters and jets. Sadly warbirds are getting not used as often as i would like. "Lower force mode" is what i only know about expensive and general lower force Brunner bases, but i can't remember that it ever happened on my Rhino(?). However, the fans do kick in on longer heavy stick pulling maneuvers. But i'm in VR with headphones all the time, so no problem for me there. Never needed to do any maintenance stuff.

Hi there. I got the first public Rhino device almost exactly 2 years ago. Still running strong and precise. Flying DCS almost on a daily basis.

Congrats! In roughly 2.5 weeks it's 2 year anniversary

It kind of amazes me everytime when Facebook pulls off stuff like this. First the simple renaming into "Meta" to get rid of "we all know what you did in the past years", now this "branding" of an Android OS version to Meta Horizon to make it sound like it's "their" operating system. This "open ecosystem" is nothing else than Subway or any other franchise system that will lock you in. If they really wanted to open up, the apps in their store would be 100% OpenXR conform and running on any other mobile Qualcomm VR device (like Pico or HTC) without any tinkering (which is easily doable, they just need to flip a "switch" it's all Android...).

Just had a similar problem. Petro couldn't see a SA-8 OSA and a M1A1 directly in front of him, instead he insisted targeting only some harmless trucks at two o'clock.

CSV slaving after ground stabilization is the most important step in the procedure.