This link no longer works, at least for me. I still need this zip file. :-/ Thanks
-
Guest Please check out the Help Wanted thread in Ickie's NewsHawks.
The future of the Outhouse depends on you!
Help Wanted
GMax and LOD's
- Thread starter stuart277
- Start date
This link no longer works, at least for me. I still need this zip file. :-/ Thanks
The site seems to have disappeared, bother! You could make your own toolbar, as per the thread earlier this year: Creating toolbars in Gmax for MeshTools If you really need the Bamse toolbar I can upload it after the holidays.
misson
Charter Member
Thank you!
Thank you
Cheers
Mario
U understood well and same time you gave the answer to me. Now i need to get the correct proceeding.
Thank you
Cheers
Mario
Blood_Hawk23
Charter Member
Glad you found it. I may need it again at some point. You never know.
misson
Charter Member
Hello! As you see I'm trying to generate lods in this plane of M Shupe and MVG3d for use in CFS2. I did like the tutorial doc says in the corresponding steps and actually could do lods with another plane, but in this case I'm having problems.
1) I do the dummy and put everything to zero as pic1.
2) I use select and link tool and move the cursor in areas, but here the problems begin, only parts is white and selected, so I select and I link various parts as in pic 2.
3) when I select to copy and rename the _LOD_xxx (to clone), only a part of the plane is illuminated and is selected. As this hapens, intuitively i have done is to group all parties and name them as NAME_LOD_050 , but when using the MODIFY TAB to start reducing polys, gmax crash to desktop.
What am I doing wrong in this process? thank you very much.
Mario
1) I do the dummy and put everything to zero as pic1.
2) I use select and link tool and move the cursor in areas, but here the problems begin, only parts is white and selected, so I select and I link various parts as in pic 2.
3) when I select to copy and rename the _LOD_xxx (to clone), only a part of the plane is illuminated and is selected. As this hapens, intuitively i have done is to group all parties and name them as NAME_LOD_050 , but when using the MODIFY TAB to start reducing polys, gmax crash to desktop.
What am I doing wrong in this process? thank you very much.
Mario
misson
Charter Member
I'm not sure what you are doing...
Hello Allen! Well... in the gmax scenery tutorial (into gmax/gamepack/fs2004/docs folder) u will find a way to make lods from a simple model (in this tut a house)
Following this tut , i could make lods a simple model of 1Mb , after that the model was increased to 3Mb, i ´ve exported and compilled it succefully like a multilod fs2004 model. In fact using ACM i can see the lods.
So i ´ve tried with the CANT Z 1007 trying to add lods using the same tut.
My problems begin when i try to select the plane to clone it , and rename it as xxx_LOD_XXX .
When i do click on the plane pressing shift at same time (to open the clone window) only a part (any part ) of the plane is selected (and not all the plane) , so i only could to clone a single part of the plane .
how can i do to clone the entire plane to rename it to a xxx_LOD_XXX?
The main gmax source is 24Mb , after make lods it goes up to 50Mb and that perhaps is too heavie source ! so that could be the reason why i have a CTD when i want to modify the polys.
Thanks
Mario
I am going to "stick" this thread as there is so much good info here. Thanks gents for pulling it together. 
misson
Charter Member
Thank you Allen , that sounds as solution, any tut? how i do that? simply do click aroud the blue box and drag it ? is the dummy box u are talking about? What about the source weight , could that be a problem ?
Sorry if i do too many questions.
Cheers
Mario
misson
Charter Member
Ok , I think that i got it. Now running with other troubles, I´ll let u know later.
Thank u very much
Mario
misson
Charter Member
Hi guys again! When i try to export from gmax to a model, i got this error log. Only happen when i try to export a multilod model.
I am worry specially for the "error A20xx: initializer magnitude too large for specified size" issues, the others are not a great problem.
Thank u
Mario
I am worry specially for the "error A20xx: initializer magnitude too large for specified size" issues, the others are not a great problem.
Thank u
Mario
Unfortunately, I have seen this several times over the years.
It may be related to stray vertices, too many polys, too many parts, or weird part construction, and more. Its not a specifically name error; more of a catch all for mesh issues or over-running the 65536 limits on addressable storage.
I have been fighting this issue for 3 months on the Bounty project, and sent it last week to Hairyspin for another set of eyes to looks at it.
I am hoping he sees something I do not. :-/
Blood_Hawk23
Charter Member
Mario,
I sent you a message. Let me know if it helps.
Milton,
Yeah currently the whole model (with the new LOD) has 135402 polys. I noticed a couple little things and thats in my message to Mario.
Its a very complex model so there is going to be issues. I don't know how you all can keep it strait. So many parts. I think I've advised all that I can. The rest is beyond me. I leave it to the Masters.
I sent you a message. Let me know if it helps.
Milton,
Yeah currently the whole model (with the new LOD) has 135402 polys. I noticed a couple little things and thats in my message to Mario.
Its a very complex model so there is going to be issues. I don't know how you all can keep it strait. So many parts. I think I've advised all that I can. The rest is beyond me. I leave it to the Masters.
We have a problem here with opaque error messages and as Milton says there are a number of possible causes. Misson may have too many polys or not enough textures, others have the System Unit other than at 1 unit = 1 metre and there's always the possibility of having borked something together with thick fingers. However there's another woodchuck in the woodpile to watch out for: scale not at 100%
I came across this again by accident because the exporter for CFS3 flags up scaling errors directly, whereas other exporters are less than explicit. How do you know if this is the case? Time to look at a little-used feature of Gmax (little used in FS developing anyway...), the Track View.
The Track View opens a window which can be chock-full of information, here for the object hull:–
and that's not all that can be shown, the list of bumf extends a lot further than this screenshot. What interests us is the Scale data (highlighted) which here is 100% on all three axes – so far so good.
To make hunting down scaling errors easier, filter the information:–
This will show only the scale information for each object:–
I came across this again by accident because the exporter for CFS3 flags up scaling errors directly, whereas other exporters are less than explicit. How do you know if this is the case? Time to look at a little-used feature of Gmax (little used in FS developing anyway...), the Track View.
The Track View opens a window which can be chock-full of information, here for the object hull:–
and that's not all that can be shown, the list of bumf extends a lot further than this screenshot. What interests us is the Scale data (highlighted) which here is 100% on all three axes – so far so good.
To make hunting down scaling errors easier, filter the information:–
This will show only the scale information for each object:–
Last edited:
