faerie & fantasy: 50 vue 6 terrains
 |
 |
 |
 |
 |
 |
 |
 |
fantasy & faerie type terrains, a lot of things here for moss & mushrooms. many
of these are flower-like designs. boulders, steps, thrones & paths for interesting
angles.
saved at a managable resolution of 512 (increasing to 1024 more than triples the
file size). a little trick you can use to get more detail is increasing the size to 1024
in the terrain editor.
of these are flower-like designs. boulders, steps, thrones & paths for interesting
angles.
saved at a managable resolution of 512 (increasing to 1024 more than triples the
file size). a little trick you can use to get more detail is increasing the size to 1024
in the terrain editor.
50 procedural & standard terrains,
created in vue 6 infinite.
the entire package is available at renderosity.
click on the thumbnails for larger images.
created in vue 6 infinite.
the entire package is available at renderosity.
click on the thumbnails for larger images.
some larger individual previews: click here.
****special note for vue 6 esprit owners:
most--if not all--the procedural terrains in my packs should load just fine in esprit.
my procedural terrains are usually created first as standard terrains, then
converted. vue esprit will load these & resize them with no problem. however, a
terrain which BEGINS as an vue infinite procedural terrain may require a
workaround in esprit. altho it will load just fine, it may sometimes flatten & squash
in the scene if resized. it will be okay if left unresized.
here is the workaround for resizing: load the terrain, do not resize it immediately.
go into the terrain editor. convert it from a procedural to a standard terrain. resize
the terrain in the scene. then go back into the terrain editor & change it back to a
procedural.
another workaround that SOMETIMES works is to load the terrain, copy-paste it,
then resize the copy. this is however not a reliable workaround.
there should be few--if any--terrains in this pack that should present a problem
for esprit. i don't usually start a terrain as a procedural auto-generated terrain. i
don't like the high camera-blocking edges this produces, & i prefer having
creative control :) so my procedural terrains tend to be converted from standard.
however there MIGHT be isolated incidences where i began a terrain in
procedural mode. again, these should be usable by esprit owners if you use the
workaround, or they're not resized. i will mention that terrains begun as
procedural, then converted to standard, then back to procedural do NOT seem to
require the workaround.
happy rendering!
most--if not all--the procedural terrains in my packs should load just fine in esprit.
my procedural terrains are usually created first as standard terrains, then
converted. vue esprit will load these & resize them with no problem. however, a
terrain which BEGINS as an vue infinite procedural terrain may require a
workaround in esprit. altho it will load just fine, it may sometimes flatten & squash
in the scene if resized. it will be okay if left unresized.
here is the workaround for resizing: load the terrain, do not resize it immediately.
go into the terrain editor. convert it from a procedural to a standard terrain. resize
the terrain in the scene. then go back into the terrain editor & change it back to a
procedural.
another workaround that SOMETIMES works is to load the terrain, copy-paste it,
then resize the copy. this is however not a reliable workaround.
there should be few--if any--terrains in this pack that should present a problem
for esprit. i don't usually start a terrain as a procedural auto-generated terrain. i
don't like the high camera-blocking edges this produces, & i prefer having
creative control :) so my procedural terrains tend to be converted from standard.
however there MIGHT be isolated incidences where i began a terrain in
procedural mode. again, these should be usable by esprit owners if you use the
workaround, or they're not resized. i will mention that terrains begun as
procedural, then converted to standard, then back to procedural do NOT seem to
require the workaround.
happy rendering!