Preventing autogen exclusion by custom ground polygons: Difference between revisions
From FSDeveloper Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
* Cleaning up ASM code made by GMax (removing extra calls, crashtrees, etc) reduces autogen exclusion | * Cleaning up ASM code made by GMax (removing extra calls, crashtrees, etc) reduces autogen exclusion | ||
* Adding transformations (scaling, translating) seems not to affect the autogen exclusion | * Adding transformations (scaling, translating) seems not to affect the autogen exclusion | ||
Add the following line at the end of the ASM code (just before the return) seems to work: | |||
SCALE_AGL OBJECT_0_RETURN, 0, 0, 0, 0, 0, 0, 0, 0, 0 | |||
Revision as of 14:09, 18 November 2009
 | This page is a work-in-progress. Generic message - Please note some detail may possibly be missing or incorrect. |
Note: at the moment this are just some personal notes from testing. I still have to continue the full testing and make it into a nice article.
- v2 value of the RefPoint does not matter
- RefPoint type does not matter
- Rotating in GMax, instead of entering heading in MakeMDL reduces autogen exclusion
- Cleaning up ASM code made by GMax (removing extra calls, crashtrees, etc) reduces autogen exclusion
- Adding transformations (scaling, translating) seems not to affect the autogen exclusion
Add the following line at the end of the ASM code (just before the return) seems to work:
SCALE_AGL OBJECT_0_RETURN, 0, 0, 0, 0, 0, 0, 0, 0, 0
