Ray has been working on an update, and he has seen film of the Komet, with quite a smoky exhaust.
He has been trying to get that effect but handballed it to me.
So I did a bit of work on the Me-163 after checking out a real one




Take-off:


Near targets:


You can see the curves in the smoke trail more clearly in this shot:


The modified 160 exe can differentiate between the 163 and the V1:

The normal V1 routine applies in this case

Jel

Any cockpit shots?

I did not do any as I was just testing the smoke trail effect and using F9.
AFAIK the cockpit used is the original one from SWOTL

Well,that was quick. Thank you very much.

Does the smoke disappear when the fuel runs out? I forgot to mention that parameter when we were talking yesterday.

Yes it does

Ok, perfect.

I have one more technical question that I posed over in the Code Group forum.

As a result of my response to Ray's last question at the Gen I had a new idea.
Because 160 is slot free the old aircraft codes such as "262a" are no longer used by the exe in any routines.
To confirm this I re-coded the "plane.dat" for the Me-163 with an aircraft code of "163B" and as I expected everything worked as it should do with no problems at all.
This means that additional programming routines could be included based on the aircraft code and this opens up a heap of possibilities for new things

FWIW, I'm going to need a 163C for the "paper plane" jet powered Me163C that never made it past the proposal stage in the real world.

Here in 1.6 EAW world, all things seem to be possible.

In general, I'll have to think on this new mod. There are a lot of possibilities.

Then there was more

Text handling in "C" is tricky, and in "plane.dat" a block of 8 bytes is reserved for one of the 30 plane-code ("p38h", "p38j"......".h111", "v1v1") text.
Only four bytes were ever needed, as all plane-codes had four letters, and now in the slot free system none of them are needed because the exe does not use plane-codes in any routine.
So each of those eight bytes is now an individual piece of data, (NewByte1....NewByte8), and they are numbers and not text.
In a test of the Me-163 smoke exhaust I reprogrammed it to be triggered if NewByte1 = 65. I edited the "plane.dat" file accordingly, and flew the Me-136.
The correct exhaust trail was visible, so I know that the system works