Thomo

Sure, send me the link, it shouldn't be a problem. I'll do it now. Cheers Ah sorry email address. DELETED

I think there is a problem sometimes when it is setup with VRay materials as this model is. Export settings need to change, particularly with .3DS.

It's only in .max format. That is the problem, I think, they are saying that they cannot convert from .max to .3ds as the file gets too big. We have the Okino plugin for Max and it will export a .fac directly from a .max file!

We also have the Okino Polytrans conversion from 3D Max, if it can't do it I'd say there is a problem!

We have 3D Max here, I can try to convert it if you like. I'm in the office now so send it through or upload to dropbox or something.

Hi to Everyone. This problem with PC Rama has been around for too long. I understand that Tomas and the team are now ready to solve this issue. Thanks Tomas. Please describe your concerns and errors until we find the bug! Please!

This is driving me crazy. If I copy and paste a texture in the material window, it does not paste in the same place! This does not always happen. I remember this was a bug years ago, except it happened all the time. Check this project. https://www.dropbox.com/sh/swy7kzpjkul280p/AABx3ijL7u5oi4hxWFHm1f0_a?dl=0 - go to material window for "roller doors" - in diffuse select the "Roller NEW MID GREY.img texture - copy - paste into diffuse or bump channel. - texture is in a different position. EIAS V 9.1 on Win 7 64 bit. Any ideas? Thanks.

