Zabuzard

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

(It is currently not planned)

Uuuh wtf is that, almost like a beat oof. The track doesnt replicate it for others and no one else reported something alike yet. So whatever it is, it must be something "on your end". Im not sure what though. My recommendation would be to do a full repair and kill all mods, but you said you did that already.

That wont work with the F4 but you could just delete the UI from the folder. In the F4 the entire UI is "local" and fully moddable. It is in Mods/aircraft/F4/UI/JesterWheel But it wont fix the problem, your UI inputs are not replayed and hence the aircraft is in a wrong state. If you make a coldstart with the UI using mouse or headtracking and then replay that, your aircraft will in the replay fly with engines off and no electric power. Consequently no weapons will drop, nothing works. Same in the F14. you can hide the UI but if the UI actions arent clicked then the aircraft is in the wrong state.

Smells like you did use HB UI such as the Bombing Tool, which isnt captured in the replay and has to be entered manually during replay as explained earlier in the thread, cheers.

That is because mouse actions and head movement on the UI isnt really captured during replays by DCS. That also leads to the tracks not working as expected, for example the aircraft taking off with a dead engine and not firing any weapons. You can either control the the Jester Wheel via keybinds (for example the CW/CCW/Enter binds) or recreate your actions while the replay plays by pressing ESC and then mouse clicking on the right actions.

(I cant watch the track right now, but) A few things to consider: * approach the target from slightly below, do not get into a look-down attitude * approach the target from the side to increase its RCS, avoid head-on * avoid placing the target in front of mountains or other terrain from your viewpoint * do not place the target at a distance equal to your own altitude * if done right, expect to spot fighters at 10-20nm, maybe 22nm if you are good. large targets like bombers at 30nm-40nm. * if ur flying against typical DCS players that hug the ground, forget it. u wont get them on screen with a regular search * at visual ranges make use of the pilot controlled radar modes, for example BORESIGHT, allowing you to lock targets by putting them on your pipper * expectation management, this isnt a search radar. you need to know where the enemy is (awacs etc) and then optimize your position to get the bandit on screen. even in good circumstances, against fighters you will only have time to fire maybe a single missile until you are already in range for sidewinders and guns

It happens during taxi because putting it into STANDBY will start the heatup, leading to the radar melting if you take your time on ground.

That is because you have not received this build of the F-4E yet. It is fixed internally but not available to the public yet Could you perhaps record it on a quick video or something? Potentially you are doing something wrong or it is correct behavior. Hard to guess based on that. For example, with wind even on a cold aircraft you will hear the engine blades making noise depending on which direction the aircraft is facing.

Hey everyone, good news! I got you the desired visibility args added. They will be available with the next update of the F-4: HIDE_PILOT_QF = 4500, -- used for QF drone liveries, the code should not overwrite this HIDE_WSO_QF = 4501, -- used for QF drone liveries, the code should not overwrite this

Not sure why you guys conclude "HB say its intended, they wont fix it" when I keep saying the opposite. Sorry if the messages have not been clear enough, so let me try it one more time: The current behavior is "working as expected" but that doesnt mean that it won't be improved/changed. As I keep repeating, it is on the list and it will eventually receive another pass so that the lag is gone. Please do not misinterpret that some things take longer than you want for lack of interest or willingness to change and improve something.

Odd. Yeah, probably try without mods then. They have caused severe issues in the past for no apparent reason. A screenshot of your "tiny ingame manual" and your settings page (graphics and f4 special options) would help :)

Are you using a multimonitor setup or sth like HELIOS? What resolution did you set in ur DCS settings? Maybe something very big so it works for multi-monitor? In that case you would need to fiddle with the Special Settings of the F4 HB UI. Screenshots will definitely help once you can share them :)