Something like Ctrl>Break or Alt>Esc would be better.ġ3. I multitask several other apps while rendering and have hit Esc by mistake while LumenRT is in focus. too easy to inadvertently abort an animation export. Cars - 200m path is too long and they drive too fast in my models (urban areas). I'm also not sure the LD trees are consistently low definition relative to their HD counterparts (see my next point)ġ1. Trees are of an inconsistent quality - some good, some bad. The uncompressed version of the same image works fine.ĩ. A large LZW compressed tif mapped on terrain mesh doesn't export properly. I've only found a text document of all LumenRT content.Ĩ. A rendered reference 'poster' of each tree/ car/ character would be a useful alternative. the only representation of what cell is being placed is ustn's four window display which shows really poor quality wireframe or smooth thumbnails. Placing LumenRT content using Microstation's cell library. A downside of this is that animation paths would change each time the export is done, so perhaps there's a way of saving the smoothing factor with each export?ħ. Smoothing of animation paths should be possible to adjust while the live cube is loaded. Blur effect works in live view, but is not rendered in the movie.ĥ. File>Save As paths a new script but it's easy to forget which script one is working on.Ĥ. In addition to the name of the exported model at the top of LumentRT, we need the name of the current. It's really important that reference files are honored in the export process, in the same way that they temporarily become part of the design file during a Luxology render.ģ. they need to be placed in the parent file to work). Trees, cars, and lights, etc are not translated (ie.

Microstation - reference files need their LumenRT content to be processed in the export.

They obscure the view while making adjustments, so it would be useful to drag them away from the working view, or onto a second monitor.Ģ. Dialog panels need to undock from their current position at the toolbar. I'm a Microstation user, so some of these might not be relevant to other CAD systems users.ġ. I have a few random comments, some gripes and some requests for development. I have also just finished work on a big project and have had great results with LumenRT. I thought it might be useful posting here too - some of these issues might be addressed by Microstation users/ developers, and I'd be interested to hear of experiences by other users. For those of you using LumenRT, I recently posted some comments on their forum after having just finished a large project.

Lumenrt 2d cad