New Aircraft

[paul_r]

Yes I'm sure there's other things you want to do - I've taken a lot of your time lately.

One question which you or maybe Ian could help with - occasionally on landing, a start-up model will fail to drop it's nosewheel. It happens at random and in itself is not a problem - it just looks silly taxi-ing around with it's nose in the air. Sometimes though (and again its random), a following aircraft on the ground will run into the back of it and this screws everything up.

I've yet to run more than 4 or 5 hours without this happening - I go back to the previous save and resume the session and it goes through OK - wondering if there's a simple solution or if Ian could create an additional aircraft trigger to drop the nosewheel if it's still in the air.

Thanks again
Paul

 

[mattsmith28]

Paul_r i would love this route

 

[cressjl]

Wow, this is incredible! Have you made any videos that show off this outstanding capability? I would love to see a video demonstration to brag about!

 

[john2002]

I'm interested in that route

 

[nzld]

Paul, you could try setting up boat's aircraft trigger to drop the nose wheel.

Gordon

 

[paul_r]

nzld, It's boat's trigger that I'm using with the start-up models. There are now 15 settings that I have played around with to no avail. One problem is that there is no description in the trigger asset of each setting and the referral to Ian's website only refers to a few of them.

I don't think the problem is with the trigger or the aircraft but with the volume of processing for the AI aircraft that my computer can cope with. I get occasional random problems not just with these triggers but with both the conventional and ATLS signalling and the AI aircraft themselves either stopping for no apparent reason or going off their prescribed routes. I can save, switch off, then resume the session and previous problems will execute correctly and then different random problems will occur. The longest I manage to run without something going wrong is about 3 hours although there are times when lag becomes apparent.

I keep tweaking things and one of the remaining needs is to have a "fall back" trigger because if the nosewheel does not make contact with the track it affects the signalling and that can quickly have a widespread affect on adjacent ground movements. I have tried an extra trigger but that just raises the nosewheel of an aircraft that has landed correctly.

I'm happy to provide this route for anyone that wants it but it's become a challenge to me to get on top of these remaining problems before I release it.

In fairness, I don't think Trainz is really designed to operate this number of AI vehicles - I remember wondering when I first got Trainz if I could operate more than 8 AI trains - but if anyone has any suggestions ......

My processor is Intel i5-3230M 2.60GHz and 8GB RAM. Windows 7 Professional 64 bit.

Paul

 

[vulcan]

Hi Paul,

1. The trigger settings for each aircraft are described in the config file description. I also mention that some values can be changed in the config string table, to specify for example, the speed that the wheels retract, the flap retraction speed, and the tilt speed (below that speed the aircraft will remain level for taxiing).

The wheels and wheel door operations are all one animation, normally it is impossible that the front wheel would not come down when the main landing gear lowers, unless as you say, the AI is overloaded and Trainz faults. This is a possibility. Of course if there is a runtime bug in the models (the bug symbol would appear in the bottom right of the Driver screen) then anything could be possible as the script fails to execute.

As I mentioned above, the wheels are automatic in the script, operating when the set speed is reached, no trigger is allocated to this action. This was done to make as many things automatic as possible and free you up to fly the planes.


2. I should outline a problem in TANE for the aircraft. Auran have instituted some more checks on the scripting than they did in TS12. For each trigger action, I allocate a a handler in the script, for example:

AddHandler(me, "Train", "NotifyHorn", "HornMessageHandler"); // open door

Most aircraft do not use all the 15 trigger actions, but I had left the handlers in the script for some unused triggers, as a place holder when I copy the script to another aircraft. Unfortunately, Auran now object to having a handler in there when there is no follow up scripting to act on the handler trigger messages. This results in a runtime bug when the aircraft is placed in TANE, or when the aircraft is operated in Driver, for those non operative handlers - a handler listens for the corresponding trigger messages as I understand it.

Since the goal posts have been moved again, I need to spend some time fixing a large number of aircraft and re-releasing them to operate in TANE, sorry for the inconvenience. All new models will be at least build 3.5. All older models on the DLS will still work correctly in TS12. While you do not need to update to any of the new models, for use in TS12, there may be some small improvements to the textures or meshes in some.

Ian

 

[lennieusa]

hello, first of all I'm new here so i posted this pic in another place of this web, but i guess now I'm in the right thread lol…well here is my first post n i repost the same here ...so this is it…….when i was browsing in threads i decided to post this pic of the Aerolineas Argentinas airliner just to share with all of you ,who love airliners with a cool livery. thanks Leo(lennieusa) from America

 

[nzld]

Hi Leo,

Welcome to the world of Planz.

Gordon

 

[paul_r]

Hi Ian

Thanks for your response - I've obviously misled you with my original post.

The problem is with a random failure to land with all wheels on the ground after the flare trigger #7 - not the actual lowering of the nosewheel - sorry.

Specifically I have a trigger #7 for flare about 8 miles out so the aircraft comes in level on the descent path. This trigger always seems to function OK although I may miss an odd one that doesn't becuase some aircraft are not start up models anyway.

