Zabuzard

FYI you can freely edit the lua file that defines what can be loaded onto each pylon. In case of the P-51D this file is DCS\CoreMods\WWII Units\P-51D\P-51D.lua (see line 367 to 576). That way, you can essentially attach any weapon that exists ingame onto any pylon of any aircraft ingame. Whether the aircrafts code supports that weapon (so it can also be "used") is a different story. In case of the P-51D, attaching smoke generators like the colored smoke producing Sidewinders does work though. Just have to "arm" the weapon ingame and that triggers the smoke.

Is only the HB UI lagging but the rest of DCS works as usual and without lag? You might be running into this rare issue that we had before launch, causing the delay of the release. Which was then fixed for all testers. Mh, odd stuff.

Does it get better if you, just for testing, heavily tune down your DCS settings? Like, set it to low quality, low visibility and similar. May I ask, what is your ping towards your flight partner roughly? When it happens and you open your task manager, is there anything that looks like being a bottleneck? For example your RAM or CPU being at 100%? Perhaps you have been playing so close to the max that the overhead of multicrew went beyond the limit and now you are running into a bottleneck.

Make sure you click with your (real) mouse into the field first so it gets keyboard focus.

You either need to have your canopy open and engines off (so they can hear you talking), or you need to talk through your Intercom while the WSO is on hot-mic (or was it cold-mic?). The Crew Chief plugs in from outside into the WSOs Intercom channel. Details in the manual, cheers. Make sure you are actually using the "Jester Wheel" and not for example trying something through the DCS default menu (or do you want to rearm/repair?)

You need to use the number keys on the main keyboard, not the Numpad. I.e. the ones with the special symbols on top of them, such as !"§$% and so on. This is an unfortuante technical limitation currently.

The "random failures" option is a DCS feature that will automatically activate failures from the list of available failures in the ME at random. It works on all aircraft by default.

Could you please send a screenshot how it looks for you ingame? Make sure you are looking at the window around the HUD area, not the canopy area.

The window that includes the drawing area and the options-box. It has a blackish titlebar and an arrow to collapse/expand it. In VR that window opens around the HUD area and if you click with your mouse on the arrow u can expand/collapse it. And if you click the titlebar you can drag it around. In non-VR it opens on the center of the screen and moves with your camera, like an overlay. The mouse controls are the same though. The results are then rendered on the canopy, as if it would be a screen.

(see your identical post on Discord)

Thats correct. Any HB UI can in VR only be shown around the HUD area. The collapsed window can be opened and dragged around using the mouse (not VR hands)

Could you explain in more detail what the problem is, what exactly you are trying and perhaps share a screenshot. Thank you.

Should be described in the manual. I, think it was something like Dcs/Mods/aircraft/f4e/Sounds

This is an ED issue. Hasnt been "fixed" yet. You need to delete the sdef.tar cache file or only overwrite existing sound files. Saved Games shouldnt work as DCS doesnt load sounds from there.

We get the list straight from the DCS Api. So whatever it is, its usually either mission or map related and not anything we can change.

Correct me if I am wrong, but these provide an in-game overlay only. And not actual video recording to your disk (which is much more complex to achieve on the technical side). Afaik Grinelli is the first to offer something like that in DCS. These "picture in picture" overlays are directly supported by DCS and relatively easy to achieve from a technical POV (as this is the mechanism used by for example any MFD or even HB UI). For recording proper videos without destroying FPS you likely need to stream the texture straight from the GPU. Any mechanism offered by the DCS API that gives access to the texture data seems to destroy FPS (from my testing). So you have to go around and do some deeper magic.

