Zabuzard

That is only the CAGE/BORESIGHT mode but not the (regular) BORESIGHT mode (Jester Wheel > Radar > BST).

If they actually appear visually on the screen for you but Jester couldnt tell, then we would definitely like to have a track as that is something we can tweak [emoji106] Just means that his "eyes" arent good enough yet. (While ofc not being too good to pick them up within clutter where humans couldnt see it either)

That's not really a thing in the F4. All the WSO can do is roughly changing the altitude (but Jester is already really good at that and you have options to further fine tune that in the Jester Wheel already) and adjusting the gain knob "at random". Even if you know precisely where the bandit is the pilots positioning plays a higher role in getting the target on screen than what the WSO can do. In the F14 its different. Take any of your encounters where you are struggling to get something on screen and fly that with a real WSO, you will see it wont work much better. You can get a lot more out of it by improving your positioning. Boresight works well for roughly up to 10nm, not just 5nm btw.

Im not saying it isnt btw, its there for a reason after all. The default scan behavior is, as the name implies, a default scan behavior. Its meant for when you dont have any idea of where the bandits might be. If you have extra knowledge just point him at the right altitude (in the future he will learn expected target positions by himself ofc). At close ranges you are likely better off using Boresight (regular) or even CAGE/Boresight or CAGE/CAA [emoji106]

We do model RCS in more detail than maybe other aircraft do. I cant really comment on how others may do it but aspect in all 3 dimensions and other things definitely have a very heavy influence on our RCS simulation for our radars. There are also some YouTube videos and similar where users experimented a bit and made graphs to visualize things a bit.

If a target doesnt appear on the radar screen then there is nothing Jester can do to change that. Your aircraft positioning determines the picture quality. If they dont appear on screen then your position isnt good enough. That said, a more clever "look here" thing is planned. As Ivandrov said, the F4 features "pilot assisted" radar modes, you should make use of them. Boresight mode lets you lock something by putting pipper on it visually, that sounds like what you need.

He can. The tldr would be "git gud". Its most likely a mix of expectations and improving aircraft positioning. A few things to consider: * dont go look-down * dont approach a fighter head-on, go sideways to improve RCS significantly * dont place them at a distance equal to your altitude or they vanish in the altitude line * dont place them next to clutter in terms of distance to increase the contrast * make sure there are no mountains or other terrain next to them or right behind them from your perspective * (if they are hugging the ground, forget about it, you wont get them on screen) * if all things go well, expect to get a fighter on screen at about 15-25nm, that gives you time to shoot maybe one missile before you are in heater range (for larger targets its rather 25nm-40nm)

His default scan behavior covers 10k ft up and down, he will usually cover everything relevant without you having to tell him. The Jester Wheel allows you to focus on the expected area but it will not really allow you to reach a spot that you wouldnt have reached with the default scan already. The antenna symbol looks like it only changes a bit but his ~3° up/down cause already a change of ~10k ft at 30nm.

What the manual states is the ideal refuel rate but in practice refueling is highly dynamic as it depends on the pipe layout. For example if you are down to only the left/right ext tanks it will take much much longer as they share the pipe. Similar for other tanks that are "behind" each other pipe-wise. Especially bad if you refuel the internal wing tanks and external tanks as they all share the pipe. Careful with doing math based on the fuel totalizer instead of the EFB fuel page (next F4 update), as it doesnt include the ext tanks. That said, we cannot change the refuel rate of the tanker itself, its constant in DCS.

He does when he visually sees a missile and you haven't turned it off in the Jester Wheel. But bear in mind visibility in the backseat is very limited in the Phantom and the WSOs primarily role is to watch six and operate the radar. So he often won't see missiles and consequently also not dispense CMS often.

If you got a video or something that would help to figure out whether what you are experiencing is normal or abnormal. Make sure that "Use Force Feedback" checkbox in the DCS settings is unchecked, it causes super weird stick and trim behavior if you do not actually have FFB and somehow DCS has it enabled by default. For some users their stick also sends inputs to the game longer than its actually held IRL. This would cause microclicks to actually be longer clicks. Some sticks have software where this minimal signal duration can be set and lowered (you can then also confirm it in Windows built-in Joystick input tester thing).

