Illegal_Alien wrote:We dutch people can do it all!
Damn straight, mate!
As for the tool I'm working on: I took a crash course in computational trigonometry and I should be able to release something workable by Sunday evening.
The thing i wanted to know is, how, when you converted it, did you get the size right? My GWR railcar is either too big or too small, and seen as palette express can only convert 5 files at a time, trial and error is becoming very tedious...if there's a knack to it, please, tell me, before my eyes melt from their sockets and my hands drop into the oblivion underneath my computer table! Thanx in advance,
Blackfour
Ok, i have solved the nose-to-nose coupling of the engines now i have one ther problem; Whatever i do the Vehicle creator crashes on the passenger wagon So no i have a TGV Duplex Engine without wagons .
Crash occurse when i am gonna save it as a .DAT file I am 100% sure that i used the correct pallete and the sizes in KB of the sprites from the engine and the passengers are the same. so he is not to big.
Illegal_Alien wrote:Its on hold atm. I am waiting for the MSTS2Locomotion from Scrat. And then i will go further with the TGV Duplex (Or even a nice TGV pack )
Thanks for you're answer, and god, I hope that everything goes well and fast . That tgv pack sounds stunning .
Oh well, stay cool, no need for any rush , I will wait silently.
It won't solve palette issues though. ChrisCF was supposed to sort that, but he seems to have disappeared in disgust after that unfortunate episode with the humourless nordic one.
But I really, really, really, cross my heart and hope to die, will sit down and sort that stupid tilting issue tomorrow.
www wrote:If you fix that annoying off-center problem with the vc expect loads of mods from me
The problem with that is that Locomotion's *original* vehicles have all been cropped to display just the vehicle and not the empty spaces. Hence, they are all differently sized. To rectify this I'd have to parse through all the images and generate the sprite xml (xofs and yofs) individually.
As it is now, Vehicle Creator assumes an uncropped sprite and measures the dimensions of the first sprite and bases all the subsequent sprites (xofs and yofs) on that measurement, like one of Oppie's (240x240) or something generated by MSTS2Locomotion:
scrat wrote:
The problem with that is that Locomotion's *original* vehicles have all been cropped to display just the vehicle and not the empty spaces. Hence, they are all differently sized. To rectify this I'd have to parse through all the images and generate the sprite xml (xofs and yofs) individually.
As it is now, Vehicle Creator assumes an uncropped sprite and measures the dimensions of the first sprite and bases all the subsequent sprites (xofs and yofs) on that measurement, like one of Oppie's (240x240) or something generated by MSTS2Locomotion:
err
scrat wrote:In short, I'm aware of the problem but it's pretty damn low on my "to do" list (definitely *after* "invading France").
Re: France. <whispers>I'm not seriously contemplating invading France, just as I'm not seriously contemplating addressing the cropped images issue. I have too much work to do as it is.</whispers>
Attachments
Uncropped image.
Generated using msts2locomotion + a bmp2pngwith correct palette photoshop script
MSTS2Locomotion_photoshoppalettemacro_000.png (1.82 KiB) Viewed 3618 times