Zabuzard

Smells like a bind issue. Gotta check your pilot binds for the view and see if it's linked to TrackIr properly.

Its also not just our content. Their own VOIP window is affected in the same way. When you press ESC you can see a black-ish rectangle indicating the "zone" these windows can be rendered in. And that zone is directly affected by those VR/graphic settings, being very small if the wrong choice is made. Its essentially how the game renders "screen content" in VR, on some form of virtual monitor placed around the HUD area. Also the reason why we cant render these windows on your view, but only static on the HUD area in VR - as opposed to 2D, where the window can be rendered so it moves with your head.

ED already worked on a fix but it seems it only did do the trick for some users. Guess they have to get back to it.

Huhu, we checked ur track and it looks like you spawned with empty tanks. Did you possibly select the empty-variant in the Mission Editor? Please doublecheck or send the mission file, thank you.

You mean this here being shifted half a position too much to the right? VS real:

Hi, I just tried what you said. I can confirm the TGT lamp doesnt light up. However, the arrow correctly changes and points towards the TGT I have inserted, including the Flight Director ("ILS needles") on the ADI.

Will look into

Huhu. Yeah, we do not control AI behavior. Gotta forward this to ED as well

Whatever the cause for the crash is, it seems to be happening solely in EDs code: So this probably has to be forwarded, cheers.

Sorry, cant view the track. It requires the A-4 mod: Could you retry making the track on a clean mission? Note that the entered data is for the release-moment, which in DT differs from the dive-moment. In particular, the Dive Angle is the angle you have during your pullup maneuver when DT decides to release, not the angle you have during the dive. So if your angle at release-time differs heavily from 30°, perhaps thats the reason. I can give you more info with a track I can work with, cheers

Can you reproduce the issue on Caucasus? I still havent gotten access to Kola (If I do what you describe, it works just fine)

Yes, this is a DCS-compromise. The weight is defined per-bullet in Entry/F-4E.lua around here: If you change it, the gun will not behave as expected in DCS, unfortunately.

Glad it works better for you now :) 64 GB arent necessary to achieve solid FPS in the Phantom. We have tested it with multiple low spec machines with generally good results. When issues happened, it was usually due to unfortunate combinations of hardware or obscure settings deep down somewhere. So its totally possible that someone with a 1070, a 10 year old CPU and 16 GB RAM runs DCS and the Phantom specifically at better FPS than someone with a "NASA machine". Its unfortunate, but that's kinda how it is - at least in DCS. Very hard to continue improving that experience once at that point.

Odd, thanks we will have a look. When I used that feature a few weeks ago it worked still [emoji2368]

This issue usually happens when you have bound switches in a certain way and especially axis. In this case it can happen that DCS forces your hardware input according to your binds on the plane and Jester then cant do much for the affected switches. See if it works after unplugging your hardware or similar, just to see if its that.

Its in ur backlog, it can't be forgotten anymore. Cheers.

The menu currently doesnt support more than 8 waypoints. It is known and will eventually be fixed, thanks.

Yeah exactly, the list just became too long Thanks for reporting, it is a known issue since the last update

Jester Wheel, Crew Contract, Silence or something like that

Ah, you mean the in-cockpit labeling of the switches/knobs. Fair, I misunderstood you.

Could you point those out so that we (or the community, since the manual is open-source) can fix it? Thanks.

The Crew Chief talks to you through headphones connected in-parallel to the WSO audio channel. Meaning that your plane must have power, your intercom must be activated, the WSO must be on hot-mic and shut up to not block the channel. Otherwise no one will be able to hear the Crew Chief talking. When that is the case, the Crew Chief will instead communicate through Hand Signals to you (which you cant see because there is no representation of the guy walking around (yet)). You also notice that by the name of the Crew Chief menu in the Jester Wheel, which says "Crew Chief (Hand Signals)".

The alignment part has a bug that was fixed for the next update. Id suggest to recheck when it drops, cheers.

It isnt more effective. Its ultimately a personal preference. Roll STAB fights your roll input to some degree with opposite artificial input in order to cancel out unwanted roll and stabilize the plane. This can feel like something is getting in your way when you want full and direct control. Overall its fairly minor though and its authority is quite small. Some prefer it on, some off. Both choices are fine :)

Are you running DCS on a SSD? These spikes are usually caused by heavily increased IO traffic due to the map-data calls made by the DCS engine to answer the radar rays. There isnt too much we can do on our side to get rid of the issue, but we are planning to shift the moment to shortly after takeoff by delaying Jester turning on the radar, so that the timing isnt that critical anymore.