Swift.

AlphaJuliet, I've PM'd you the references for this bug

What is the selected sensor? It should say in the top left of the TPOD screen (among other places)

The aircraft luas. For example FA-18C.lua in CoreMods/aircraft/FA-18C. The caveat is the rack mounted weapons, they don't respond the same way. Perhaps there is something to be done in the AircraftWeaponPack, idk. Of course, the easy alternative to this is to reanimate the models so the proper model is at arg value 0, but its been years and ED havent done that so there must be a reason why they aren't.

On all versions of JDAM there is an M904 mechanical fuse being shown. This fuse is not allowed to be loaded onto JDAMs IRL, and instead you will most often see a nose plug installed instead. (Needs confirmation, but it looks like Navy prefer the MXU-735 nose plug and air force the short cone shaped one) The solution to this issue is very simple, now that the DrawArg line has been revealed for the aircraft luas. Simple add DrawArgs = {{56, 0.5}} to the Navy jets, and DrawArgs = {{56, 0.4}} for the USAF jets.

Its funny, some SME's say its too draggy, some say its not draggy enough. Some say its too powerful, others not powerful enough.

Here's another image of it, for reference

Offset waypoints are super unreliable right now, I only still use them because I'm trying to catalogue the bugs that appear every flight with them. Also remember the approach course isn't necessarily the same as the runway heading.

IRL I'm thinking CAS situations. Especially once you add VMF into the mix where the target location is automatically stored into a waypoint

TOO employment can still be accomplished against waypoint designations, it doesn't have to be an onboard sensors designation.

If you guys reeeally want the single amraams. Stop asking for single amraams and start asking for the pylons they mount on.

Are you confusing true and magnetic bearing perhaps?

You literally said 'US Hornet, not a swiss one' and you want me to interpret that as completely the opposite literal meaning?

Nope, thats definitely a swiss hornet. US Hornets don't have numbers like that Notice the J-5011 on the tail and the 011 on the nose. A US hornet will always have either two digits like the marines and USN squadrons not assigned to a CVW or 3 digits starting with 1 2 3 or 4. Additionally that hornet has those pylons I was speaking about earlier, the same ones the SuperHornets have on their outboard stations. Heres a picture of the same hornet J-5011 in a different livery, visible are the Swiss roundals

I'm doing this in the parent forum because I can't reproduce these issues well enough to generate tracks of them. Has anyone been seeing really odd bugs with the offset function in hornet? I've tried to create a list of them but I'd love it if anyone knows how to reproduce these or if anyone has even seen them. - Offset is applied to all waypoints, when entered to only one - All waypoints are labelled as OAP even though they dont have Offsets - The offset location cross appears to drift on the HSI/SA when you turn and resets its position when you switch from one format to the other. - Navigation range to OAP shown in the HUD is measured to the offset rather than to the OAP, where on the HSI the range is measured to the OAP. - OAP will show as a WYPT even though it has an offset applied to it - Switching HSI/SA with SCS Aft appeared to switch the existing designation on the OAP to a designation on the offset These bugs all happen independently of each other, and seemingly every sortie I use offsets on, but I cant reproduce them on missions shorter than several hours so I havent reported them yet. Basically what I'm saying is if you guys could keep an eye out for them and try to save any shortish tracks you experience so we can tie up these bugs at last. Thanks

These'll be awesome to have in the sim, does this also mean the associated damage modelling, for locking the wings before they are fully deployed, will be done?

And to expand on that, its a Sparrow mounted on a LAU-115. Which has no problem directly mounting to the pylon.

And after all that, the Flight Models are one of the better parts of DCS

AFAIK the standard behaviour for aircraft is the aimpoint represents the pattern centroid. I don't have anything specific for hornet, but its certainly supposed to work that way in harrier

Wait are you saying when you ripple 2 with 200ft spacing the second bomb hits where the aim point was? Because that's not 200ft short, its 100ft short.

You do realise that having a FM within like 10% of the real numbers is already twice as good, in a lot of regimes, as the industry standard for flight simulators?

It would be nice to have a model argument to remove the panel that covers the fuel probe when fully retracted.

The INTV ODU option input is currently too large by a factor of 10. Expected behaviour: ODU>INTV 75 entered into scratchpad Scratchpad shows 75 ENT pressed 70 shown in scratchpad 7 shown on ACP actual bomb release is 75ft Current behaviour: ODU>INTV 75 entered into scratchpad Scratchpad shows 75 ENT pressed 75 shown in scratchpad 75 shown on ACP actual bomb release is 750ft intvharrier.trk

When JSOW C is loaded onto the hornet, the model shown on the aircraft is that of a JSOW A. Whereas the model shown for JSOW C in the model viewer is the correct version with the IR sensor. JSC.trk

When the Auto Pilot is disengaged by any means other than depression of the paddle switch, an AUTO PILOT caution should be displayed for 10 seconds or until the paddle switch is activated. The caution is written into the code, and the auto pilot system is already in the game. So this caution should be shown. AUTOPILOT.trk

Yeah the result is the same, even if the mechanism that creates it isnt correct.