Hi Guys,
Don't know if this is a problem that anyone has run into. I'm trying to load up a scene that was made in LW 11.5 and LWOctane 1.0 to LW 11.6.2 and LWOctane 1.5. I try to render the scene in the newest version and the scene renders black. I'm also missing out on alot of the old plugins that I had been using before I switched to octane. Could that be the cause? Or is it that the scene is simply to old and has to be redone.
Draydin_r
HELP! Loading a 1.0 scene to 1.50: will not render scene
Moderator: juanjgon
In theory you should be able to load a scene from Octane 1.0 with current Octane 1.5 plugin without problems. Perhaps you have something else in the scene that is broken, a parameter with a problem, or a missing plugin.
If you want to send to me the scene I can check it here to see what could be the problem.
-Juanjo
If you want to send to me the scene I can check it here to see what could be the problem.
-Juanjo
Sadly, Client NDA prevents me. It's a house that the builder still has indevelopment. I'll give the plugins a try and go from there. I'll keep you intouch and let you know the results.
Draydin_r
Draydin_r
Intel Core i7 CPU 6850K @ 3.60GHz 128.0 GB Ram / Win 10 64 bit / 1x GeForce RTX 3080
OK ... if you continue with the problems you could send to me only the scene (without the objects and textures) to see how the render target is configured. Also can be useful the log file you get while you render the scene with F9/F10 (you can enable the log in the plugin render options panel).
Do you get any kind of error or only a black rendering?
-Juanjo
Do you get any kind of error or only a black rendering?
-Juanjo
- FrankPooleFloating
- Posts: 1669
- Joined: Thu Nov 29, 2012 3:48 pm
Draydin_r -- If the above does not work or Juanjo can't find solution: lws files are just text files (readable by humans) and can be opened in a text editor. There have been a couple occasions where I could not open old scenes or they caused a crash every time - and I had very specific camera and light setups etc... What I did in all cases was make a clean scene, load all the objects and save it. Then open it and the problematic scene file in text editor (Notepad++ is my weapon of choice) and copy/paste the camera data and the object and light positions/transformations into new scene, saved it, opened in LW and finished setting up the scenes, and was good-to-go. This can certainly save the day, if you are truly in a pinch. It goes faster than it sounds and likely way faster than starting completely from scratch. And although a lot of stuff in scene files might be intimidating to non-programmers (I'm a JS programmer myself), you should be able to make sense of it after a couple minutes and find the stuff you need. Especially if you just need camera and a couple object positions etc.
Good luck bro!
Good luck bro!
Win10Pro || GA-X99-SOC-Champion || i7 5820k w/ H60 || 32GB DDR4 || 3x EVGA RTX 2070 Super Hybrid || EVGA Supernova G2 1300W || Tt Core X9 || LightWave Plug (v4 for old gigs) || Blender E-Cycles
Hey Guys turned out to be much simpler than I thought. It was a couple setting in my thinlens node. the Focal depth to be specific.In one of my previous scenes I must have turned to zero to remove the depth blur from the image I was working on. (the client didn't like the effect) Turns out that just chaning it to auto focus solved the issue. Thanks for the suggestions!
Intel Core i7 CPU 6850K @ 3.60GHz 128.0 GB Ram / Win 10 64 bit / 1x GeForce RTX 3080
- FrankPooleFloating
- Posts: 1669
- Joined: Thu Nov 29, 2012 3:48 pm
Great. This is still a nice trick for future reference, for those who have trouble with previous version scenes.
Win10Pro || GA-X99-SOC-Champion || i7 5820k w/ H60 || 32GB DDR4 || 3x EVGA RTX 2070 Super Hybrid || EVGA Supernova G2 1300W || Tt Core X9 || LightWave Plug (v4 for old gigs) || Blender E-Cycles