ARender version 1.1

About Truespace Archives

These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.

They are retained here for archive purposes only.

ARender version 1.1 // The Garage

1  |  

Post by Johny // May 31, 2008, 2:57am

Johny
Total Posts: 672
pic
Ever have problem with rendering to very big trueSpace's scene?
Want to render trueSpace scene for up to 16384x16384 pixels? (LightWorks only) ;)
Want to compare several trueSpace render results before continue to final render?

If one or more of above questions answer are yes, You're on the right place! :D

You can download ARender tsx plugin version 1.1 for free on below link.
Please install ARender on your trueSpace ".../tsx/ARender" folder.

Special thanks to Emmanuel Asset for visual help file. If below visual help file is hard to read, you can download the original size of visual help file on this link: http://emmanuel.asset.free.fr/tsxarchive/arender_help.jpg

Post by splinters // May 31, 2008, 5:22am

splinters
Total Posts: 4148
pic
Wow, cheers johny. This will come in very handy indeed...:banana:


:jumpy:

Post by SteveBe // May 31, 2008, 7:22am

SteveBe
Total Posts: 282
pic
Thanks Johny!!! Very nicely done!!!:banana:

Post by nowherebrain // May 31, 2008, 9:11am

nowherebrain
Total Posts: 1062
pic
Agreed, this is fantastic to do stuff for print.

Post by Changa // May 31, 2008, 10:14am

Changa
Total Posts: 187
pic
Thanks Johny! Very useful plagin. It works nice for 6000x6000.But when I tried it with Vray 10000x10000 render n10 split, and 'vray render faild' during first pice and I had to hit Esc button other 99 times to stop the process. My suggestion is to have a way to stop the sequence at once for the emergency cases lime this.

Post by Johny // May 31, 2008, 2:20pm

Johny
Total Posts: 672
pic
Please download ARender version 1.11 on first post for solved this problem. :)

Post by adriani // May 31, 2008, 3:48pm

adriani
Total Posts: 89
Hi Johny!!!

Thank you so much for another good work :) again

I have one big problem....since others versions I cannot use the 4x

antialising :( only Ad....

In some cases the 4xis very important because show more detail....

How can I fixed it? is 4X is still a bug of vray ?!?? and still Ts people

do not fixed?!

Thank gain

Flavio Adriani

Post by Johny // May 31, 2008, 8:39pm

Johny
Total Posts: 672
pic
Adriani, I think that your "VRay rendering error" msg cause by VRay failed to allocate some memory for rendering. The 4x antialising require more memory than 3x, and 3x need more memory than 2x, 2x need more memory than ad, etc... So I think its not VRay bug, but sytem can not give enough memory that want to allocate by VRay.

And also I want to reminder you that ARender was build using trueSpace 6.6 plugin SDK, so its only use tsx function that create for use with LightWorks. So I only can guarantee that maximum 16384x16384 pixel only can reach if you render using LightWorks. I think for VRay rendering we must need newer trueSpace 7.51 plugin SDK. :D
Adriani, on my tested with ARender and "ducati1" scene (find on tS scenes library),with Bridge OFF and antialising set to AD, VRay only can render up to 8000x8000 pixel. VRay rendered failed on same resolution if Bridge ON. With Bridge ON, VRay only can render up to 6000x6000 pixel. (Result may variable depent on available memory). On your attached image, I see that you try to render 3000x3000 pixel with antialising set to 4x. I'm affraid it not possible with ARender. My advise is turn Bridge OFF, clean model view scene, go to workspace view and use workspace's VRay rendering tool. :)
Other advise if you still want using ARender is try to render to 8000x8000 pixels (with bridge off, empty model view, and scene that you want to render loaded on workspace view). Then use you image editor to resize render result to 3000x3000 pixel. Remember maximum resolution that can render by VRay is depent on available memory.

ARender splits file render also no advise to use with VRay GI/HDRI. Because VRay will calcuate GI/HDRI map for each split and you'll get very splits noise rendering result.

PS: If you render to very large size, please save only to TGA or BMP file format for avoid out of memory msg error while ARender try to merging split file.

Post by Emmanuel // May 31, 2008, 10:38pm

Emmanuel
Total Posts: 439
pic
Adriani,

If you compute a 1000*1000 pixels render with antialiasing set to 4x, trueSpace will "render" a 4000*4000 picture, and downsample it to 1000*1000, with more details as a result.
Therefore, if you plan to render in 4x mode, you must also increase by 4x the number of splits in Arender.

ARender's power is to allow fine control over the size of what trueSpace has to render.
Depending on your computer performances and the level of detail in your scene, you can find that let's say 100*100 pixels is the maximum V-Ray for trueSpace is capable of. If so, just increase the number of splits to get that 100*100 resolution for each split.
Example : you want a 6000*6000 res picture, in Adaptive Antialiasing mode. Open ARender, set 6000*6000 as resolution and set 60 splits (n). This will make trueSpace to compute 60 renders of 100*100 pixels each, that will get merged at the end.
Does it make sense ?

Post by nowherebrain // Jun 1, 2008, 6:09am

nowherebrain
Total Posts: 1062
pic
Yes I did know(lol), but this is very useful knowledge for others. I highly recommend paying attention to this. Thanks for the wisdom Emmanuel.

Post by chamaeleon // Jun 1, 2008, 7:57am

chamaeleon
Total Posts: 74
Example : you want a 6000*6000 res picture, in Adaptive Antialiasing mode. Open ARender, set 6000*6000 as resolution and set 60 splits (n). This will make trueSpace to compute 60 renders of 100*100 pixels each, that will get merged at the end.

60 renders of 100x100 would only compute 1/60 of the desired image. 3600 renders would cover the whole thing... Sorry for the nitpick. :)

Post by adriani // Jun 1, 2008, 11:08am

adriani
Total Posts: 89
OK Johny and Emmanuel,

First of all thank you!!!


I will try again....but in workspace is not so good for complex and big scenes, so always use only modelspace.

In workspace the problem is very very very slow...is good for simple scenes no complex scenes like building details etc...

Another problem in workspace, I said it to Paul, the problem/sometimes the tga 32bits not working....and png too. You never know when it happens...

Sorry I have a bad english :)

I know about many bugs, but since last year NOBODY speaks about that only wait wait.

thanks again
Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.
Awportals.com   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn