Internally the wrappers handle all the coordinate conversion and accounting for resolution, etc. TerrainInfo is an abstract class with a concrete implementation for each map type. TerrainInfo info GetInfoAt(Vector3 position, MapType mapType) // world coordinate So either this thing needs to be vastly improved, or all the features that are currently exclusive to treecreator-trees need to also be available for custom-mesh-trees.Ĭlick to expand.Ya I noticed those last time I looked in the docs and saw they were there.īeing that the overall revamp is probably a major project, one thing I'd love to see is just a better api wrapper for getting and setting values in the different maps.įor example I wrote my own wrapper methods that deal strictly with world coordinates and hides having to figure out what part of a map I need to fetch based on what I'm changing. I've tried the tree creator tons of time, but I can't get a decent tree out of it, because of this I always model them by hand. (without this, trees that lie in the shadow of a mountain look like they give light) Trees need to be able to receive and cast shadows. There are a lot of things I would like changed/added, but the following are most important to me:
I don't really care much about waving in the wind and stuff like that though. I'm mostly interest in a good vegetation&trees system.
What use-cases, features, workflows do you have or would like to see? A proper terrain-system is vital for this. Our scenes are vast in size and almost always outdoors with lots of nature.
#SOURCE ENGINE SDK FLOWMAPS WATER SOFTWARE#
We're working on cycling simulation software which features large outdoor-scenery. What kind of game are you trying to build or would like to build?
#SOURCE ENGINE SDK FLOWMAPS WATER PROFESSIONAL#
I'm a professional 3D and Technical Artist, in the industry for over 5 years. It's maybe a bit late to add my opinion, but I'm gonna do it anyway. Wow, I can't believe I missed this thread.
0 kommentar(er)
