Zabuzard

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?

What happens if you left mouse click this arrow? It should expand the window and give you a light-greyish window in which you can draw. At least the arrow icon should change to pointing down. If you are using VR or similar, try using your actual mouse instead. It is possible that the window, once you clicked the arrow, was resized to almost zero. The resize handle is on the bottom right corner of the window, a small black-ish symbol. Likely easy to spot for us if you send another screenshot after clicking on the arrow once :)

Technically possible. But it would also affect for example where mouse hints would show and could lead to an odd experience with touch controls, since that's all tied to each other. I believe it would also be unusual with respect to other modules, but haven't check. These hitboxes can be displayed if you open the model with DCS/bin/Modelviewer.exe and click on some "show collisions" button. And yes, they are mostly exactly the switch and not surroundings. Thanks for the suggestion though. Ill forward it to the artists for consideration :) By the way, if there is a switch you are having trouble with specifically, plewse mention it and we can improve it for that individually quickly.

Could you also attach a screenshot of what are entered into the bombing tool please, since it is not captured in the track. Or did you do it without Jester and the track works without any tool input?

The box is expanded by clicking its top left corner, there should be a dropdown button next to a name. If you could share a screenshot I could point you directly to where to click. Cheers

Jester modding is currently not supported yet. This is mostly because IC topics are not resolved yet, i.e. the ability for mission or server makers to specify and enforce what people are allowed to mod and what not. The files are not "decrypted" but lua-compiled. It is possible to decompile them if you really want to have a look and start messing around, but it will not pass IC. Ideally you gotta wait for us to make it available first.

Not sure what you mean. The fixes will be in the upcoming DCS update. You have to ask ED when that will be, probably not too long. Usually their update cycle is something around 4-6 weeks.

What kind of black rectangles are you talking about, could you screenshot that perhaps? When you click the right side of the window where the mouse hint pops up, a window will open on the screen. It might be collapsed and have a clickable arrow to expand it. Once expanded this window can be drawn in, there also is a menu on the top right corner of that window. To hide the window, you would click the spot on the canopy again. Please, elaborate in more detail what issue you are facing, try to document the process with some screenshots or a mini clip. It is probably just a small misunderstanding and easy to fix once we see what you see :)