Planeset [version 1.5.3 released 2006-10-24]
Moderator: Graphics Moderators
The rotors are much better, but compare the three N-bound views (attached at 4x).
If I rotate the nacelles, the paint jobs on both sides change, the tail changes in various ways (among other things, the horizontal portion is 50% wider when the nacelles are diagonal), and length of the nose changes. I think the wings flap too.
I realize I may seem picky here, but this is a matter of several percent of the sprite.
If you don't mind, I'll mix and match the parts of the bodies I like best, so they are consistent.
I'm afraid the center-of-sprite indicators, while a nice idea, don't help. Because the aircraft rotates around the offset point, it must always be at the same part of the aircraft, which is not necessarily the same part of the sprite. OTOH, they won't cause problems, so leave them in or take them out, as you please.
If I rotate the nacelles, the paint jobs on both sides change, the tail changes in various ways (among other things, the horizontal portion is 50% wider when the nacelles are diagonal), and length of the nose changes. I think the wings flap too.
I realize I may seem picky here, but this is a matter of several percent of the sprite.
If you don't mind, I'll mix and match the parts of the bodies I like best, so they are consistent.
I'm afraid the center-of-sprite indicators, while a nice idea, don't help. Because the aircraft rotates around the offset point, it must always be at the same part of the aircraft, which is not necessarily the same part of the sprite. OTOH, they won't cause problems, so leave them in or take them out, as you please.
- Attachments
-
- osprey.PNG (2.13 KiB) Viewed 3753 times
To get a good answer, ask a Smart Question. Similarly, if you want a bug fixed, write a Useful Bug Report. No TTDPatch crashlog? Then follow directions.
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Thank you for the version with body silhouettes in the rotor sprites; I was pretty sure you were right, but having the silhouettes makes it very obvious that the holes are where they belong.
I was trying to set the offset point to be the pixel at the center back of the wings, but it's set relative to the upper left corner of the sprite, so I'm not sure how much help it would be to have that pixel in any particular location.
I hate it when I do this. I complained about something, you accomodated, and now, to reward you for accomodating, I'm going to complain some more: I prefer the your previous renders; the symetrical ones with pixel jitter.
I'm off to remove the jitter and code, using the sprites from the top of this page.
I was trying to set the offset point to be the pixel at the center back of the wings, but it's set relative to the upper left corner of the sprite, so I'm not sure how much help it would be to have that pixel in any particular location.
I hate it when I do this. I complained about something, you accomodated, and now, to reward you for accomodating, I'm going to complain some more: I prefer the your previous renders; the symetrical ones with pixel jitter.
I'm off to remove the jitter and code, using the sprites from the top of this page.
To get a good answer, ask a Smart Question. Similarly, if you want a bug fixed, write a Useful Bug Report. No TTDPatch crashlog? Then follow directions.
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
It's a post from DaleStan with three attachments. Those of you who have been around a while probably have a pretty good idea what that means.
For those of you who don't, or want it spelled out anyway, I have coded the Osprey.
The acceleration is intentionally set very low, to show off the diagonal nacelles during "low-speed" flight.
The NFO has cursory comments; feel free to ask for better ones.
The nacelles are supposed to work as follows:
- Nacelles vertical for take-off, landing, in the purchase list and hangar, and whenever it is waiting at the gate
- Nacelles diagonal for taxiing and low-speed (<240 mph) flight
- Nacelles horizontal for cruising-speed flight
Known bugs:
- The nacelles refuse to return to vertical at a gate, although the rotors sometimes do (specifically: when the aircraft details window is open). The aircraft-details window updates properly.
- Some water-magic-blue pixels have snuck into the sprites.
For those of you who don't, or want it spelled out anyway, I have coded the Osprey.
The acceleration is intentionally set very low, to show off the diagonal nacelles during "low-speed" flight.
The NFO has cursory comments; feel free to ask for better ones.
The nacelles are supposed to work as follows:
- Nacelles vertical for take-off, landing, in the purchase list and hangar, and whenever it is waiting at the gate
- Nacelles diagonal for taxiing and low-speed (<240 mph) flight
- Nacelles horizontal for cruising-speed flight
Known bugs:
- The nacelles refuse to return to vertical at a gate, although the rotors sometimes do (specifically: when the aircraft details window is open). The aircraft-details window updates properly.
- Some water-magic-blue pixels have snuck into the sprites.
To get a good answer, ask a Smart Question. Similarly, if you want a bug fixed, write a Useful Bug Report. No TTDPatch crashlog? Then follow directions.
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
-
- Tycoon
- Posts: 3849
- Joined: 20 Jan 2003 14:51
- Location: Broadstone, Dorset
- Contact:
Slight problem
I use the planeset with great satisfaction, though I encountered a slight problem. Sometimes planes do get stuck on airports/heliports, they do not go to the next station unless I force them to do, and then they get stuck again.
Is this a common problem or I do something wrong.
Is this a common problem or I do something wrong.
Re: Slight problem
Which planes? What do you mean by "stuck"? What do you mean by "force"? Which TTDPatch version? ("latest" is not a version number.)Monty wrote:Sometimes planes do get stuck on airports/heliports, they do not go to the next station unless I force them to do, and then they get stuck again.
Is it similar to this problem? If so, please post a savegame there.
To get a good answer, ask a Smart Question. Similarly, if you want a bug fixed, write a Useful Bug Report. No TTDPatch crashlog? Then follow directions.
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Clarification
I use 2.0.1. alpha 42 version. The problem is not the same as in the other thread, though I encountered that one as well (with the AI's Zeppelins getting stuck on small airports).
In my case a plane or a helicopter lands on a heliport/airport and it goes to load/unload and remains in that position foreever, until I notice it and open it's go to menu and click "skip". But on it's next station it starts again.
I also noticed that the do load passangers but not mail, although there is plenty of mail at the station and they are not set to full load or to unload.
I don't remember which planes were these exactly as I simply sent them to hangar and sold them (if I replace it immediately the problem remains
).
Unfortunately I can not send a saved game as I already deleted it, but if it happens again I'll save one with that problem.
In my case a plane or a helicopter lands on a heliport/airport and it goes to load/unload and remains in that position foreever, until I notice it and open it's go to menu and click "skip". But on it's next station it starts again.
I also noticed that the do load passangers but not mail, although there is plenty of mail at the station and they are not set to full load or to unload.
I don't remember which planes were these exactly as I simply sent them to hangar and sold them (if I replace it immediately the problem remains

