Zabuzard

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.

The defog handle is currently not simulated and hence has no binds. Binds will be added once the handle has a function, cheers. Also see here in your clickabledata.lua:

Sounds unrelated. The second thing you mention can have a plethora of user error reasons. Could you share some screenshots of your front panel and/or a track or video?

thats the thing, it doesnt seem to happen for any of us or other users - the Jester repeating voices stuff. no one so far is able to reproduce this issue. if you found a method that reproduces it always it would be great to get the exact detailed list of steps or a video yes, you can bind the actions to direct keybinds. those would work in the replay as well. essentially, you just have to make sure to not use mouse or headtracking for interaction

Sounds like you used the Jester Wheel UI during the track, which means that if you replay it it wont work. So I suspect the track will not be useful, unfortunately

Just to make sure, when you replay that track (DCS Main Menu > Replay), it occurs there as well, yeah? How long into the track is it roughly so we dont miss it while watching? Cheers and thanks

This has been fixed for the upcoming patch. Cheers

For that bug we are still hoping that someday someone is able to put it on a track that can reproduce the issue when replayed. We werent able to find the cause without yet.

Make sure you flick up the Screen Source Switch on your Pedestal Panel: https://f4.manuals.heatblur.se/cockpit/pilot/pedestal_group.html#screen-source-switch You do not have to hop into the backseat by the way, Jester will turn on the radar.

Mh, bit sparse on the details, given that it works for others. Could you retest it after the coming update, I recall a few changes on the procedure. Otherwise we probably need a track, video or a detailed list of actions. Recently someone had a mission that flipped a switch which messed up their sequence.

note that shrike behavior once off the rail is controlled by ED, not us. so if u suspect a bug, ideally, direct it at them[emoji106]

Mh, could you try outside of VR?