Zabuzard

Well, its complicated. There is a lifepoint threshold at which he will consider an aircraft to be done, report it as dead and ignore it in his logic.

If you make it too low you will have enemies that are burning to the ground but still considered a threat. If you make it too high you will have Jester ignore someone on fire who is still flying around shooting missiles at you, being unable to attack them back since Jester ignores them.

We have to work with what the DCS engine offers to us. Unfortunately, that isn't much when its about the combat status of another aircraft.

The External Tank Feed switch must be in OFF for the internal wing tanks to be used.
They both share the same pipes and if the valve is in the wrong setting you are only allowing the non-existent ext tanks to feed, not the internal wing tanks.

The aircraft has no awareness of ext tanks being loaded or not. So if you select ext tanks to feed, but have none, you are still blocking your internal wing tanks.

Thought I responded back then already, seems not:
Thanks, all of them are on our list, cheers.

Huhu. This is correct as-is. The marker is on the glass, not the gauge itself and a lot of what you see is just due to parallax.

The marking is put manually by the ground crew and there isnt too much attention paid for it to be pixel-perfect.

If you check out a few reference aircraft, they will all vary a bit.

Cheers

Subtitles (and possibly with translations) are a planned feature, so no need to ask for it :)

Hello, kindly do what is adviced in this thread. Thank you:
/topic/366674-f-4-authorization-error/#entry5576100

There is no clean, easy and safe way for us to create content inside DCS own savedgames folder.

So what we always did for our modules is to create our own folder and then have full control over it.

Possibly that can be changed if ED gives us a proper way to manage content in their folder.

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).

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 :)

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

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.

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:

 

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.

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.

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.

Yes, thats on the list 🙂

Probably something for ED to look into. The content of the mirrors is managed by them :)

does the ingame stick visually move or also stationary? on ground or in air (or both)?
does it happen to you always or only sometimes?

trimming changes the length of the lever that allows the bellows to put force on the stick in order pull it aft. if ur bellows are out (ground, frozen, lost tail, combat damage,...) trimming won't do anything

Are you launching DCS with the "new" launcher? Perhaps double check the settings menu in the launcher and then again ingame for the "Use FFB" setting.

I recall the launcher sometimes messing with settings after updates. At least when it came out.

Depends on what exact call you got from Jester.
If it came from his radar code, he can't know that the object is "dead" yet. The radar shows returns and doesn't tell Jester anything about what it is.
Same if the call is from his RWR code.

If it came from his "eye code" then he can confirm that the bandit is down, but that also depends on what the DCS SDK had to say on the objects lifepoints and similiar.

Either case, getting hands on a track or at least a video would be really helpful, thank you :)

The HOBOS are broken in the current DCS version. The issue was fixed internally already, available with the next update. Cheers

The weights are all defined in the main lua file in your game folder. Something like Dcs/Mods/aircraft/F-4E/Entry/F-4E.lua and the Weapons.lua right next to it.
You can probably CTRL+F "weigth" or "drag" your way through it
Any weapon not defined in those files is DCS-built-in and defined by ED.

Correct, the F-4E (pre DMAS) has no audible low-altitude warning, only a light.
The DMAS upgrade adds a Voice-Warning system which includes a low-altitude alarm.

Can't promise a date but they will come back once the gremlins are resolved :)

Sorry, cant view the track. It requires the A-4 mod:

Could you retry making the track on a clean mission?
Note that the entered data is for the release-moment, which in DT differs from the dive-moment. In particular, the Dive Angle is the angle you have during your pullup maneuver when DT decides to release, not the angle you have during the dive. So if your angle at release-time differs heavily from 30°, perhaps thats the reason.
I can give you more info with a track I can work with, cheers 🙂

Thanks, this is a known issue since around a month. Cheers