models have a limit of 512 triangles, being a nice power of 2.
shadow length (max) is set in the lighting tags. the normal grassland lighting has a maximum distance of 64 or so (by memory). i'm not sure what the maximum is, but it should be able to go longer, and thus taller models won't have truncated shadows.
models needed for Greek Plugin
The reason you're getting no shadows is because Apathy sucks. If you use Vegas you can set up all the triangles that are replaced by model, and that are walking/flying impassible, which points grab the mesh (you know how myth 2's models 'stick' when you place them), and if you're doing water models, which points animate like media, and which surfaces reflect. I'm pretty sure Vegas is up for grabs on TFV site, but if it isnt I can email it to you some time.
Hey A-Red!
wassup!
At last it I discovered that it was the beta loathing I was using on my mac that didn't create shadows.
I tested it on a PC and it worked.
I do have VEgas, I don't know how to use it though, but I'll give it a try for mesh grabbing.
Basically what's the benefit of doing that instead of just covering the mesh with it?
wassup!
At last it I discovered that it was the beta loathing I was using on my mac that didn't create shadows.
I tested it on a PC and it worked.
I do have VEgas, I don't know how to use it though, but I'll give it a try for mesh grabbing.
Basically what's the benefit of doing that instead of just covering the mesh with it?
I might be able to offer some additional advice, though it's been a while since I actually worked with any of this stuff and I'm not up to speed on the current state of the engine, so my figures might be out-dated.
A Myth model can have a maximum of 512 polygons. However, there is a bug in Vegas that causes it to spit out any models with more than 510 polygons.
Apathy has a lot of broken functionality. None of the vertex functions work, and the design of the interface makes it nearly impossible to use some of the surface editing functions. Also, the collection (.256) tags Apathy generates are shit. You must use Amber to replace all of the collection bitmaps if you want your models to look good.
With the above in mind, I also strongly suggest you not use individual collection tags for each model if you can help it. If your map has multiple models that all use similar color palletes for their textures, and/or different models that use identical textures, you can combine all of the textures into one master collection tag and discard the duplicate textures. Then scrap all of individual collection tags Apathy has generated. Then use Fear to change all of the models' collection reference (CORE) tags so they reference the master collection. This process can be time-consuming, but it will make the in-game performance much better because the Myth engine should less texture data to chew through. In case you didn't already know, the Myth engine does not pre-cache texture data--model textures are loaded on-the-fly as you play through the level. Thus, maximum efficiency is vital.
On the subject of using models to deform the mesh (i.e. sticking to the mesh), this isn't really necessary unless you are using a model to build a ramp or bridge, or similar structure. If you just have a basic building sitting on a flat mesh, the deform mesh setting isn't needed. Well, it can help keep things looking better if you have massive explosions that cause HUGE mesh ripples, but even then I don't think it's really helpful or necessary.
A long time ago I wrote up some directions on using Vegas. The text file might still be floating around the Magma Hotline server. Ozone might also have a copy.
If you are planning to have rooved buildings that units can walk in and out of, consider three possible ways to help prevent the units from disappearing entirely from the camera and getting lost by the player. The first solution is the simple Bungie method of making sure the building is tall enough so that when the camera zooms in all the way, it penetrates the roof of the building. Another method is the technique iggy used when making the Nionel buildings in Jinn. Basically, the buildings are annimated models with two frames -- the first being a the "roof intact" frame, the second being the "roof ripped away" frame. The annimation is triggered with a simple script that detects the presence of a player unit entering the building. A third option is to set part of the roof texture to be partially transparant. You can also use different texture permutations: say 0% transparent and 50% transparent. The permutations can be scripted to change at the appropriate time just like with the annimated method described above. Note that the transparent method will only allow you to see the units inside the building, not click on them, so you will still want to make sure the building is of sufficient height so the player can zoom the camera in through the roof to interact with the units.
Models can have annimated textures. By default, textures in a model collection all have one frame each. You can easily use Amber to assign additional frames. I used this technique once to make the walls of a crypt have a flickering torchlight effect.
One last tip on optimizing models for Myth. Consider the angle of the in-game camera and delete all polygons in the model that the camera will never see. This will help you get closer to the 510 count and make the model quicker to load and easier to texture map. 510 polygons doesn't seem like a lot, but with a the right techniques, you can make some amazingly detailed models with far less than that number.
Good luck!
A Myth model can have a maximum of 512 polygons. However, there is a bug in Vegas that causes it to spit out any models with more than 510 polygons.
Apathy has a lot of broken functionality. None of the vertex functions work, and the design of the interface makes it nearly impossible to use some of the surface editing functions. Also, the collection (.256) tags Apathy generates are shit. You must use Amber to replace all of the collection bitmaps if you want your models to look good.
With the above in mind, I also strongly suggest you not use individual collection tags for each model if you can help it. If your map has multiple models that all use similar color palletes for their textures, and/or different models that use identical textures, you can combine all of the textures into one master collection tag and discard the duplicate textures. Then scrap all of individual collection tags Apathy has generated. Then use Fear to change all of the models' collection reference (CORE) tags so they reference the master collection. This process can be time-consuming, but it will make the in-game performance much better because the Myth engine should less texture data to chew through. In case you didn't already know, the Myth engine does not pre-cache texture data--model textures are loaded on-the-fly as you play through the level. Thus, maximum efficiency is vital.
On the subject of using models to deform the mesh (i.e. sticking to the mesh), this isn't really necessary unless you are using a model to build a ramp or bridge, or similar structure. If you just have a basic building sitting on a flat mesh, the deform mesh setting isn't needed. Well, it can help keep things looking better if you have massive explosions that cause HUGE mesh ripples, but even then I don't think it's really helpful or necessary.
A long time ago I wrote up some directions on using Vegas. The text file might still be floating around the Magma Hotline server. Ozone might also have a copy.
If you are planning to have rooved buildings that units can walk in and out of, consider three possible ways to help prevent the units from disappearing entirely from the camera and getting lost by the player. The first solution is the simple Bungie method of making sure the building is tall enough so that when the camera zooms in all the way, it penetrates the roof of the building. Another method is the technique iggy used when making the Nionel buildings in Jinn. Basically, the buildings are annimated models with two frames -- the first being a the "roof intact" frame, the second being the "roof ripped away" frame. The annimation is triggered with a simple script that detects the presence of a player unit entering the building. A third option is to set part of the roof texture to be partially transparant. You can also use different texture permutations: say 0% transparent and 50% transparent. The permutations can be scripted to change at the appropriate time just like with the annimated method described above. Note that the transparent method will only allow you to see the units inside the building, not click on them, so you will still want to make sure the building is of sufficient height so the player can zoom the camera in through the roof to interact with the units.
Models can have annimated textures. By default, textures in a model collection all have one frame each. You can easily use Amber to assign additional frames. I used this technique once to make the walls of a crypt have a flickering torchlight effect.
One last tip on optimizing models for Myth. Consider the angle of the in-game camera and delete all polygons in the model that the camera will never see. This will help you get closer to the 510 count and make the model quicker to load and easier to texture map. 510 polygons doesn't seem like a lot, but with a the right techniques, you can make some amazingly detailed models with far less than that number.
Good luck!
Mauglir
comprehensive model making guide...
comprehensive model making guide...
would be good if someone compiled the info and made a definitive how to guide...
would be good if someone compiled the info and made a definitive how to guide...
if one does not learn from the failings of the past they are likely to suffer its return.
time flys
carlinho wrote:shoot...that was 2 years ago....damn....
yes time flys in the world of myth making... I need to finish this stuff up so i can foster my other hobbies
if one does not learn from the failings of the past they are likely to suffer its return.