Zabuzard

draw_args.lua is accurate, it is what the code uses after all. You are talking about external draw args instead of cockpit draw args. Scroll down in the file to where the ext draw args are defined :)

The Stop-part of the throttle range is not part of the throttle axis. To me it sounds like you might have mapped the idle-cutoff buttons that are under the Warthog throttles to the fingerlift bind in the Phantom. Which, when triggered, toggles the throttles between Stop and Idle.

Those issues are common in DCS and affect most modules one way or another. It ultimately boils down to DCS physics combined with an underground that isnt always 100% flat.

Most likely there is no target return on the radar screen and hence it cant be locked. If the targets are visible already, go CAGE/BORESIGHT instead. Otherwise, either fly co-alt or tell Jester the target altitude via the wheel. If he still cant see it, its due to gain or you are just expecting too much from the radar. For latter, you can try finding them on the radar yourself and if you fail, Jester couldnt do better either.

Thanks, we are looking into it.

Please make sure you are actually equipping the pods on the "special pylon" CMS. If you were referring to the chaff/flare sliders in the rearm menu, they do not do anything.

The binds for the antenna elevation were broken before the update. The update aligned the binds with the underlying implementation of it being a "springloaded 3-pos switch". So now the binds work. The next step is to change the thing to also provide a relative and absolute axis, as well as self accelerating inc/dec binds.

You can do it either from regular boresight or cages/boresight mode. Select your RADAR missiles, set the correct target aspect, point the radar at the target and shoot. If the cirrect aspect was picked, the missile will usually be able to pick up and lock onto the target a few seconds after shooting. Jester will support this situation in the upcoming patch.

Make sure you do not have the "Use FFB" option checked in your DCS settings. Some reported that it auto-enabled itself after the last update again, and it is known to cause issues like that. And yes, the reason the stick becomes "so sensitive" and moves all the way aft during takeoff is due to the bellows starting to sense speed. So they start to pull the stick aft by themselves, taking away more and more of the force applied by the bobweights.

That's how we organize them in our projects. Others may do it differently. The Viggen for example only used raw numbers without names IIRC, bit painful.

Perhaps you can share screenshots or the exact and full name of the binds you are using. It works on my end

Not sure what the confusion is about. The process is to turn the Jettison Selector Knob down to STORES, then "select" the station you want to drop by clicking their respective station arm button-lamps. Now, click on the Jettison Button that is on top of the Selector Knob. All of those actions can be bound.

Could you provide some screenshots? I really have trouble following what you are describing.

I am not sure I follow the issue regarding the pencil. The second thing you mention is unfortunately impossible to change at the moment, it is Aa DCS limitation. We can only render UI at the front area in VR. The same limitation affects the DCS chat window and VOIP controls.

The DMAS variant and in the future perhaps another module for a Navy Phantom.

Draw argument, or simple: animation. The aircrafts animations are stored in so called draw args and can be played usually from 0 to 1 (sometimes also - 1 to 1). Everything that moves or blinks in the cockpit is an animation stored in such a draw arg. Mission designers can also read them and Livery designers can for example also set/write to them. That's also how the different helmets and similiar in liveries work.

Sure thing, putting it on the list. Thanks :) If someone from the community feels fancy, feel free to have a look[emoji106]

The animation arguments are all listed with names in a lua file accessible to you. Its in the Dcs/Mods/aircraft/F4E folder somewhere, called draw_args.lua. It lists all animations the plane has to offer, internal and external, with names. Similiar for the command values (the ones used by binds), in a file called command_defs.lua. You can also play and test out the animations in DCSs ModelViewer (see DCS/bin folder), the exterior model is in the CoreMods folder, the interior in the Mods folder, subfolder Shapes :)

It is due to a bug in the hydraulic system. The AAR door thinks the pressure in the Utility Hydraulic line is zero until you start up the left engine. Thanks, fixed.

The aircraft has plenty of delivery modes to choose from, they are described in detail in our manual. You could for example use Laydown or Offset. Loft of course works as well. If you happen to have the pod equipped (I guess you don't), you can also use TGT FIND very effectively.

Indeed, the Phantom doesnt support the raindrops for technical reasons yet.

Possibly you overheated/broke the seat? It must only be used for a few seconds per minute. There is a warning on top of the seat about that and in our manual. But yeah, looking forward to a track or something once you are back :)

Thanks, this one is known to us

Thanks. This is a tricky one, I am having a very hard time finding the target with the radar myself here as well. It is not really a "Jester issue" and more that this is a really difficult situation to pick up that small Mig-21 coming straight ahead and masking itself behind the terrain in a slight look-down attitude. I can see the return pop up occassionally for one sweep but then vanish again on the very next sweep. Even if I fine-tune the antenna angle and gain manually, the target usually vanishes immediately again. It is a bit better after telling Jester to change the display to 25 nm NARROW (Jester Wheel > Radar > Scan Type), but still very difficult. The target can then be spotted fairly well manually at around 6 nm. Jester spots it a second later at around 5 nm. The best I was able to achieve in this situation by operating the radar manually was spotting it at 12 nm with 25 nm NARROW and descending a bit. Jester found it himself at 10 nm then, after he tweaked the gain a bit to make the target appear for longer than one sweep.

Both of them require electrical power. The AAR door additionally needs hydraulic power. Perhaps you did not have the power you needed? Can you reproduce it and possibly send a short SP track showing the issue? Cheers