Zabuzard

If you do not have a Sidewinder attached on all sides you may have to use the button on your Pinky Hat to Cycle the station to select the right missile to use (Pinky Hat up IIRC). Not all Sidewinders have the growl tone. A lot of them have Null-Seekers, which go dead silent as soon as the missile looks at the target. Kindly see the manual for an overview on this: https://f4.manuals.heatblur.se/stores/air_to_air/aim_9.html#employment Thanks for the tracks, will check on Monday.

Yeah it's on the list to add them.

Mind sending over a track of you replicating the issue? Cause it looks good on our side :)

Kindly see this thread, thanks:

The automatic fuel transfer system kicks in when cell 1 + 2 drop below a threshold, so it likely did activate in your case. I need to doublecheck the code tomorrow to tell you how it behaves exactly when wing tank + ext tank are selected. But I do for example recall that this system overrides the "stop internal wing transfer" switch. Then again, there could be other reasons. Perhaps you pulled some heavy G or extreme outside temps or sth and one of the valves broke or got stuck. Perhaps just momentarily but while you were in AB. If you can reproduce it and send a track, it would be awesome. Then I just have to launch the track with the debugging interface open and can see the status of the entire fuel system within a second :)

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.

Perhaps you are too fast? Have you trimmed the aircraft correctly? Are you holding the stick full aft until the aircraft takes off on its own? What is your procedure, at which speed are you airborne? Not sure what you mean regarding the SU. A track would be nice :)

Did you fly with afterburner on for a few minutes? Possibly even some negative Gs? The system cant feed faster than the AB burns. But yeah, smells like you trapped the wing fuel. There are several ways to do so.

(Track likely wont be possible due to the crash, but a mission file with the concrete steps to reproduce would be useful )

Could you elaborate on what happens for you and guide us through your procedure? A video or track would be perfect. I am sure you are just missing something minor and we can quickly get you on track then[emoji106] Otherwise I would just recommend any of the great YouTube tutorials on the matter.

Kindly review this page again: https://f4.manuals.heatblur.se/procedures/bombs/bombs_loft.html For LOFT you need to enter the loft angle (low angle knob) and the pullup timer, as shown on the linked procedure. Thats it, nothing else needs to be entered. Once you are over the IP you press and hold the Bomb Button. At this point the aircraft starts running down this Pullup Timer. Once it hits zero you get the cue to pullup (tone and lamp). You pullup and the aircraft automatically releases the weapon the moment you hit the Low Angle you configured. Since it is solely based on a pure timer it is crucial that you fly the parameters you used in the tool to obtain the timer value precisely. That is, if you for example fly faster or higher or miss the IP by 0.5nm than the values you entered into the tool that spit you out the timer value, then you will miss the target. I agree, the manual would benefit from more details. You will find an "issue" for that on its Github page already. The manual is open source, so feel free (or anyone else) to edit and improve it[emoji106]

The release altitude and speed are only used to compute the correct drag coefficient value. They are not entered separately. Kindly see the corresponding manual page for details, cheers: https://f4.manuals.heatblur.se/stores/air_to_ground/bombs/employment/lofting_tossing.html#procedure---loft Also see: https://f4.manuals.heatblur.se/procedures/bombs/bombs_loft.html

The default model without any "weapons" loaded has pylons and hence the aircraft weight is configured for that specifically. A "removed pylon" is considered a weapon by DCS. Hence you can pick it from the loadout options, like a bomb or pod. Since it is a weapon, it has weight, including negative weight in this case. If you would configure the aircraft by default for "no pylons", users would need to "equip" pylons manually in the loadout editor each time and we would also need to tie the pylon visually to all selectable weapons. It is much easier and more reasonable to instead have the pylons there by default and make the "no pylon" an equippable option. That decision then leads to the weight setup.

Sure, the dialog-UI supports the same controls than the Jester Wheel. That is: * head tracking * mouse * QWE and CTRL+1..4 * assignable cursor axis

Please make sure you are actually using TAS not IAS. Speed does affect the release solution because it impacts the Drag Coefficient. Wrong Drag Coefficient leads to wrong ballistics. Could you supply a video and/or track showing your issue? Im sure we can then easily identify the cause of the problem (be it you or actually a bug). Note that when you supply a track we also need a screenshot of what you entered into your Bombing Tool, since that otherwise is not captured. Cheers

Yes, kindly see this thread, thanks:

Can you share the full error message, a screenshot and/or your DCS log file? The "code" you shared is just the full name of the aircraft.

If you cant find it, please share a screenshot so we can guide you to it. Possibly you need to scroll down.

Mind sharing a screenshot or something? Have you checked the screenshot in the above manual link?

Yes, its one of those: https://f4.manuals.heatblur.se/dcs/special_options.html

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

Yes, internal and external are using different materials.

Nope

Does it crash in an empty mission with just you and your Phantom as well? If not, smells like out of RAM or similar. Can you share your crashlog file please.