New Aircraft

Welcome to the aircraft reskinner club, Pagroove!

Send your request to Vulcan, with one example of your work, and it shoud be no problem.

Regarding winglets, these small, inclined surfaces are difficult to map. You need to distort your texture, so that it appears correctly. A lot of trial & error..

Pascal
 
Thank you papou :).

Will do when they are completely ready. Question. Do you know of another 747 which has letters on the winglets? That is the difficult. The All Nipon 747-400 has ANA written on the winglets. But I distorted the hell out of it yesterday but couldn't get it right. So it would help if there is another 747 in which I can look in the main.tga?

Also. With Tane out now is there anything special we have to do? I can't test because Tane Mac isn't out yet and my specs are probably to low.
 
Nice work Pargoove.

The winglets on the 747 are going to be tough without interference from Vulcan. From memory, there isn't high enough resolution to get you what you're after. Vulcan is the only one that can help. Sadly he's hit a computer snag with his computer last time I heard from him so you may have to be patient.

The 737 is a different story. From your screen shots, it looks like you may have used an outdated model as a template. I can't be certain. The turbofan texture is a dead give away. It may well be that the template you used doesn't have the fancier looking texture for the fan. When you uplaod the model (as I'm sure you will) you will need to be clear about which 737 variant it is. Have a look at some of the others on DLS (I find Content Manager to be the easiest to do this) and look at the naming structure that Pascal & I use (and are trying to get others to adopt). <Brand><Type>-<variant> <Airline> <year> startup. eg. Boeing 737-2H4 (Adv) Southwest (1971+) startup . It helps others understand what they are downloading & helps when you want to generate other re-skins from it. There are so many Vulcan models & re-skins out there now that we've had to be a bit organized. Also make sure the right credit is given to Vulcan (see my manual for details). It's only fair since he kindly gives his time & frustration to us free of charge.

The following info is useful for those wanting to do 737 reskins.
The 737 has a range of models now and you have to be careful to pick the right one to start with. So here's the run down.
There are a number of models out there pre "Startup" era. You shouldn't start with any that don't have "Startup" in the title.
We now have the following models with the original Vulcan model (or template).
B737-200(Adv) - Template:- Boeing 737-232 Canadian North startup
B737-500 & 600 - Template:- Boeing 737-683 Scandanavian Airlines startup
B737-300 & 700 - Template:- Boeing 737-781 All Nipon Airways startup
B737-800 - Template:- Boeing 737-81B China Southern startup

Notes.
The pre-startup model is based on one of the shorter 737 variants. Most of the existing re-skins have been heavily distorted to make them work. Over time we'll work to replace them.
The 200 series has variants with shiny jets like the United & Southwest re-skins I've done and also Pascal. Vulcan did some specific model changes for those and anyone re-skinning should be aware of that before making a start.
The models that the 300, 500, 600, 700 & 800 are generated from have a number of features that are able to be turned on or off with a modification the config.txt. This includes winglet and dome options. Vulcan has built us domes for a specific airline so you may have to look around to find the right one. If you're having trouble, ask us. I also have a split scimitar winglets that I haven't tested and rolled out yet. Southwest Airlines have been retrofitting them of late.

Below are the key lines. The auto-create line is how you turn the feature on and off. 1 is on. 0 is off.

dome
{
mesh "body/dome.im"
auto-create 1
att "a.origin"
att-parent "default"
}

wingtips
{
mesh "body/wingtips.im"
auto-create 0
att "a.origin"
att-parent "default"
}


Sorry this got a bit long winded but I thought it was important. The A320 family has a similar system.
I hope it enlightens.

Cheers

Rob
 
Last edited:
This is a "heads up" for creators and skinners on here who may not be aware of the discussion going on in the TANE forum - Edit of default content.

For those of us who feel strongly about this I would suggest we add our two-penneth to try and force some reaction from N3V

Personally I am furious about this situation

Paul
 
Thanks Rob275 for the explanation on the 737 system. I will look if I got the right one. As for the 747 I can leave it now. Or I can make the winglets blue so without the ANA logo.
 
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


Hi Ian

Just a note to tell you I finally completed a full day's Heathrow re-run yesterday and there has been no repeat of the problem since I widened the trigger radius. The only remaining issue is that after a resume, aircraft already on approach flare after landing which is something I can live with. So - no problem with the flare trigger after all.

Thanks
Paul
 
Paul,

I use Train Priority to allow different aircraft to react or ignore triggers. You should be able to group them by the way the aircraft are configured. I've used parallel invisible tracks to run heavy and light aircraft.

Hope that helps.
 
Hi Rob

Priority codes are not appropriate because all aircraft are commercial. The only way to deal with aircraft already on final approach (i.e. already passed the first trigger) after a session resume is to have a new trigger to turn flare off when flared, or ignore if not flared. I don't want to ask Ian to accommodate another trigger with his aircraft when I'm sure he's enough to do with modifying his aircraft for TANE so I'm happy to live with that.

Paul
 
Hi Pagroove,

Like for any reskin, you will have to accept some limitations, due to the texture resolution, shape of parts (flat surfaces are not frequent on aircrafts) and difficulties for the author to produce such models with not too many polys.
So, do your best, even if you need to be a bit far from the reality. Leaving the winglets blue may be a good option so far.

Pascal
 
Hi guys, a few comments.

Pagroove, I had given general permission for you to reskin aircraft, it lets me do new ones instead of spending a lot of time reskinning, and gives Rob and Papou something to do as well. Send me a model and I will look it over, and perhaps provide a few helpful comments.

Thanks for the explanations Rob on some of the options for wingtips and domes on the more recent aircraft. Perhaps in the future we can allocate a larger texture part to the wingtips for better detail.

One other thing for the aircraft is a change in Tane for the sound file tags for the engine.wav file. This is the sound that the aircraft plays after you start the engines, an idle sound file. For the main engine sound asset for the aircraft, I make a silent idle1 sound so we can do the correct startup sounds for an engine and then the idling sound. Only after you move and the engine is at notch 2 does the main engine sound take over.

You do need to make sure the the sound file tags look like this, earlier configs did not have or need the zero:

sound
{
0 "engine.wav"
}

Secondly, the use of quotes was not required in earlier versions, and no quotes was acceptable in TS12. If you import a model into Tane without the quotes, Tane adds them. Unfortunately, it also adds about three spaces after the file name in the config. This does not show as an error, but a warning, and can be missed. The warning is "cannot find the sound file engine.wav (because the config name with the spaces does not match the sound file name in the asset). Even if you have a carriage return immediately after the name, those spaces are added.

The result is the aircraft starts up with the usual sounds, then silence. after you move forward, the main engine sound cuts in at notch 2 - this is one warning that has to be fixed in the config, fix the quotes manually in Tane or add them before import.


For the flaring, on commercial aircraft I used to use the V key, but Rob needed that for some other animations, we only have three keys to use plus the triggers. You may find the V key as a flaring option for some older aircraft - check the config description.


Matt, some larger aircraft have the bogies relatively close together, and can derail on very tight curves during taxiing for instance, this determined the minimum radius Rib and I used for our fixed turnout models. Otherwise, they should not normally derail, but you MUST set the Derail to None in Surveyor options or all aircraft will derail on large radius curves at high speed.

My computer seems to be running ok at the minute so I can get back to some updates for Rob and Papou, and also test out Tane. The latest Tane patch took 7 hours to install the other day, unbelievable. I had imported one of my test aircraft routes, some of the invisible line colours were not showing in Surveyor though the verticees were there, and everytime I tried to add or adjust the track, Tane collapsed and vanished, I had to restart it. Not impressed, I will have to import another routs to test.

Paul I did read the comments on editing routes, interesting, some things seem to get more difficult instead of easier.

Ian
 
Last edited:
Ian - just read your comments and you've obviously got a lot to do for TANE

Can I ask - and this is not a request if the answer is no - when you referred earlier to having to rework a lot of aircraft, does this include upgrading all TANE aircraft to "start up" ? (I ask because the British Airways 320, 321 and 763 models are not - and they make up a large element in my Heathrow model)

Paul
 
Hello Paul,

I did not have that in mind, but as I work through them I might do that for some older models, I will note the ones you mention.

Ian
 



Colourful Thai A340-600 on the 12.30 TG911 departure to Bangkok with the distinctive Heathrow tower and a taxi-ing American B767 in the background
 
Hi Paul,

The BA 320 is one of my reskins. I will have a look. If you have other models in mind, just tell us.
There are many to convert, so some priority is necessary ;-)

