|
Go
![]() |
New
![]() |
Find
![]() |
Notify
![]() |
Tools
![]() |
Reply
![]() |
|
|
Member |
I wish,...
Enlivens Scene camera, or at least the Directors cam, would default to the camera position of the camera that the imported scene was developed with. Imported scene lighting would be nice, too. Scene assets could be saved to the library, as seperate objects. Scene .mtx and .html files could be imported at the same time and work without over-riding the imported ones and creating default buttons instead. Animations imported into Enliven could be saved into an animation library. (currently, mixing/combining animations in the .mtx is a lot of fun, really. Enough wishing for tonight! lauramb |
||
|
|
Member |
Hello,
I added these to our enhancement list. Keep 'em coming! Regards |
|||
|
|
Member |
Had a 'Close' option in the 'File' menu. Exiting and restarting, the program dampens inspirational enthusiasm.
|
|||
|
|
Member |
Hey Laura! Great thread starter!
Hey everyone else...what do you wish for from Enliven Pro? Let's build this list... Give us your comments, your wishes. DavidR Rich3D |
|||
|
|
Member |
Hi guys,
As you can see, I moved this thread to a new forum topic: Enliven Wish List. I created a shortcut to this thread in the Enliven forum where it used to reside. Enjoy! Regards |
|||
|
|
Viewpoint Sr. Expert Member |
The Camera in most cases will use the camera setting from the animation package, if you are not seeing this then it sounds like you have a bug. What modeling package are you using? Also we typically support light maps what type of lighting are you referring to?
Unfortunately the ability to pull individual assets from a scene for saving into the library will be unlikely but importing them individually should give you the results you need. <<Scene .mtx and .html files could be imported at the same time and work without over-riding the imported ones and creating default buttons instead>> I’m not sure I understand, imported MTX’s should not get overwritten although they may be altered when published do too many factors. HTML pages are never imported but you can build your own templates for previewing and publishing. By "default buttons" are you referring to the ones created on the HTML page when publishing? If so that’s just a function of the template you can just use or create a template that does not create the buttons. Importing animation files has been looked at and I believe is under consideration. ~B |
|||
|
|
Member |
Imported .mtx camera settings: <MTSCamera OrbitDist="1" > <Rotate x="9.00391" y="-87.00349" z="0" /> <Translate x="9.70871" y="2.96682" z="22.14364" /> <Scale x="1" y="1" z="1.016" /> <ViewLocation x="0" y="0" z="4" /> </MTSCamera> Upon loading into Enliven, By selecting the 'Runtime Camera' in the Hierarchy Viewer/Objects panel. The Object Attributes displays: Pivot, 3DRotate, and 3D Translate all coordinates = 0.00. 3D Scale all coordinates = 1.00. Orbit Distance = 4.0
All of my work so far as been created in Poser 4 and 5, with some in trueSpace 6.6 wih Conversion Pack 2.1. I'll be working with Carrera 5 and Shade 7 when I'm able to upgrade my systems.
Recently, I've been experimenting with HDRI and IBL/AO lighting. Lighting formats that have been shown to greatly provide a more realistic appearance of cg environments and people. The results so far have been comparable to Lens Flare, which set aside some time ago.
I should split this one up to make it clearer. Scene.html: In the Publish Room one can, 'Load Existing URL, Load Local'. If one has pre-created a template with .html buttons to control the scene interaction , the way that I interpret/presume the 'Load Existing', to work, is that the paths that are preset in the template will automatically work with the .xml file. Ex: Poser 4 and 5 exports 2 or 3 MTSTimeElems in the Scene.mtx: 1.'Poser Transform Group', the default scene control if no Animation Sets are created. 2.'Poser Animation Sets Group', controlled/split animations. 3.'Poser Deform Group', Still a mystery but usually controls loading, and an ON/OFF switch for the entire scene. These buttons are automatically generated/default buttons, added to the Scene.html by Poser when exporting a VET scene. If one , Preloads the exported Scene.html, currently, Enliven adds 3 new ones that work, over-riding the imported ones. What my wish is, is that if one has already created a scene that works, that all of the companion documents could be imported at the same time to add more advanced elements, e.g. Sounds, Behaviors, Superview, etc. (No Sir, Enliven does not over-ride the existing Scene.xml. I never really expected Enliven to read the imported Scene.html. Enliven is supposed to be the environment we use to create the wonderful interactivity that Viewpoint has available. This is part of my experimentation, to discover what Enliven does already.)
|
|||
|
|
Member |
Here is my list
-I wish enliven would not crash so much on 64 bit OS -I wish the material editor for Enliven was more complete, with Ambient.Difuse/Reflection colors and complete and seperate control for each type of maps, difuse, bump, reflection, and so on, with ability to rotate and tile and flip the maps -I wish the interface was more like standard windows software, with regular floating windows, and the ability to open recent files from open menu -Better animation and key frame controll, like other 3D software. If these improvements take time and effort, I dont mind paying more for a realy good software, Enliven is a lot cheaper than other software Thats it for now, I am sure I will come up with many more Norman |
|||
|
|
Member |
I would say... besides the bugs
Make the interface more geared to potential large scale projects. Please fix the scale transform model so that things are easier to group together and not be on different transformation scales. I ran into this one recently and still have not found a work around. Allow Enliven to open up multiple copies or multiple projects at same time like Flash, Maya, any other industry standard program. Its very frustrating to toggle between 2 projects to take a look at settings in the IDE. Offer a viewer for displaying settigns such as poly counts, animation settings, scene settings, etc; like the viewport in Maya. Please.. Please make the VET script window more of an editor and larger for coding in VET script. debugging? more thourough and up to date documentation for the IDE and VETscript. It feels like all the docs are either incomplete or scattered everywhere. (you ought to see my favorites folder for Enliven in my IE browser) and I would say just as important if not the most important, please update Enliven too utilize flash much more recent than Flash 5. Half of the methods and objects in flash 5 are considered no longer used. (Need full movieclip support)(v2 components would be awsome) having help examples and or code snipets accessable directly in Enliven would be great as well. (look at Anark Studio's set-up) more to come later |
|||
|
|
Member |
I'd like to see enliven allow larger light maps, better smoothing options for light maps and even an option to use a flash as a light map. Better light maps would help me alot with creating reflections.
|
|||
|
|
Member |
My Wish is..
free keyboard controled camera with simple collision detection and gravity parameter. To make great Architectural Walk thru's. Like Turntool can. Thanks |
|||
|
|
Member |
My wish list.
1. An option to group single material together. Right now, enliven would break one type of material assigned to multiple objects (ie. bodyShader1, bodyShader2... ad infinitum). I would have to crack open notepad and assign a shader manually on each object just to be able to change everything with a single keyframed animation, which, i strongly feel, should be the modelling program job, and not mine. 2. BETTER DOCUMENTATION!!!!!!!! I want explicit explanation of what each tag means and do, and a good example of how to use them, no hidden gotchas. 3. Better interpreter engine. I want everything works as promised, either through manual coding or generated by enliven, not something that will broke on the next engine release, not "i have to use a noop before, or after, or find a workaround, or scratch my head all night long, or fix what enliven did wrong to make it compatible with the "pro" way of writing XML to make it work" approach. Enliven is a tool to make my life easier, not harder. 4. Better code and workflow example It has been 2 years since I used viewpoint, and not lightly, I might add, but up till now, i haven't found a single complete tutorial/example/explanation on how to make a flash based pre-loader. 5. Faster development time schedule Come on people, flash is an open source language, you can practically hack it apart using the internet as a research tool, and you all have been light years away from the current implementation (what, 4 versions behind? and limited implementation too...) 6. Embedded FLV support. Easier video conversion, better compression. Nuff said. |
|||
|
|
Member |
Would it be possible to get Enliven to work with e-frontiers' Motion Artist flash files?
|
|||
|
|
Member |
Modern Flash support (at least up to 8).
|
|||
|
|
Member |
I created a texture animation in Motion Artist today! Saved it as an .swf file. It imported to Enliven smooth as silk Wishes do come true sometimes, even if I have to do them on my own. Warning: Be careful for what you wish! |
|||
|
| Powered by Eve Community |
| Please Wait. Your request is being processed... |
|

