[thegrindre]

 captain_bazza, on 21 May 2010 - 09:39 PM, said:

Hi'ya Richard, thanks for the info. I guess if you omitt the emitters in TSM, then there'll be nothing to affect an external plug-in from displaying such emissions in their place.

Cheers Bazza

I believe 3DC works similarly. Once the model has been exported, we go to the .eng file to make the fine adjustments.

[espee]

 captain_bazza, on 21 May 2010 - 09:39 PM, said:

Hi'ya Richard, thanks for the info. I guess if you omitt the emitters in TSM, then there'll be nothing to affect an external plug-in from displaying such emissions in their place.

Cheers Bazza

Well no, but the steam, smoke and lighting effects are hardcoded into MSTS and the .eng file parameters calls the appropriate sub-routine. Without the parameters in the .eng file MSTS does not do anything. You do not have to have any calls from the eng file if you don't want, MSTS does not care.

So you need the eng file to tell MSTS what sub-routines to run and how to run them. An external plug-in in OR would need to access the eng file to get the variables and then execute the sub-routines using the variables and feed them back to OR.

Not a particularly elegant way of doing something if you ask me - well I know you didn't but...

An external plug-in could be inserted into OR as a module, likely the same as MSTS, that way it is an internal call and a lot faster. I don't see the need for an external one, but I am not part of the OR team so I have no idea of the complexity's, and I never took computer programming as a career so am really out of my depth.

With MSTS you do not have to actually have wheels, bogies, couplings etc, the wheels don't even have to be touching the rails or in gauge. MSTS displays whatever your shape file is called, and animates as described in the shape file. ie if it is exported as a loco and has a cabview then you can drive a 1 poly thing or a brick... you do not even have to have sounds...

And you only have to include the coupling code in the eng file for you to couple one brick to another, same with every other effect, lights will shine and smoke will spew forth just with the code, you don't need a physical ? headlight or chimney/exhaust or coupler.

[thegrindre]

That is right, Richard. You could drive a tree down the tracks if you wanted too with or without steam or smoke or lights or wheels.
I've removed the firebox glow tag on one model and the lights tag on another. I even turned the smoke off by accident one time. 3DC will spit out a default .eng file for you. It's up to us to tweak it as necessary.

[captain_bazza]

Don't laugh, my first successful import into MSTS was a teapot!

The smoke n steam emitters will be independent of MSTS code.

Cheers Bazza

[bpratt]

Most of that is way over my head but I can say that i have never put emitter points on one of my models in 3DCPro and they all smoke.

[captain_bazza]

Thanks Bill, the points for MSTS are entered in the relevant section of the ENG file. OR's approach will be different, but more flexible and with much better effects for our steamers, and those other stinky things, aka diseasels.

Cheers Bazza

[pwillard]

Count me "in"

[captain_bazza]

Thanks, PW, which modelling prog do you use, or have the most experience with?

Cheers Bazza

[pwillard]

 captain_bazza, on 26 May 2010 - 07:16 PM, said:

Thanks, PW, which modelling prog do you use, or have the most experience with?

Cheers Bazza

Oops Sorry. Forgot to say.

3D Canvas Pro (although I have TSM and have used GMAX neither really thrill me much after using 3DC Pro)
My Website