Hi, This question may have a simple answer that I'm overlooking but here goes... I have several lights in EIAS. So when rendering in Camera and I am using photons, it tells me it is "baking database" for light # of # (eg: 3 of 6) Does light # relate directly to the Project Window order, ie: the 3rd light from the top in the Project Window list? And then what if I move it in the list? Does it stay as 3 of 6 or change it's number. Or does it remain as the order you "install" the lights? It seems maybe this is the case but having moved lights up and down the project list it has become difficult to know which is which. Naming makes no difference, Camera merely gives a light number (#). The reason I ask is because it is hard to determine with several lights which one is slowing down the render or causing a particular problem. Any ideas please? Or maybe this could be addressed in Camera by actually "naming" the light in accordance with the project window naming convention that is already established. IE: In the camera window instead of "Light 3 of 6". Perhaps "Sunlight 01 of 6 lights". Sunlight being the name of the light that is being rendered at that time by Camera and corresponds to the actual light name in the project window. Any ideas or feedback would be greatly appreciated. Thanks

Ok but I still don't see how any of these "work arounds" give a true DOF in relation to focal length. What if I want to focus in the MIDDLE GROUND? So therefore I would have the FOREGROUND blurred, the MIDGROUND in focus and the BACKGROUND blurred. Am I missing something? Z Depth or Fog don't solve this scenario as far as I can see. Please tell me if I am wrong. Does anyone have a clear answer to this question please? Many thanks,

The fact is it does not work. As I have said before. I want my money back! It is USELESS to me. Yes it may have worked in the past. I'm not kidding. Once again there is no response from the producers. They HAVE my money. I do not HAVE a working product as advertised / specified and as should be. Give me my money back. WHEN you have it working in conjunction with WIN EIAS, call me.! I'm more than happy to TEST it for you. Last time I am going to say this. Enough. I don't want to wait until you fix it. Simply because you are not doing so. Give me my refund and THEN I will know you are listening. !!!

Thanks Tomas, please keep up your great work! Best regards

Hi Tomas! 1 year ago this issue was raised and then it was "later" also.That was before you started with your "complex issue(s)". Rama is separate. It doesn't work correctly. It is in fact almost useless as the product it states to be. Sorry but this is true. I have no doubt these are difficult problems to solve. You solved it for Mac. Solve it for PC please. Complex issues aside it must be solved first as part of the package. What I truly cannot fathom is that you have sold an incomplete product and have no qualms. On top of that you continue to do so. Truly, tell me when you are going to fix it.

Hi Diego, I am aware what has to be provided in order for a bug to be resolved. Meester Smith has the same problem. In my previous post I quoted him from a private email conversation we had. I have explained the problem directly to EIAS before this thread in another thread. The problem is reproduced by continually sending projects, any projects, via Rama PC to PC. I honestly don't know how it is possible to deliver that information any more clearly. My frustration lies in the point that this issue does not even prompt a response form EIAS as to whether it is being addressed or not. I can only assume the lack of response indicates it is not. Thanks

Ok well that nearly worked, using textures and clip but Placer wont render textures properly. Everything is set correctly but it just renders as though the texture is flat mapped from a top view. Have you done this Reuben, if so any advice please? Thanks https://www.dropbox.com/sh/z4nqu1m4hqs6d1f/AABkEPEo8zi9t4Fl_v33Fzxoa?dl=0

Hi Reuben, Do you mean the less polys on the stamp surface or the stamp object? I have tried before with diffuse maps and clip maps but camera couldn't handle it when they over lapped, they would just "balck out". I haven't tried that for a while so I might go back and try it again. Thanks for the suggestion.

e

Is anybody taking note here? Rama does not work on PC!!! Is this just going to be left out and totally ignored? Please test it and see for yourself. Can't sell it if it ain't working, surely! Somebody at least respond please. Sincerely.

A couple more explanations of what happens that may help. 1- It seems that Rama Master drops communication with slaves (even running on the same machine) after a period of time sitting idle. Sending a job to Master at this point produces no result and no activity on slaves or master. 2- After several render jobs consecutively Rama master drops communication with the slaves during rendering. This causes the slaves to "hang" on sending the last frame or strip back to the master. Master shows at first that it is sending files then sits displaying as though nothing has been rendered. Closing master and re-opening shows that it has rendered some frames / strips and then stopped. So master renders some of the file but does not display that it has, until it is closed and re-opened. This seems to be the 2 most common problems with PC to PC Rama. It does not happen on Mac to PC or Mac to Mac. PC to Mac I cannot test anymore so I don't know. As said before, a restart of master and slaves and all is back to normal. Until the next time it happens. I hope that helps at least explain the problem.

Yes it works, but when I close or reduce EIAS the desktop goes haywire with drag strips all over when a window is moved. A full machine re-start is the only fix. However it's not such a great problem, I'm sure we won't have to set to Win XP upon the EIAS update.

All I know is that EIAS developers are doing wonders with the program now with 64 bits has much more capacity, speed and quality remains unsurpassed, that's the reason because the Hamburg planetarium development team have chosen EIAS 9.1 for their full dome projects which are rendered in 60 fps and 8k. I agree the EIAS team are doing wonders Diego. Please take my comments in the light they are intended, as constructive criticism.

Hi Well this is interesting as I have never had a rama problem with a PC master and that is even using mac and pc as slaves. I've had 2 previous set ups with Mac masters - one worked after trying a couple of things and one didn't, but thinking about it, I may have forgotten to try out the previous fix as I just jumped straight onto using a pc master again as it was the faster machine. The fix that worked for Mac master to Pc slave - create static ip adresses for the machines, give it a try. This may even fix Pc master problems....let me know how it goes. I am still getting Rama problems. I'm aware of the "re-set" trick but my problem is definitely a bug. Generally Rama works well, the problem I have seems to happen if Rama has been sitting open for a while or after several jobs being sent to it. Basically the Rama master gives no indication that it is doing anything, the slaves "hang" on sending the rendered strip back. If I then close and re-open Master is shows some of the strips have been rendered. A re-start of master and slaves and all is ok. So this is not a huge issue in terms of actually have Rama working, the issue is that I have to be at the computer to restart Rama. I was doing a lot of Amazon rendering having setup a render farm on there. It works really well but Rama has this problem and ends up spending the night in a state of limbo until it is re-set [/indent]

Yes I agree. I don't seem to have many problems once figuring the right export settings. I know for my PC setup that the V8 upgrade also resolved a lot of problems with various "bugs". My system is very new, graphic cards / drivers particularly and FMZ had to address this. Personally I thing FMZ 7&8 are very good.

Yes that is the problem, 32 bit camera. I was hoping that the 64 bit version that was sent to me would have been resolved by now. I understand what is being said but it just is not working for grass in Arch Viz for me. Proxy seems to be better but more tedious to setup, particularly on contoured surfaces. I can't even produce a weight / strength map on a new graphics card. This is hopefully being addressed. Thanks for you input though. Best

Hi Al, No I didn't realise it was you! That was a great coincidence back then that we met in Siem Reap of all places and both using EIAS, great to hear you are still doing so. All is good at my end, I'm based mostly in Thailand now with the Australian business as well. What about you? It is very encouraging you are not having the Rama problems on PC, I'd pretty much put it down to PC. I have tried everything that has been suggested before but I think I will start "problem solving" from what you say. New switch, re-install, fixed IPs and see if I can nail the problem down. I'll keep you posted. Yes I am on Win7 Ultimate, what's your setup? I am also having problems with new GeForce Cards and HDRI maps, another post here as well. Thanks for getting in touch. Best,

Hi, FormZ 8 addresses quite a few problems but not all of them. They have definitely changed .obj export in FMZ V8, I have spoken with them about this. I have found if you try to export from FormZ with textures checked on as a .fac it causes problems. Unchecking this seems to help. Another thing to try is, triangulate on export. If you are modelling as smooth objects in FMZ 7 or 8 you may need to triangulate these within FMZ before export. FMZ treats curves very differently now (7&8), there are a lot of parameters to setup your own segmentation and facetting of arcs etc. I have found FMZ support very helpful on these aspects. Yes the communication between FMZ and EIAS has been at a standstill for ages it seems. I don't know why. From the information I get from FMZ they are willing to co-operate, I dont know what EIAS's standing is on this. The export for .fac files from FMZ is still stated as "ElectricImage V 2.9"! I feel your pain but it seems right now the only thing is to find "work arounds". I just wish I knew what the future holds, ie what is being done / discussed about issues such as these. Good luck. Some past posts here http://www.eias3d.com/forums/topic/6252-rendering-problems/ http://www.eias3d.com/forums/topic/5893-form-z-to-eias-91/?hl=form