For example engine start can done be done in 3D.

Some versions of F16 has a dragchute.

It should be converted to canvas..its osg text now I think

It looks great, so why not..

Same principle as Mirage-2000

The new fuel dialog will break the F16 payload system.

In future: set opt/lbs to non nil also for jsbsim in F16 payload system.
Also make use of setprop("sim/gui/dialogs/payload-reload",1); to reload the dialog.

The Mirage2000 ordnances is in progress of renaming.

When that is done, enable damage from them into F16.

i understand its an old model but here are some points of interests, hope this helps :)











also the AOA indicator is floating

you can see threw the engine wiglet (both sides)

intake rod isn't connected

some clipping threw a gauge

front gear doors float


the rear wheel floats off the rear landing struts
gap in the model between fuselage and intake



vapor is clipping threw the wing when pulling G's

vortex generators float both wings

Make this pod visible and selectable from the central pylon.

That would allow for text like in the livery below to be readable from both sides.
There is plenty of room on the UV map for this and the geometry is already volumetric to allow for this, right now we have to avoid text there.

Create fragmentation of bomb casing and cluster units after some time elapsed after drop (could be also linked to alt?).

It also jettisons dummy wingtip missiles..it shouldn't

This has not really been looked at since the system was made, it needs a review.

Unknown needs to go or be strongly filtered.

Update damage system in other projects so f16 can damage them:

AGM-65
GBU-12

For:
Mirage2000
Admin assets
Viggen
F15
F14
SR-71
Mig21
etc etc..

The geometry have to be remade for the main trunk of the bomb.

Needs a serious overhaul and check that stuff works.

Richard has started by doing the right main panel and the left aux panel.
A couple of days ago I did left main panel switches and a couple of knobs, it need more knobs though.

Note: After a 3D conversion the texture must be updated to look more 2D and not try to draw 3D switches on the flat 2D panel etc.

duo has been made (twinrack.ac), needs to be textured.

This is an issue that involves many things. Such as moving viewpoint (which means chaging 3D of cockpit so MFDs RWR can be seen clearly. It might also involve changing the HUD model a bit to keep bore symbol inside it.

Add default inert missiles as a payload option also on the second pylon.

Its too rescricted for JASSM, it will overshoot target often.

pjedved made a nice model for F16D. It would be a great variant, but also alot of work to add.

Add intake side pylons as additional payload positions for targeting/navigation pods.

So it consumes framerate, even after it has been clicked away.
If it has been shown on both MFD the cost doubles.

Adding different textures to the pilot model according to the livery worn by the a/c, (e.g. F-15).

Type in FTTY as destination to provoke error. @Zaretto has been informed.

Add contrail at high altitudes.

Spectre reports refuel is broken.

Needs confirmation and possible fix.

The landing lights are inside the front wheel bay door:

There currently is no autopilot.
It could use one.

They are harmless, but I will fix them anyway, when I get around to it.

`In file /home/steve/dev/f16/Systems/jsb-controls.xml: line 1871
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 152
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 306
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 564
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 599
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 763
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 777
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1035
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1070
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1103
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1115
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1193
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1211
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1412
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1447
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1475
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1508
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1543
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1834
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1869
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1902
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 1937
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 2251
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 2351
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 2384
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 2454
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 2482
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 2517
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 2594
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 2881
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 3158
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.

In file /home/steve/dev/f16/Systems/jsb-aerodynamics-block15.xml: line 719
only has one argument which makes it a no-op.
Its argument will be evaluated but will not be applied to the result.`

Loadouts right now are mainly Greek. US loadouts can be done due to docs I found and that would be nice (like tripleracks of AGM-65).

These views (also chase w/o yaw and model) are a bit too far away from the model, would be better to have them closer.

Right now stores can be mounted and used, but only the fuel tanks show in 3D.

The issue is finding some way to get them to show properly and smart over MP.

This is a showstopper for remerging into FGAddon.

Here is some examples:

the gun the sound doesn't stop playing after bullets runs out

bug: if you are locked on someone who disconnects, the HUD will freeze for ~5 sec

FG 2018.4.0

No clue why, that display don't use textures.

James is making a Canvas method available that allows for more efficient ground clutter drawing.
When its included, we should look into making a dedicated ground radar page on the MFDs.

oil press failure conditions ^^

AB simulation ^^

Ill add more as i see it, and i understand some of them may already be in place

Pitch oscillations around stall speed which result in NaN being propagated through system.

Block 60
Pilot: Megaf

This is very serious and need to be kept an eye on.

As the title says.

Needs to see how it behaves with Shinobi's new code (its disabled, pending review).

As of now only the AGM65 can be used with the TGP.

I think what we want is:

All A/G weapons should be able to fire at radar target, but with less precision.
Using TGP should give best precision.
The radar lock lack of precision should be translated to TGP whenever a new radar lock is obtained. Actually it should lock also.
The XMIT procedure has to be rethinked. It should not be needed, a lock is a lock.
Maybe when firing first check if there is a TGP lock, if yes, use that, if no, use radar lock if available.

Need to rethink more, the problem is we are simplifying it due to not having tons of custom weapon/TGP pages on MFD.

See also #81

In Linux 5H1N0B1 reported with FG 2018.1.1:

*** stack smashing detected ***: <unknown> terminated Abndon (core dumped)