Pascal
 
I have something to add to Ian's very comments. (Ian,sorry for correcting you)

The current commercial aircraft key set up is as follows.
B-key - Startup
H-key - Door (mainly step/door on the smaller turbo-props & small jets but the E-190 has a door as well.) H was also used for flaps on the older non-speed activated flap models like the A340.
V-key - Flaring
The trigger assignments are fairly consistent as well. Below is an extract from the current B737 config. This is pretty typical.

- to start engines, press the B key or use trigger setting 2. An engine start rule is also available for AI.
- issue smoke and sound from the tyres when landing, use trigger setting 4.
- to flare the aircraft for landing, trigger setting 7 or V key.
- come to a gradual stop on landing, trigger setting 9.
- use reverse thrust on engines for 10 seconds trigger setting 13.
- set speed to 40% of maximum speed, for landing approach, trigger setting 14.


Some older models use H for flaring and V for flaps and B in some cases. Before the startup jets we we using one of the keys for activating the landing/air braking flaps. We are gradually phasing these out and aligning them.

The military aircraft are a different prospect because they have all sorts of special tricks. Ian's had to sacrifice the H & V keys for other more interesting things like re-fueling probes, cargo doors and missiles.

Hope that helps
 
Hi Paul,

The BA 320 is one of my reskins. I will have a look. If you have other models in mind, just tell us.
There are many to convert, so some priority is necessary ;-)