there really is no problem in disagreeing or having a healthy discussion. and we are always very open to feedback of an sort. im sure there is sth about the lighting that can be improved as well. ideally talk to cobra about it, the person who worked on this topic the most. but yes, afaik its fairly spot on, more or less (provided ur running reasonable dcs settings that are generally considered as the standard to tune the experience for). we have SMEs in our group who flew the F-4E many years during wartime and also pilots and WSOs who flew other variants, for example the german Phantoms. and if they together say "this is correct", then that has a lot of weight - for any aspect that we simulate. i can understand that it's frustrating as u typically dont get to talk to these SMEs urself, so it might feel like someone just being mad and "playing a card" to kill ur argument. but thats not the case. its unfortunate that most SMEs dont participate in public community, but i can also totally see why. that said, some people with access to real phantoms are here and open to talking about such details. I understand, we would like to have it working as well. But there is nothing that can be done about it at the moment.

Yes. I believe I even recognize whose signature this likely is. Ive tried a few approaches and spend about two weeks on it without a lot of progress. Cobra hasnt found much time himself yet to give it a try, he knows more about this than I do. Anyways, just a matter of figuring it out.

Yup. The image is likely more blurry though if the lense isnt in the right spot bc its focal point is elsewhere :)

Yeah. Its this guy here. They would attach it before each flight (and detach after to get the film to analysis). And before you ask, at least IRL it was "mandatory". They never flew without it (according to our SMEs). (func fact, I've heard stories when they forgot to attach the screws and the entire thing would fall in your face during takeoff - yikes)

Possibly you misunderstood me. The grease pencil is made using HB UI and HB UI, as explained earlier, cannot offer "touch controls" or similar because that is a DCS limitation. There is no interface for it that thirdparties could use. HB UI uses ImGui to render a texture in a popup window (that texture being written to by CEF, through off-screen-rendering). ImGui natively features mouse and keyboard controls straight through the Windows API, although we had to take some extra steps to actually capture keyboard events that DCS didnt suck up and forward them to ImGui. Additionally, in Jester Wheel and Jester Dialog, we have mocked mouse events driven by character head-movement. I am not sure how you can conclude that we "dont test it" or are unaware of this. This is simply a technical limitation and as soon as DCS offers a way for us to access what your VR hands are doing and where they are pointing and clicking at, we could forward that to HB UI as mouse events. Until then, you have to use your actual mouse, there is no way around it - sadly. But that doesnt mean the Phantom wouldnt be tuned and optimized for VR since day one. Please try to be fair with your feedback, thank you.

The aircraft currently isnt even equipped with the gun camera. The gun camera is installed on the HUD dashboard and takes away roughly a third of the forward visibility. It is supposed to get shipped as soon as the team found time to implement proper video capturing (which is actually quite difficult on the technical side) - see the manual for details.

Likely a Map definition issue, yes. We specifically query the DCS api for TACAN signal senders and display its outcome. Might need some looking into by the team behind the map, or we are possibly not using the right API calls/options. Ideally sth to fix in a collaboration or similar, I guess :)

Im not sure how you came to the conclusion but the Phantom was developed with VR since day 1. The experience is in many regards tuned specifically for VR users as well. Jester UI has full VR support, was also tuned for voice support, all switches and buttons support hand control, Crew Chief operations have been added to Jester Wheel so they can also be done through head controls or via voice control instead of the default immersion breaking menu. There is a detailed VR Pilot Body. Extra effort was put into ensuring that everything in the cockpit is millimeter accurate to ensure everything has exactly the right size and dimensions specifically in VR. Ofc some things dont work well in VR (yet), but that is mostly down to DCS/engine support shenanigans. Most notably HB UI. For example, there is no way technically to interface with VR hand controls as mouse substitute yet, DCS simply lacks an API for these things (afaik).

It hasnt changed. Potentially you or RedKite damaged their PaveSpike by pulling too many Gs or by flying without having it powered on so it can hold its electric stow position. Or you or RedKite selected a Condition that wasnt 100% in the Mission Editor (or a Wear that wasnt 0%). Make sure to select "reference aircraft" in the Mission Editor, airspawn and try it again then. Then you have the perfect setting :) The zoom lenses can easily get bumped around by too much force or if the manufacturer didnt place them carefully.