 Show Posts
|
|
Pages: [1] 2 3 ... 7
|
|
1
|
infiniMap / General infiniMap Discussion / Re: Bug: Black Blocks in Render
|
on: July 22, 2008, 01:21:47 AM
|
Thanks for the betas! The procedural shader is working great. I imagine you're already aware that the node version crashes lightwave. If not it seems to be for me, let me know if I can be of any assistance in testing the beta further for you.
I'll check it out, thanks. Which one of the two nodes... and which version of LW are you using? Cheers and thanks, Mike |
|
|
|
|
4
|
infiniMap / General infiniMap Discussion / Re: Infini Map and Normal Maps
|
on: June 21, 2008, 03:39:25 PM
|
Thanks for the suggestion with "Object Tangent" works beautifully. I really love infinimap, it should be on every Lightwave user's "must have" list. The new openEXR support is sweet, giant 32-bit floating point images with a small memory footprint!
Thanks a lot *blush* ... can we quote you on that ? Cheers, Mike |
|
|
|
|
5
|
infiniMap / General infiniMap Discussion / Re: Infini Map and Normal Maps
|
on: June 20, 2008, 06:56:40 PM
|
One way to solve it would be if or is there a way with infinimap to make an image loaded by infinimap appear in the image dropdown list so that I could select in in the normalMap nodes image dropdown. Agreed, I wish that was possible. It would have also saved me from coding the 80% of infiniMap that emulate LWs image texturing  Or I've been playing with the infinimap extended node thinking the "colour (Normal)" output might work somehow, but I still seem to be stuck in the fact it needs to pass through the "NormalMap" node which takes no image input.
That output actually interprets the infiniMap image as a bump map and outputs a vector that perturbs the normal according to the bump. You can try the "Object Tangent" node from Denis: http://pagesperso-orange.fr/dpont/plugins/nodes/Additionnal_Nodes_2.html , this works if there is a UV map to project the normal map with. Cheers, Mike P.S. native suport for normal maps is on the to do list... |
|
|
|
|
7
|
exrTrader / exrTrader General Discussion / Re: Network rendering problemL No image output with exrTrader 1.1a and BNR4.03
|
on: April 03, 2008, 10:48:46 AM
|
My problems still continue and I'm somewhat at a loss to explain them. One of the issues is a problem in exrTrader
- SNC4 loops the same frame over and over again because exrTrader defaults to writing out frmXXX files, but LW seems to (for me) output frmXXXX files. The dummy saver and the image filter saver don't agree, so SNC believes the node has crashed and requests the same frame to render. I'm not sure if this is an SDK limitation - Mike?
It is, the number of digits and the frame format needs to be set manually in the exrTrader GUI to match the output settings of LW. exrTrader can only read out the path and base file name, but not the format used by LW to build the final file name. I'm not sure if this is an OS X oddity either.
That could well be. USB should be fine, OSX on intel CPUs handles those just as quickly now as FW drives (if you run Leopard). One thing that might help is getting a cheap SOHO NAS... you can get cases for two 3.5" drives (that allows for a mirror) for around 200€, plunk in two 500GB drives and you're at less that 400€. Not ideal but maybe more reliable (plus they use a lot less energy if they run 24/7). Cheers, Mike |
|
|
|
|
10
|
exrTrader / exrTrader General Discussion / Re: OpenEXR plugin for AfterEffects CS3
|
on: March 27, 2008, 07:21:32 PM
|
Hey Mike
Trying to get this to work with the MAC versions and having problems!
I used the ZIP compression method which works perfectly on the PC, but you get a bunch of stars (*) next to the extra channels on the MAC. I tried a different format, but then I got the stars!
What I'm after is a compression that will work with both - any ideas?
ZPI should work with both... Fnordware use the latest openEXR library as well (and ZIP hase been there for ages). Does uncompressed work? Otherwise you might need to send a sample image for Fnordware to check out. Cheers, Mike |
|
|
|
|
11
|
exrTrader / exrTrader General Discussion / Re: Network rendering problemL No image output with exrTrader 1.1a and BNR4.03
|
on: March 26, 2008, 10:41:42 PM
|
Installed the latest exrTrader with BNR4.03 running LW 9.3. A test scene was run through the pipeline, but no image files are written to the output directory. The LWSN log shows an entry for writing the image file, but it also shows OpenEXRSettings master handler failing.
Hi Mike, I had a look here and it works with 9.3.1 as expected... Now, the question is... can your nodes actually access the plugin? Maybe you could check the plugin config file used by the nodes to see if it contains exrTrader, and check if the nodes can access the plugin as well. Cheers, Mike |
|
|
|
|
14
|
exrTrader / exrTrader General Discussion / Re: Network rendering problemL No image output with exrTrader 1.1a and BNR4.03
|
on: March 26, 2008, 08:53:26 PM
|
Interestingly, I'm seeing nodes completely wedge with the dummy saver applied as well as the image filter. Just after the 'rendering frame' line is shown, all CPUs spin at 100% and then nothing more happens. I've had CPUs churning for a combined total of days of render time before I caught this :/
Which render controller are you using? I'll be having a look at that later on today, and hopefully I can track it down. A problem with the dummy saver is weird, as it doesn't really do anything... Cheers, Mike |
|
|
|
|
15
|
exrTrader / exrTrader General Discussion / Re: Network rendering problemL No image output with exrTrader 1.1a and BNR4.03
|
on: March 25, 2008, 08:58:43 PM
|
|
Hi Mike,
thanks for the detailed log. The master handler shouldn't fail... nonetheless... images ought to be written even if it fails (at it does is provide the settings for the EXR file - if it isn't present, the files are written using the defaults).
The only things that strikes me as being off is that you're writing to a directory that is outside of the content structure, but that should be no problem either, especially when using the normal OpenEXR saver (which doesn't do any file name manipluation at all).
I'll try to reproduce the issue here using a similar path set-up as yours.
Cheers,
Mike
|
|
|
|
|
|
|
*phew* 
