Locomotive cab

[aksingha]

Hi,
I am trying to get my cab and the control parts(with animation for Horn, reverser and lever) in the game. But i have some doubts which i want to clarify.

1. Do, i have to attach the cab and all the control parts to the main "engine" and then export, OR do i have to export the cab/interior and the controls separately. If separately then which folder. Should it be the Cab folder or the engine folder. This part confuses me a lot.

2. For now i want to animate only three objects- Horn, Reverser and Throttle. So, Do i have to make those particular parts a separate object and export or should they be attached to Some other part.

Sorry, i just don't get it. Someone please explain me. Thank you for any response

[GreatNortherner]

Hi,

[quote=]1. Do, i have to attach the cab and all the control parts to the main "engine" and then export[/quote]

Cabview and Engine shape file must be two seperate models/IGS's. Build the engine model with only those components that you would see from external camera views, then build a seperate cabview model that only contains elements which you would actually see from the inside of the cab. Check the hierarchy and naming conventions in the DevDocs. A third seperate model would be required for a passenger view (for example if you're modeling a DMU/EMU).

[quote=]2. So, Do i have to make those particular parts a separate object and export or should they be attached to Some other part. [/quote]

All animated parts/controls in the cabview must be part of the main cabview object. So if your static components of the cab are in the main hierarchy group 1_1000_cabview, you can put the controls (1_1000_reverser, 1_1000_throttle, etc.) as child groups to the main group. Animate them as described in the DevDocs, and export each animation seperately (one for reverser, one for throttle, and so on). Then finally export the entire model (cabview+controls) as a single IGS.

Hope that helps
Cheers
Michael

[aksingha]

Hi,

Cabview and Engine shape file must be two seperate models/IGS's. Build the engine model with only those components that you would see from external camera views, then build a seperate cabview model that only contains elements which you would actually see from the inside of the cab. Check the hierarchy and naming conventions in the DevDocs. A third seperate model would be required for a passenger view (for example if you're modeling a DMU/EMU).

All animated parts/controls in the cabview must be part of the main cabview object. So if your static components of the cab are in the main hierarchy group 1_1000_cabview, you can put the controls (1_1000_reverser, 1_1000_throttle, etc.) as child groups to the main group. Animate them as described in the DevDocs, and export each animation seperately (one for reverser, one for throttle, and so on). Then finally export the entire model (cabview+controls) as a single IGS.

Hope that helps
Cheers
Michael

Thank you That definitely cleared my doubt

[aksingha]

Also can anyone tell what names should i give to the control parts like Reverser,throttle and others. For now i have given the main cab as 1_0000_cab as per Dev Doc but it does not mention about other control parts.

[GreatNortherner]

You can name them whatever you like (I think), the important part should be that the group names are identical in the shape file and in the control section in the engine blueprint. So for example, if your reverser node is called "1_1000_revhandle", you have to add "revhandle" into the Transform Name field in the Control Value's Interface elements of the Reverser.

Cheers
Michael

[g_nash]

@ aksingha , what Max version are you using ? .

[aksingha]

You can name them whatever you like (I think), the important part should be that the group names are identical in the shape file and in the control section in the engine blueprint. So for example, if your reverser node is called "1_1000_revhandle", you have to add "revhandle" into the Transform Name field in the Control Value's Interface elements of the Reverser.

Cheers
Michael

@g_nash i am using Max9