Pascal


Well Pascal you asked for it!

To do a full sweep I've set out all aircraft that don't flare and leave it to you what you want to do and when. I've listed each section in order of significance to game play and I've taken the liberty of showing a more appropriate aircraft type for Heathrow 2012 if anyone fancies doing a re-skin.

Pascal - the Virgin B744 does not show as startup but it does in fact flare.

British Airways A320
Turkish Airlines A320
Air France A321
Finnair A321
Cyprus Airways A321
Air Malta A320
El Al B737 > B747-400
Air Algerie B738
JAT Yugoslav B727 > B737-300
Japan Air Lines B763
Brussels Air Lines BAe146

Ian - the British Airways B744 and the A380's Qantas and Singapore show as startups in content manager but for some reason do not show as such in the game content. Not a problem to me - these aircraft all flare on landing.

British Airways B763
British Airways A321
Alitalia MD82 > Airbus A321
KLM retro B738

Rob -

United Airlines B763 (100155)
Air Canada B763 (green)

Other -

Lufthansa B738 by cj187 > Airbus A321
Scandinavian B737 by nzms > Airbus A321
Aer Lingus B736 by cj187 > Airbus A320
United Airlines B763 (1020) by iced8383
American Airlines B763 (1278) by nzms
Emirates A380 by nzms
Germanwings B737 by cj187 > Airbus A319
Air Canada A320 by nzms > Airbus A319


Correct me if I'm wrong but I assume that models being reworked for TANE will not result in improved versions or even workable in TS12. I am thinking of uploading "as is"

Next thing is to see how this route loads and functions in TANE when I get my disk - I am not very confident. The biggest problem in keeping the game going has been the signalling and I had high hopes of improvement with interlocking towers.......

Might be a case of starting again from scratch.

A couple of questions I will be putting in the TANE forum but someone might know -

1. Will I be able to opt out of locked junctions in TANE?
2. Is there a way of loading a spreadsheet timetable into the session?

Paul
 
Back
Top