bwcc

not sure if there is a way to fix this - if you are having Camera write any kind of temporary file like a environment map or motion blur, the RA Cameras and the local Camera will get errors. It seems like what happens is the RA Camera will write a temp file the the local camera will write over it then the RA camera will try to read the local temp file and get an error. brian

using a MacPro from 2008 here, so thinking just about anything will be an improvement. Still trying to decide between better CPU (6 or 8 core) or better GPU (D500 or D700). I know what the CPU will do - more cores faster rendering. But, on the graphics, knowing that the that GPU rendering is not going to happen anytime soon, the D500 has 3GB memory per GPU and the D700 has 6GB memory per GPU - what would be the difference in EIAS? would it use all 12GB of memory to draw openGL models and textures? would it use the memory from both cards or just one? - is the only difference to EIAS between D500 and D700 the ability hold larger models and textures in memory so they could be manipulated in realtime? I use a lot of really big models - millions of polygons - I like using EI and rendering is fast but setting up scenes with big models is slow... Also, from what I have read the CPU is upgradeable - doesn't make sense to do it now because the cost would be more than what Apple is charging. But, in a couple of years when the price of the 12-core comes down you could upgrade - I think you are stuck with the GPU's, not sure. brian

thanks for the response! - I have the same computer, it's been a while since I have upgraded, this is one I was waiting for. You seem to be leaning toward the 8 cores rather than the D700 card. I guess it's a trade off between rendering speed and drawing speed. Do you think the D700 is just overkill? Only useful in the most complex project with the biggest models? I think the D500 will be such an improvement over what I have maybe I won't wish for the D700. Also, If I am using a plug-in to generate geometry - would the creation and manipulating be accelerated by more cores or more GHz? For example, when Blobmaker is generating the geometry it only uses 1 core. Is this because EI only uses 1 core? Will the plugins need to be multithreaded to use the additional cores while in EIAS? If the plugins were multithreaded would they use multiple cores to generate models even if EI was not multithreaded. thanks! brian

EIAS isn't the only app I use so it's not the only consideration - looking at the options for the new MacPro would would be best for EIAS? Processor: you can get 6 cores (12 virtual cores) that run at 3.5GHz or 12 cores (24 virtual cores) at 2.7 GHz ($3,000 extra). obviously the more cores the better but since they run slower is it worth the extra 3K? Does the difference in speed (3.5 - 2.7 GHz) make that much difference for Camera. Which features in EIAS would benefit from more cores vs more GHz? Graphics: Choose from D500 or D700 - the upgrade is $600. Other than the additional memory (3GB to 6GB per card) does EIAS benefit from the upgrade? The D700 has more and faster processors, would this benefit EIAS or is just the additional memory to load bigger models. Would Bullet Simulations benefit from this upgrade or does it rely on the processor? Memory: 16 - 32 - 64. I know Camera 64 would benefit from more memory, but would all this memory benefit EI? Since EI is still a 32bit is limited to 2GB? What benefit would we see with a 64 bit EIAS that could use all the memory? Which would most benefit the speed of using EIAS - loading, manipulating, deforming big models / textures - real time animation playback in EIAS. Processor, Graphics, Memory, waiting for EIAS 64 bit? all the above? brian

One thing to keep in mind. If you edit the settings for any Camera it applies to all Cameras on your computer. it would be nice to set Camera preferences for each Camera. You could keep the Camera in the EIAS folder set to 4 or 6 threads for snapshots and continue work in other apps. Then send the project to Renderama (overnight) and render with a Slave Camera set to use all treads. bw

I run into this using AfterEffects while trying to render in EIAS - I set the threads to 4 (out of 8) for Camera, and set the treads in AE - actually works great. Neither is as fast while using fewer threads but it does not slow down at all. brian

I wish - Tailor is completely broken... doesn't work at all in 64bit or 32 bit Camera. The project uses Mrs.Bebel and it works in 32bit, but I have to reduce quality the source and the segments in the extrusion (so it will work in 32-bit) to the point where the model looks faceted when rendered in HD. I can increase the quality of the model and it will render in 64bit but it's really slow. Also using NX a lot, only works in 32bit. I know these are NL plugs, but the same thing happens with Placer, Dante, Contortionist. bw

I'm sure there are other things to consider beyond what I need need, but these plug-ins are critical. There is almost nothing I do without a plug-in or shader. I am constantly switching between between 32 & 64 bit Camera. I have project now that will only render in 64 bit, but because I'm am using a 32-bit plug-in with 64 bit Camera it increases the render time by 5x. If I try to use 32 bit Camera it runs out of memory. All in favor of the next version of EIAS. but I think would rather have the working plug-ins and shaders first. EIAS is 9.1 is awesome, but I don't think I am getting everything out of it because the plug-ins and shaders either don't work or are painfully slow. brian

Could the Plug-in, if it is a 32-bit plug-in if might really slow down. I noticed this with Placer Deposit and Mrs Bebel bw

awesome - thanks!

Starting in (I think version 9) when the preview went to hardware only, the preview in the Camera window is really rough with many missing polygons. The previews in the other views (side front, top) are perfect. Is there any way to get the preview in the Camera window to look better? thanks brian

