Zabuzard

Thanks for the tracks. Can you replay them locally in DCS to see if they work and replicate the issue? That's how you can verify yourself if the track will help us or not. Thanks :)

Yeah. Its not the best UI for this particular use case. Theres some stuff on the list to improve it. But welp, time... :D

When you set it to launch according to a configured program it will release them based on the configured programs parameters. Are you saying it is doing something different? If so, could you provide some details please? Cheers.

This is a DCS VR engine issue for which ull find solutions reported in the forum and the FAQ. Essentially, go to ur VR settings and check "Use System Resolution", select BOTH EYES and then go to ur graphics settings and select a resolution of at least 1920x1080. Restart DCS. It should work now. Otherwise, ull find some options to mitigate in the Special Options, such as offset and resizing.

Nope :)

Such vertical lines are either the result of getting jammed or its a known bug that a lot of players report being fixed after selecting the "Radar Performance" option in the Special Options. So I'd give that a try. Regarding Jester not finding the Mig, if you havent seen the return on the screen then its likely your fault for not positioning the aircraft right or simply expecting too much from this early radar tech. There isnt too much Jester or any WSO can do to make a target appear on the screen besides pointing the antenna there and tweaking the gain, which Jester does automatically. If you can supply a track or video of the situation we could have a look and give details on what happened :)

Please do take note that the manuals often cant be taken literally and sometimes contradict the electric wiring diagrams of the technical maint manuals and the like. But yeah, we will have a look. Thanks.

Rest assured, we read all bug reports. It will ofc be investigated. Cheers

Right, we are aware. It happens to us occasionally as well. The issue is not knowing that it happens or what it does. The issue is that in order to find the source of the problem and to then fix it, we need a working track file (short and SP) that reproduces the problem when replayed within DCS. Since then we can attach a debugger to the game while it replays the issue and inspect the system in order to spot what is going wrong in the code. So far neither we nor the community was able to capture it on a proper track yet, sadly. And our ~3 blind attempts at fixing "something that looks odd in the relevant code" apparently did not fix it. At that point the only way forward is to work with a track.

We have several features planned to improve on this. From a virtual keyboard to being able to bind the numbers. And also generally improve the UX of the text-input in the UI, in particular for VR users.

This is happening occasionally since release but no one was able to pin it on a working (short SP) track. Our blind investigations and attempts on it didnt do the trick, sadly.

No update.

I would have to guess but I suppose yes. Messing with this file allows you to change a lot of stuff, for example adding the Mig-21 nuke to the Phantom. Or giving the AI Phantom ultra acceleration. Or removing Damage Cells.

If you dont like the training bombs (or any other weapon on the affected pylons) and dont want to wait for the proper fix, the best I can offer you for today is to remove the weapons from the pylon definitions locally. Therefore, go to Dcs/CoreMods/aircraft/F4E/Entry/F4E.lua and remove the following lines (or whichever weapon you want to remove):

Thats the POV of someone who is perhaps flying on a server or similar and wants to blow up stuff. If you ask someone from a squad who makes realistic trainings you would hear the opposite. Either case, a solution will eventually be found :)

I assume you are in VR? This issue is the result of an unfortunate combinations of settings. You can find a few explanations on the forum. Essentially, you need to go to the VR options and check "Use DCS System Resolution", select "BOTH EYES", then go to the regular graphics settings and choose a resolution that is 1920x1080 or higher, then restart DCS for the changes to be loaded fully. That should do the trick. If you really can't get it working, the Special Options tab has a few options to mitigate the issue a bit (for example you can manually force a lower resolution, offset it left/right or up/down and so on).

Yeah... hopefully ED can find a solution. Would suck having to remove a weapon.

Yeah its a known issue. A couple of updates ago we added a few more bombs and now the aircraft just has too many weapons :D The GUI itself is indeed out of our control.

Huhu. The numpad is currently not supported due to engine limitations. Offering ways to bind it through the normal bind menu is a bit complex to make for this specific case but it is indeed on our list, cheers.

It definetly should be fixed with the latest update. I haven't heard anything negative yet, on Discord people reported that they work again.

Sure. Eventually. You will see it in the changelog when it has been fixed, cheers.

It should be the same way as in CAGE/Boresight, so just LONG context command (V). Details here: https://f4.manuals.heatblur.se/jester/combat/radar.html#dogfight

Sorry, no ETA.

Im a bit out of the loop on this topic specifically but you should note that the Bombing Tool (due to engine limitations) currently assumes CBU would never open in-air and fly all the way to the ground - and that is the solution the tool spits you out. You can counter that by artifically telling the tool that the target would be higher than it actually is, namely at the altitude above the real target where the container would open. That should then give you better values for the WRCS.

Not quite sure I follow. If you set the flares to SGL and mash the Dispense button like a maniac they will dispense very fast. Make sure though that your hardware has a minimal impulse time set that allows sending DCS the command fast. Ive seen people with hardware setups where its impossible for the software to get signals more often than twice a second.