Opening old 1.9 scenes

3D Studio Max Plugin (Export Script Plugins developed by [gk] and KilaD; Integrated Plugin developed by Karba)
Forum rules
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
voltaire585
Licensed Customer
Posts: 91
Joined: Sun Jun 08, 2014 7:37 am

First, why cant i post in the releases forum? How can we comment on a particular release????

So i tried the demo 4.18 version and opened a 1.9 scene, but just got grey materials. I thought this version was meant to open old materials.
:|
voltaire585
Licensed Customer
Posts: 91
Joined: Sun Jun 08, 2014 7:37 am

Sorry, i was mistaken. I have opened some more scenes and it seems that the problem is fixed. Bravo!! You are the man neonZorglub :D

Should we save each scene after open?
User avatar
paride4331
Octane Guru
Posts: 3821
Joined: Fri Sep 18, 2015 7:19 am

Hi Voltaire585,
2.23.2 - 1.9 was the last version using old material code.
All scenes from versions later than that should be loaded without problem.
4.19 version soon will fix Octane 1.9 scene issue.
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
voltaire585
Licensed Customer
Posts: 91
Joined: Sun Jun 08, 2014 7:37 am

Ok so i have done quite a few tests now. I am having crashes on our more complex files.

Max completely crashes after trying to load to Octane for a long time. After it crashes i have to force log off my computer because something is still caught in RAM. When i force shutdown it says "task host window" is the last thing to close.

Max 2015
Octane 3.0 4.18 demo
windows 7
User avatar
paride4331
Octane Guru
Posts: 3821
Joined: Fri Sep 18, 2015 7:19 am

Are your tests with scenes 1.9 or later?
How many Mb are your scenes?
How much RAM does your PC?
it would be useful to know this information.
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
voltaire585
Licensed Customer
Posts: 91
Joined: Sun Jun 08, 2014 7:37 am

Ok, so it looks like the problem is that the Octane moveable proxy got switched off when opened in v3 4.18, and this was causing polycount to go to the billions. Maybe i missed that fact in the release notes. Ill let you know if I have any more problems.
User avatar
paride4331
Octane Guru
Posts: 3821
Joined: Fri Sep 18, 2015 7:19 am

Hi voltaire585,
I encountered this problem too.
I sent the issue to developers Octane 3ds max plugin.
Thanks for your contribution.
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
voltaire585
Licensed Customer
Posts: 91
Joined: Sun Jun 08, 2014 7:37 am

Thanks paride4331 it would be good to get the movable proxy thing fixed.

Now i tested on another scene in which i merged from xrefs scenes. It came through with almost all materials missing, maybe because i merged from Xref??
voltaire585
Licensed Customer
Posts: 91
Joined: Sun Jun 08, 2014 7:37 am

Thanks paride4331 it would be good to get the movable proxy thing fixed.

Now i tested on another scene in which i merged from xrefs scenes. It came through with almost all materials missing, maybe because i merged from Xref??

Image attached
Old scene.jpg
User avatar
oguzbir
Licensed Customer
Posts: 715
Joined: Fri Jun 25, 2010 12:30 am
Contact:

voltaire585 wrote:Thanks paride4331 it would be good to get the movable proxy thing fixed.
Now i tested on another scene in which i merged from xrefs scenes. It came through with almost all materials missing, maybe because i merged from Xref??
Image attached
Old scene.jpg
Should be because of the xrefs. it's problematic as far as I know.

Could you test this or similar scene with xrefs merged as objects to scene and renders fine on 1.9. and test the conversion again.

So far few tests I did..
and my scenes that are smaller scale (like single object and so on )got converted ok. didnt do a through test...

I wonder what you'll see with this scene conversion without the xrefs?
My Portfolio
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
Post Reply

Return to “Autodesk 3Ds Max”