You may have already tried this, I am using a Mac MIni as a slave and I had to install from the installer (not just copying the Slave folder from another computer) - it is running a newer OS - but I couldn't get the Salve to run at all just by copying. Also, remember... If you are using any 32 bit plug-ins it is usually faster to render in 32-bit. for some reason 64-bit Camera slows down with the old plugins. bw

Even if the slave camera can't show the last frame rendered, would be nice if in the text of Camera window it would have the current job. Now it says "File:Renderama_Output.img" no matter what the job or the file it is rendering. bw

would be nice if EIAS would ask if you want to use the older plugin or let you select a newer one when opening a project into a newer version. bw

I guess I could try this, but I'll ask anyway - This was a .prj started in version 8 opened and saved in 9.1, but I could still go back and open the project in version 8. Are all projects, even ones created in 9.1, able to open in 8 or only ones started in 8? If so how how far back does it go? thanks brian

very good to know - thanks for the quick response! brian

I can't collect because I can't get it to open all - can I just send the .prj?

I have a project I have been working on and I opened the file today in EIAS 9.1 and EI continues to crash while opening - I believe the problem is a Blobmaker object that has become corrupted (maybe not really sure) - In the past I have been able to remove the plug-in file from the sockets folder, open the file and choose to remove or skip the socket object. Then I could delete the object, save, quit, reinstall the plug-in and it all worked. to get the file open. I have tried all that, and no matter what I do it continues to crash without opening. I have also tried to merge the prj into another prj. - crashed. is there anything I can do? thanks brian

64 Bit Placer? - how do I get one of those? brian

Steve - yeah that's exactly the same kind of models I get also. I've been using ViaCAD Pro to convert CAD models and have tried to build some models from photos, but it it hard to use and a little buggy. I also use Modo for sub-d. Seems like Rhino will probably be the way to go. You mentioned the model was from SolidWorks. Does Rhino import SolidWorks native files? Do they need to be converted to something first? Do you know if the Mac beta will import SolidWorks? brian

I actually used FormZ about 20 years ago - it was the first modeler I ever used, not counting Ray Dream Designer. It was interesting to see it again, it's different (much better) but some things are exactly the same. I think exporting facetted models was a problem then too. FormZ is a really nice modeler, it is so disappointing that the export is still a problem. I have tried a number of options on angle and maximum segment length on a number of different models. The mesh in wireframe looks really good, very dense small polys. The mesh looks nearly identical to an export from ViaCAD or EI Modeler (which render perfectly) . For some reason the model will always have some part that does not render smooth. I built a partition, installed OS 10.8 and downloaded the beta of Rhino - it's really good... The current build does import igs but not yet stp or sat - I guess the released version will include those. The obj export of the igs file was perfect. It still doesn't feel as easy to use as EI Modeler but it does so much more and does it much better. Really wish I had some idea of when it would be released. brian

thanks for the input! - I have been experimenting with Rhino and I do like it. The beta builds now no longer work in 10.6. So I have to upgrade the OS to continue with the beta. I need a modeler to be able to import a (stp, igs, sat) cleanly be able to make edits to model and export to fact or obj. the last Rhino beta I downloaded didn't have the import implemented yet. I have ViaCAD and it tessellates smooth and exports fact, but ugh... it is hard to use and crashes a lot. I have tried TurboCAD (It's the same app as ViaCAD) I do think Rhino is the best solution - Do you know if they have any import(s) implemented yet? thanks, brian

If it is the same as before - it isn't really a problem other than the inconvenience. Only one world (the original world) will have any effect in the scene. The problem is you can't hide or nest into a folder the bogus world objects. They just sit at the top the project window taking up space. I would give the real world a label to tell which one it is. bw

I remember this was a bug back in version 6 or 6.5 where every time you would merge a project it would add the world(s) from that project - I think I had a project with like 32 worlds - like string theory...

the model I'm trying to export now is an imported .stp (edited a bit in FormZ) then exported to FACT. I am testing FormZ to see how it works with EIAS. Exporting from Modeler isn't really an option, I am looking at FormZ as solution to replace Modeler so I can upgrade my OS. I need something that can import and edit CAD files (STP, IGES etc.) and be able to build some hard surface models. I used FormZ maybe like 18 years ago? - It looks good but I really need easy workflow with EIAS. this is a screen grab of the model in FormZ - fairly simple. http://www.brianwhite.cc/temp/formz.jpg these are renderings from EIAS http://www.brianwhite.cc/temp/Project9_17.jpg http://www.brianwhite.cc/temp/Project9_19.jpg within FormZ, in Export/Options/Facetting Options, you can choose "Use Objects Display Resolution" I was able to set a Custom Faceting Scheme and it seems to export and facet to those settings but it won't completely smooth shade. If I override the display Resolution and set the angle, edge length and "additional facetting" doesn't seem to work at all. Is there a better way to set the tessellation? Could the problem be the original imported STP? I have tried to export as OBJ and 3DS also. thanks so much! any help is appreciated brian