On landing, I have triggers #4, #7, #9 and it is the 2nd #7 trigger that occasionally doesn't execute, leaving the aircraft in flare position with it's nose in the air. It's likely that the other triggers sometimes don't execute either but go un-noticed because there is no knock-on effect if they don't. I've tried changing the spacing between the triggers and even placing an additional #7 but as expected, that just raises an aircraft that has landed properly into the flare position.

I am pretty sure the problem is with my computer trying to process too much information (although the red bug you mention only appears very occasionally) hence my enquiry to possibly create a "fall back" trigger to execute again. An aircraft that has already executed the original command would just ignore the fall back command.

Now that I have finally got on top of signalling problems, this has become apparent as an issue because signals to the rear of an aircraft in the flare position do not show red.

As far as TANE is concerned I am expecting there will be problems to iron out. I tried running the CE version but soon gave up - I will just wait for my boxed copy and take it from there. I will probably keep to TS12 for this route and start anew with TANE with whatever is available. TANE must be causing an awful lot of work for you content providers and I for one give you a big thank you.

Paul

 

[lennieusa]

thank u Gordon

 

[vulcan]

Thanks Paul, that makes it clear.

I am not sure how often the script "listens" for a message from a trigger, but it is not continuous, perhaps a fraction of a second. If an aircraft is traveling quickly, it might be possible for it to cross a trigger and not be listening for the pulse, if that makes sense. We used a series of triggers for the float planes on landing to emit "smoke" as water spray over the landing distance. Rob might tell you it took some experimenting for him to get a continuous spray effect, the aircraft speed, distance apart of the triggers, radius and the time I set in the script for the smoke effect had to be taken into account. For example if the smoke is still emitting when it crosses the next trigger, there can be a missfire.

I would suggest you can make the trigger radius larger for flaring on the runway, (set it in Surveyor) so the aircraft is within the radius for a longer time. Again, if there is a lot going on in Ai with many aircraft and triggers, the listening pulses may become spaced further apart depending on the computer power, and could miss a trigger.

Ian

 

[paul_r]

Thanks Ian. When I look at the trigger radius, I have #4 and #7 triggers along with 2 ATLS triggers and an exit junction all quite close together so I shortened the radius to avoid overlaps, although on a second landing path, the #7 trigger radius is unchanged at 20m.

It will be a while now before I can try this out as I've started a new run which I check out from time to time but which is still only at mid-day. Touch wood, so far I've only had 4 instances so that is definately an improvement but I don't know why. Maybe the compter "learns" as it goes along?

As a point of interest to avoid having to stop and start the session again from the beginning, I now have a maintenance area track with an extra #7 trigger on it and offending aircraft get directed over it so as long as I spot it in time, it keeps the session going.

Paul

 

[paul_r]

Late morning departures beginning to build up at Heathrow

 

[Rob725]

hello, first of all I'm new here so i posted this pic in another place of this web, but i guess now I'm in the right thread lol…well here is my first post n i repost the same here ...so this is it…….when i was browsing in threads i decided to post this pic of the Aerolineas Argentinas airliner just to share with all of you ,who love airliners with a cool livery. thanks Leo(lennieusa) from America

Leo,

Does this Trainz version of the A340 look close enough to your photo?

Pascal mentioned you had asked for this re-skin.

Touchdown....

The A340 model is a little bit out dated as far as Vulcan Avionics is concerned. The Wing flaps are manual instead of the automatic (speed triggered) flaps and the flashers are not started with the start up routine (B-key). What it does have is reverse thruster flaps for landing (see below).

Taking off heading back to Buenos Aires.

Landing now at a DLS near you.

Airbus A340-313X Aerolineas Argentinas (2011+) startup
<kuid2:590184:100454:1>

 

[KenRuof]

Very nice skin Rob even if it is an outdated model.

 

[Rob725]

Thanks for the encouragement KenRouf but it isn't one of my best works. It was a difficult re-skin. The larger passenger jets are always tricky and the Argentinas isn't often photographed like some of the European and North American brands. This all adds up to a tough re-skin job.

Anyhow. I hope you all like this South American girl despite her blemishes.

 

[papou]

Well done, Rob.

Sure that good pics of this particular livery are scarce, and often pale.
Difficult to really appreciate the blue and grey tones. I think anyway you are close to the real thing.

More South American aircrafts please!!

Pascal

 

[lennieusa]

Thank you so much Rob725 for that aircraft.its really beautiful and it means a lot to me. if all of you allow me id like to dedicate this Aerolineas Argentinas aircraft to my mother Irma. She is in heaven and i miss her a lot…so thank you again Rob725 also Papou cause u sent my request to Rob, n Vulcan cause he made lots of nice aircrafts n gave me the pleasure of appreciate all diff airliners liveries. Thank You!! Leo

 

[pagroove]

Hello. Here are my first Aircraft Reskins.

Air Nippon Wings 737:

And a All Nipon B747-400.

Does anyone know how to get readable winglets? There is very much texture distortion. Otherwise the second skin is nearly done. I ask for permission to release these aircraft if they are acceptable enough.