Unfortunately I can not send a saved game as I already deleted it, but if it happens again I'll save one with that problem.
- SuperTycoon
- Chief Executive
- Posts: 733
- Joined: 24 Jun 2004 20:05
I guess I should have said "multiple loading states". Unfortunately, as far as I can tell, there is no reliable way to detect what type of airport the airplane is using. (We can tell the difference between heliports and airports.) We could do an ugly hack based on the direction the plane is facing. Byte 63 might contain useful information, but I don't see how it could be used.In a different thread, krtaylor wrote:Wait a minute.... I've actually thought about this a bit for the Planeset. If we can detect whether the plane is at a large or a small airport, then we could have the door open and stairs appear next to it; or, for the cargo aircraft, show the nose open. Or some such.DaleStan wrote:[However, the only things that commonly carry more than 255 units are airplanes and they don't usually have different loading states, so the point is pretty moot.
To get a good answer, ask a Smart Question. Similarly, if you want a bug fixed, write a Useful Bug Report. No TTDPatch crashlog? Then follow directions.
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
I think it would really add to things.
Development Projects Site:
http://www.as-st.com/ttd
Japan, American Transition, Planeset, and Project Generic Stations available there
http://www.as-st.com/ttd
Japan, American Transition, Planeset, and Project Generic Stations available there
OK, here's a new Osprey:
- CC livery
- No more blue in the rotors
- Now has nacelles horizontal in purchase list/hangar
- Nacelles still misbehave (see previous post) (patch bug)
@krtaylor: What's still on the todo before the first official release of the the company-colored PlaneSet?
I can come up with:
- Fixed livery for Ruslan and Shorts 330
- Code for Shorts 330 (is 459 going to do this?)
- Fix whatever is wrong with the 747-400.
- Loaded states for the Chinook (?)
(Attachments removed--included in latest Planeset)
- CC livery
- No more blue in the rotors
- Now has nacelles horizontal in purchase list/hangar
- Nacelles still misbehave (see previous post) (patch bug)
@krtaylor: What's still on the todo before the first official release of the the company-colored PlaneSet?
I can come up with:
- Fixed livery for Ruslan and Shorts 330
- Code for Shorts 330 (is 459 going to do this?)
- Fix whatever is wrong with the 747-400.
- Loaded states for the Chinook (?)
(Attachments removed--included in latest Planeset)
Last edited by DaleStan on 06 May 2005 10:30, edited 1 time in total.
To get a good answer, ask a Smart Question. Similarly, if you want a bug fixed, write a Useful Bug Report. No TTDPatch crashlog? Then follow directions.
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Who is online
Users browsing this forum: Amazon [Bot] and 21 guests