great Spooger! Download the engine demo. It displays all the engine's features and capabilities. The latest version is pretty kewl.
sexy screenie!
sexy screenie!
Last edited:
Need help with static meshes
- Thread starter afecelis
- Start date
-
Two Factor Authentication is now available on BeyondUnreal Forums. To configure it, visit your Profile and look for the "Two Step Verification" option on the left side. We can send codes via email (may be slower) or you can set up any TOTP Authenticator app on your phone (Authy, Google Authenticator, etc) to deliver codes. It is highly recommended that you configure this to keep your account safe.
Great Vito! you guys are going to spoil us, h ehe he h =)
I made my first attempt with my ase file. I exported the whole geometry as a tsatic mesh and it imported ok. Obviously collision went nuts but I think from now on it will be a matter of test and error.
thnx Vito!
I made my first attempt with my ase file. I exported the whole geometry as a tsatic mesh and it imported ok. Obviously collision went nuts but I think from now on it will be a matter of test and error.
thnx Vito!
Cool!! Can't wait to see it with all of the textures and stuff.
I can ask will (islington) to share the source MAX file for these as well as all of the other stuff not shown here... http://www.planetunreal.com/Spooger/Decos.html
As for the textures, only a small amount (maybe 10%) are shown here... http://www.planetunreal.com/Spooger/Images_Set-1.html
Those are just a few of the more game related ones but we have a lot more, plus 6 tuxture set CD's.
I can ask will (islington) to share the source MAX file for these as well as all of the other stuff not shown here... http://www.planetunreal.com/Spooger/Decos.html
As for the textures, only a small amount (maybe 10%) are shown here... http://www.planetunreal.com/Spooger/Images_Set-1.html
Those are just a few of the more game related ones but we have a lot more, plus 6 tuxture set CD's.
Good thing to hear about the trees. It is indeed a bothersome point when it comes to realistic mapping. I might also have a thing going on with a bunch of landscape architects at the university. I presented my stuff and they seem intersted in how UTcan be used in presenting their projects and such. I know that there is also different software, such as OnyxTreePro and SpeedTree, but I haven't tried it myself.
I got got everything into the the Runtime editor except for the a few meshes that I created in Unreal and hence don't have the ASE files. there seem to be some differences in colour and light as well, but it might have to do with me using different textures now.
I havn't done anything with this project for aobut 4 months now and I got some new ideas for the middle part of the building....Well one thing at the time, first I better get the thing running. Thanks for your support Vito!
Spooger, I'll mail you right away!
I got got everything into the the Runtime editor except for the a few meshes that I created in Unreal and hence don't have the ASE files. there seem to be some differences in colour and light as well, but it might have to do with me using different textures now.
I havn't done anything with this project for aobut 4 months now and I got some new ideas for the middle part of the building....Well one thing at the time, first I better get the thing running. Thanks for your support Vito!
Spooger, I'll mail you right away!
Attachments
The trees on the spoogers site are low(ish) poly versions intended for the old UT engine. The masked textures are made the old way with 0-pallet transparency.
I have made some higher poly lofted trees with alpha masked texture suitable for the new engine that look more realistic. I also have quite a few bushes and flowers if you need them. Let me now what kinds of trees you need eg fir,oak etc and I will put them in a pack for you
I have made some higher poly lofted trees with alpha masked texture suitable for the new engine that look more realistic. I also have quite a few bushes and flowers if you need them. Let me now what kinds of trees you need eg fir,oak etc and I will put them in a pack for you
Attachments
Last edited:
Hey Will, those trees look amazing. Anything that fits an architectural presentation will do. In fact, I'd love to use all of them!
Spooger:
I was able to texture the house and import it, although some problems came up. I just wrote you an email with details.
cheers!
Spooger:
I was able to texture the house and import it, although some problems came up. I just wrote you an email with details.
cheers!
Will, I saw no shadows in the screenshot. Do they cast shadows?
ps. About the screenshots (above) : I removed the window (glass) brushes since I still don't know how to create transparent textures. I tried to create one following a tut I found but all I got was a frozen editor, so, If anyone knows about a good tut on how to create them please post!!!!
ps2. Spooger: I tried the same exercise of the house in ut2k3 and the results were exactly the same.
cheers!
ps. About the screenshots (above) : I removed the window (glass) brushes since I still don't know how to create transparent textures. I tried to create one following a tut I found but all I got was a frozen editor, so, If anyone knows about a good tut on how to create them please post!!!!
ps2. Spooger: I tried the same exercise of the house in ut2k3 and the results were exactly the same.
cheers!
Last edited:
Thanks 
I made those trees about a year ago for a project that did not get off the ground. I will have a closer look at them this weekend to make sure there are no problems. I think I will at least need to import simple Karma collision models. At the moment the whole tree trunk and branches are the collision and it only needs the area the player can touch to be considered in the calculations.
afecelis, In real-time rendering foliage is made with sheets and masked textures to minimize the poly count unlike max where the individual leaves can be modeled, and so cast shadows.
In Unreal, by far the best way to produce tree shadows is with a projector. A good example is in the map that comes with runtime EM_Runtime.urt. Also have a look at the tutorial on UDN
http://udn.epicgames.com/Content/ProjectorsTutorial
I made those trees about a year ago for a project that did not get off the ground. I will have a closer look at them this weekend to make sure there are no problems. I think I will at least need to import simple Karma collision models. At the moment the whole tree trunk and branches are the collision and it only needs the area the player can touch to be considered in the calculations.
afecelis, In real-time rendering foliage is made with sheets and masked textures to minimize the poly count unlike max where the individual leaves can be modeled, and so cast shadows.
In Unreal, by far the best way to produce tree shadows is with a projector. A good example is in the map that comes with runtime EM_Runtime.urt. Also have a look at the tutorial on UDN
http://udn.epicgames.com/Content/ProjectorsTutorial
I found a couple of realistic trees at:
http://www.planetunreal.com/staticreality (the link is calle "tree set" and can be found at the bottom of the page) The download contains a ut2k3 mesh package so it can't be used by the runtime, but it can still be worth to take a look on how they were made
http://www.planetunreal.com/staticreality (the link is calle "tree set" and can be found at the bottom of the page) The download contains a ut2k3 mesh package so it can't be used by the runtime, but it can still be worth to take a look on how they were made
Great! Yep! I was wondering from the runtime map; the leaves move and a shadow is casted (and I think it moves too). The projector is a beautiful trick (work around) in the engine. I'll look into the link you sent me.
Even just as tree models, they look impressive! Have fun this weekend checking them. If there's anything we can do to help please let us know.
cheers!
Even just as tree models, they look impressive! Have fun this weekend checking them. If there's anything we can do to help please let us know.
cheers!
oooooooooppppps!
I did a full giant one and whole ase.
My bad?
Following your tutorial it says when you're done texturing you must collapse all the meshes and attach all of them into one.... and so I did.
So, shall I export things by chunks?
Will their location in space be preserved ?
I did a full giant one and whole ase.
My bad?
Following your tutorial it says when you're done texturing you must collapse all the meshes and attach all of them into one.... and so I did.
So, shall I export things by chunks?
Will their location in space be preserved ?
LOL... not a problem man. It's OK to do that as a "how might it look" thing but it's not such a good idea if you want a good working map.
OK, it's a lot of info but maybe it will help...
When I talk about collapsing all the meshes in the tutorial I was referring to a group of objects like several pipes, etc.. Not so much the whole map in a single shot. But that's ok, you just got a look at how it might look once everything is imported.
As best as you can, it's a good idea to import "chunks" as you call it, like all external walls that touch (ones that "touch" is the key word here). If the internal walls are joined with the external walls then go ahead and do those at the same time too. It's a matter of trial and error when it comes to doing a structure (walls/floors/roof) as an ASE file, remember it's not the best approach, but for a down and dirty VR it will do what is needed. In some cases geometry that overlaps in MAX might look OK in the Runtime if it is exported out together, other times it looks worse than if it was exported alone. Again, it's trial and error at first, but you will start to see a pattern in time as to what looks/works best.
Just try and break things down into related groups (but not MAX "groups", you know what I mean), once you have all of the sections of geometry for export it's a good idea to relocate the house center and ground elevation to the 0,0,0. This way when it's a static mesh in Unreal your insertion point is not way off in left field from the static mesh. Remember, Unreal does NOT use the object pivot point that MAX/VIZ uses, it only uses the MAX/VIZ 0,0,0 grid location as it's insertion point in Unreal. So, to relocate everything into a better position, you might want to select EVERYTHING in MAX, use the actual "group" command, use move and relocate the house to that 0,0,0, then when done you can "Ungroup" everything again. Now you have a near by insertion point (0,0,0) for Unreal.
Next simply select each chunk of geometry and use the "Export Selected" command to create the individual ASE files. Give them names that best relate to the "Chunks", not an easy task sometimes. I name them in MAX and then use that same name for the exported ASE file, that way I can come back later and I know what chunk relates to what ASE. Cool?
Last, to answer your question about placing the chunks in Unreal... yes, they will retain the position given in MAX if you place them in the Unreal Editor by right clicking (as you would a normal static mesh insertion) in the same spot each time in the editor. How I do this is I use the "Top" view port at full screen, I set the grid to something like 32 or 64, and then zoom all the way in as far as I can over Unreals 0,0 (it's a little thicker grid lines and a little darker, ya know?), once zoomed in you have what looks like a crosshair that you can right click on each time to insert each of the static meshes. I just keep the Static Mesh browser open and off to the side, selecting each item and right clicking to place it until they are all in. That way I know I'm hitting the same insertion point each time in Unreal.
EDITED:
Another good thing about working this way... as you find surfaces that don't look right in Unreal you can go back to MAX and work with that chunk of geometry to fix it, then export that ASE chunk again (instead of the whole map thing, less time that way). But remember to use the same name and replace/update the older ASE file, then re-import into Unreal. The real cool thing is that you don't have to insert it again into the scene, since once you replace it in the Static Mesh Pack and save it, the editor will display the updated chunk in your map. It's fixed.
Hey VITO!!! Do you know of a command line that we could be using to insert the Static Meshes into the same location, instead of doing it the way I have been doing it? *Fingers Crossed*
OK, it's a lot of info but maybe it will help...
When I talk about collapsing all the meshes in the tutorial I was referring to a group of objects like several pipes, etc.. Not so much the whole map in a single shot. But that's ok, you just got a look at how it might look once everything is imported.
As best as you can, it's a good idea to import "chunks" as you call it, like all external walls that touch (ones that "touch" is the key word here). If the internal walls are joined with the external walls then go ahead and do those at the same time too. It's a matter of trial and error when it comes to doing a structure (walls/floors/roof) as an ASE file, remember it's not the best approach, but for a down and dirty VR it will do what is needed. In some cases geometry that overlaps in MAX might look OK in the Runtime if it is exported out together, other times it looks worse than if it was exported alone. Again, it's trial and error at first, but you will start to see a pattern in time as to what looks/works best.
Just try and break things down into related groups (but not MAX "groups", you know what I mean), once you have all of the sections of geometry for export it's a good idea to relocate the house center and ground elevation to the 0,0,0. This way when it's a static mesh in Unreal your insertion point is not way off in left field from the static mesh. Remember, Unreal does NOT use the object pivot point that MAX/VIZ uses, it only uses the MAX/VIZ 0,0,0 grid location as it's insertion point in Unreal. So, to relocate everything into a better position, you might want to select EVERYTHING in MAX, use the actual "group" command, use move and relocate the house to that 0,0,0, then when done you can "Ungroup" everything again. Now you have a near by insertion point (0,0,0) for Unreal.
Next simply select each chunk of geometry and use the "Export Selected" command to create the individual ASE files. Give them names that best relate to the "Chunks", not an easy task sometimes. I name them in MAX and then use that same name for the exported ASE file, that way I can come back later and I know what chunk relates to what ASE. Cool?
Last, to answer your question about placing the chunks in Unreal... yes, they will retain the position given in MAX if you place them in the Unreal Editor by right clicking (as you would a normal static mesh insertion) in the same spot each time in the editor. How I do this is I use the "Top" view port at full screen, I set the grid to something like 32 or 64, and then zoom all the way in as far as I can over Unreals 0,0 (it's a little thicker grid lines and a little darker, ya know?), once zoomed in you have what looks like a crosshair that you can right click on each time to insert each of the static meshes. I just keep the Static Mesh browser open and off to the side, selecting each item and right clicking to place it until they are all in. That way I know I'm hitting the same insertion point each time in Unreal.
EDITED:
Another good thing about working this way... as you find surfaces that don't look right in Unreal you can go back to MAX and work with that chunk of geometry to fix it, then export that ASE chunk again (instead of the whole map thing, less time that way). But remember to use the same name and replace/update the older ASE file, then re-import into Unreal. The real cool thing is that you don't have to insert it again into the scene, since once you replace it in the Static Mesh Pack and save it, the editor will display the updated chunk in your map. It's fixed.
Hey VITO!!! Do you know of a command line that we could be using to insert the Static Meshes into the same location, instead of doing it the way I have been doing it? *Fingers Crossed*
Last edited:
ROFL !!!!!! 
Man! No wonder! Thanx a lot for the explanation. It's pretty logical and I can't wait to try it out. And what about collision. Does it work better this way?
Has the unreal level editing technique changed from added brushes to static meshes? I downloaded 3dbuzz's unreal VTM and they're using lotsa static meshes too.
Gonna print out a copy of your explanation and take it to the office. I'll have fun on my breaks!!!!
thnx Spooger! see ya around
Man! No wonder! Thanx a lot for the explanation. It's pretty logical and I can't wait to try it out. And what about collision. Does it work better this way?
Has the unreal level editing technique changed from added brushes to static meshes? I downloaded 3dbuzz's unreal VTM and they're using lotsa static meshes too.
Gonna print out a copy of your explanation and take it to the office. I'll have fun on my breaks!!!!
thnx Spooger! see ya around
Yes, collision works a LOT better this way, not perfect, but better.
It's ALL static meshes in dis world baby! It's da shizznit! If you are building your levels with anything over 10% - 15% adds... your in the stone age.
You may still run into some issues with the faces/surfaces looking screwy at times, but we can help you get those cleaned up as you go along. That's another tutorial in itself.
Peace!
It's ALL static meshes in dis world baby! It's da shizznit!
If you are building your levels with anything over 10% - 15% adds... your in the stone age.You may still run into some issues with the faces/surfaces looking screwy at times, but we can help you get those cleaned up as you go along. That's another tutorial in itself.
Peace!
man, I feel like an unfrozen caveman!
afecelis hits reality and sees things are easier this way... it seems like his only useful neuron worked this time!!! ah ah aha h a
Great Spooger! lotsa things to try out tomorrow, now I'll hit the sack!
Now I understand why when I opened ut2k3 maps 90% of the stuff was green!!!!
BTW. I'm also gonna check some ut2k3 maps for the sake of learning.
peace! and thnx!
afecelis hits reality and sees things are easier this way... it seems like his only useful neuron worked this time!!! ah ah aha h a
Great Spooger! lotsa things to try out tomorrow, now I'll hit the sack!
Now I understand why when I opened ut2k3 maps 90% of the stuff was green!!!!
BTW. I'm also gonna check some ut2k3 maps for the sake of learning.
peace! and thnx!