This is expected and correct behavior due to the bellows vs bobweights system (as explained in depth in some similar threads already). (Make sure you have the force feedback checkbox in the DCS settings disabled though) There is also a Special Setting in the F4 settings to help users who have trouble with this (correct) behavior, I think it was called stick smoothing period or something like that. The core difference to some other aircraft is that trimming in the F4 doesnt trim the stick, it "trims the bellows". The bellows apply their force dynamically based on airspeed measured at the tail (bellows intake). They pull the stick aft the faster you are. They are the opposing force to the bobweights which push the stick forward the more G-load you have. Trimming essentially scales the force the bellows decide to apply. The outcome is a highly dynamic play of forces that changes constantly and it leads to the Phantom naturally wanting to fly in large oscillations. Test pilots also noted this as a bit annoying but ultimately decided, after a bit of tweaking on the system by the engineers, that its not a problem in practice if you "just fly the aircraft", i.e. not going hands off stick. And there is also the autopilot after all. Also, trimming is done in micro clicks, dont hold it :)

Exactly, so I doubt you will have much luck "exporting" it - it is not a screen. That said, for the actual screens in the cockpit the feature has been (partially) implemented now. It will be available with the next F4 update. Details in the manual: https://f4.manuals.heatblur.se/dcs/screen_export.html Cheers

Hey guys, this feature has been (partially) implemented now. It will be available with the next F4 update. Details in the manual: https://f4.manuals.heatblur.se/dcs/screen_export.html Cheers

Hey guys, this feature has been (partially) implemented now. It will be available with the next F4 update. Details in the manual: https://f4.manuals.heatblur.se/dcs/screen_export.html Cheers

Hey guys, this feature has been (partially) implemented now. It will be available with the next F4 update. Details in the manual: https://f4.manuals.heatblur.se/dcs/screen_export.html Cheers

Hey guys, this feature has been (partially) implemented now. It will be available with the next F4 update. Details in the manual: https://f4.manuals.heatblur.se/dcs/screen_export.html Cheers

Hey guys, this feature has been (partially) implemented now. It will be available with the next F4 update. Details in the manual: https://f4.manuals.heatblur.se/dcs/screen_export.html Cheers

Hey guys, this feature has been (partially) implemented now. It will be available with the next F4 update. Details in the manual: https://f4.manuals.heatblur.se/dcs/screen_export.html Cheers

Hey guys, this feature has been (partially) implemented now. It will be available with the next F4 update. Details in the manual: https://f4.manuals.heatblur.se/dcs/screen_export.html Cheers

In the meantime, using any other Bombing Tool selection that allows you to enter TGT ALT should work as well. (Note that you can also fly the aircraft from the back, the flight stick is functional - and Autopilot binds are exposed to the backseat as well)

Correct. The feature itself is already there since launch. The 3d model has all the options as separate animations and livery makers could already use this to for example have their livery equipped with a different helmet or for example a female pilot. The UI hooks into the same mechanism and just plays this animation. You can have a look at them already in DCS ModelViewer for example. From a technical perspective it works the same way as a switch or knob that is moved in the cockpit, just an animation with several states.

It will come during EA. We currently cannot provide any ETAs though, cheers. Regarding the "how", it is a popup window similar to the other HB UIs (e.g. Bombing Tool, in-game Manual, Jester Wheel, Virtual Browser, EFB, ...) similar to the one shown in the announcement trailer. Currently it allows selection of body type (also gender), helmet, gloves, sunglasses - but that might get expanded.

Hey there. The UI menu for selecting fuzes in the rearm menu is defined in the weapon settings of the respective module. If its a "custom weapon" it looks something like this: { name = _("BDU-50LD - 500lb Practice Bomb LD"), mass = 241, wsType = {wsType_Weapon, wsType_Bomb, wsType_Bomb_A, BDU_50LD}, Cx = 0.00018, picture = 'bdu-50ld.png', settings = Get_Fuze_GUISettings_Preset("MDRN_B_A_TPLD") } { name = _("Mk-81 - 250lb GP Bomb LD"), mass = 118, wsType = {wsType_Weapon, wsType_Bomb, wsType_Bomb_A, Mk_81}, Cx = 0.00013, picture = "FAB100.png", settings = Get_Combined_GUISettings_Preset("MDRN_B_A_GPLD") } Note the last part of each entry, with that Get_Fuze_GUISettings_Preset and Get_Combined_GUISettings_Preset methods. That is what adds these menus. For weapons that exist already by ED, one can just use their CLSIDs and it works out the box. For example the F-4 uses CLSIDs {SAMP250LD}, {SAMP250HD}. The actual selected fuzing in the cockpit when launching the weapon is then communicated by the module to DCS through the SDK.

Ive just checked the code, they are sorted by creation time. an "own map markers" menu was added now. will be available with the next f4 build