Author Topic: Corona 5 not working with 3dsmax 2016  (Read 11045 times)

2019-11-08, 14:45:07

Jak

  • Active Users
  • **
  • Posts: 63
    • View Profile
I just installed the newest build, and I am getting errors on 3dsmax 2016 load regarding corona, and do not have Corona available in my render selection roll down. Is there anyone on Max 2016 that has newest Corona build working for them?

I know there is a disclaimer before installing (that you dont have 3dsmax 2016 to test Corona on). This is a crucial moment in time for me, as I have access only to 3dsmax 2016 and earlier, I will have to make some important decisions depending on how this unravels.
« Last Edit: 2019-11-08, 14:51:26 by Jak »

2019-11-08, 15:17:03
Reply #1

pokoy

  • Active Users
  • **
  • Posts: 1983
    • View Profile
I *think* the following is valid, but best wait for someone from the support to confirm: as of v5 plugins are installed in the Programs folder and not in the max root anymore. It's probably safe to remove these as these are the old files. Best backup them and move back if it fails.


2019-11-08, 15:20:03
Reply #2

Jak

  • Active Users
  • **
  • Posts: 63
    • View Profile
Update:

I uninstalled Corona entirely (previously I have updated from 4.x to 5.0), restarted computer and reinstalled from scratch.

I am still having the same errors, cannot initialise Corona (I am a monthly paying customer).

Is there any more information that the Corona team could share on this situation? Is there anyway to try and get Corona working for 3dsmax 2016, or is version 5.0 the version where support is officially dropped for versions 2016 and earlier?

Thanks for your input.

2019-11-08, 15:22:25
Reply #3

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 6107
    • View Profile
The versions it works with are on the download page, and that starts with 2013 :)
Tom Grimes | chaos-corona.com
Product Manager | contact us

2019-11-08, 15:23:54
Reply #4

Jak

  • Active Users
  • **
  • Posts: 63
    • View Profile
I *think* the following is valid, but best wait for someone from the support to confirm: as of v5 plugins are installed in the Programs folder and not in the max root anymore. It's probably safe to remove these as these are the old files. Best backup them and move back if it fails.

Thanks for input, however I dont quite follow what to do in this situation? Clearly the Corona plugin is not being loaded from withing 3dsmax root directory? Or am I understanding correctly that you are trying to say that Corona installer did not install Corona to the appropriate location?

2019-11-08, 15:25:18
Reply #5

Jak

  • Active Users
  • **
  • Posts: 63
    • View Profile
The versions it works with are on the download page, and that starts with 2013 :)

Hi Tom, I understand it stated that it works with version 2013. However I have 3dsmax 2016 (original naturally), I have installed corona using autoinstaller from Corona official website, and I am having problems running corona as per attachment in the first post.
Is there something I am missing, or that I could do to make Corona 5.0 actually work? Thanks for your time.

2019-11-08, 15:34:19
Reply #6

Frood

  • Active Users
  • **
  • Posts: 2002
    • View Profile
    • Rakete GmbH
I know only two things causing this:

A) if you use Windows 7, it needs to be updated
B) Old Corona DLLs in max root (should be handled by the installer though)

For A see

https://forum.corona-renderer.com/index.php?topic=25036.msg157683#msg157683

For B see

https://forum.corona-renderer.com/index.php?topic=25036.msg157270#msg157270


Maybe....


Good Luck



Never underestimate the power of a well placed level one spell.

2019-11-08, 15:46:59
Reply #7

Jak

  • Active Users
  • **
  • Posts: 63
    • View Profile
I know only two things causing this:

A) if you use Windows 7, it needs to be updated
B) Old Corona DLLs in max root (should be handled by the installer though)

For A see

https://forum.corona-renderer.com/index.php?topic=25036.msg157683#msg157683

For B see

https://forum.corona-renderer.com/index.php?topic=25036.msg157270#msg157270


Maybe....


Good Luck

Wow... Thanks for your help and reply.

For A:  I only have Windows 7 updated only as much as I needed, however the previous versions of Corona did work without a problem. Ill try to look into this.

For B: (guess this is what @pokoy was referring to in his earlier post) I searched 3dsmax root directiory, and did not seem to find any .dll's that have been mentioned and have to do with Corona renderer. However, during the update I ran from Corona 4.x to Corona 5.0, I initially had an error pop up in the Corona installer, something about corrupt Corona files. In the end it uninstalled everything it seemed, and reinstalled version 5.0. However I had problems with Corona initialisation; I then uninstalled Corona from Control Panel, then reinstalled Corona 5.0 fresh after reboot, with no luck however.


Thanks for your time everyone, seems I have some digging to do with this one.

Would be great if anyone on 3dsmax 2016 that is running Corona 5.0 sucessfuly could chime in.

2019-11-08, 15:54:53
Reply #8

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 9258
  • Let's move this topic, shall we?
    • View Profile
    • My Models
Would be great if anyone on 3dsmax 2016 that is running Corona 5.0 sucessfuly could chime in.

I'm on max 2016 and have no problem with Corona 5, but i'm also on windows 10, so it could be that's what makes the difference.
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2019-11-08, 15:57:22
Reply #9

Frood

  • Active Users
  • **
  • Posts: 2002
    • View Profile
    • Rakete GmbH
Would be great if anyone on 3dsmax 2016 that is running Corona 5.0 sucessfuly could chime in.

Ok then: chiming in :)


But no Win7 here. I bet it's issue A. Others have already been successful by following the solution provided by bluebox so maybe give it a try?


Good Luck


Never underestimate the power of a well placed level one spell.

2019-11-08, 16:18:01
Reply #10

Jak

  • Active Users
  • **
  • Posts: 63
    • View Profile
Would be great if anyone on 3dsmax 2016 that is running Corona 5.0 sucessfuly could chime in.

I'm on max 2016 and have no problem with Corona 5, but i'm also on windows 10, so it could be that's what makes the difference.

Would be great if anyone on 3dsmax 2016 that is running Corona 5.0 sucessfuly could chime in.

Ok then: chiming in :)


But no Win7 here. I bet it's issue A. Others have already been successful by following the solution provided by bluebox so maybe give it a try?


Good Luck

Great, thanks so very much for the input. I am not giving up yet (neither on 3dsmax nor Corona - Blender is on the very back of my mind, its interface is ghastly... still waiting for 3dmax yearly indie licence subscription implementation; if that would be a go I see no reason to switch from 3dsmax at all, or Corona for that matter).

At least now I know that its not a problem with 3dsmax 2016 directly, there is something amiss with my system.

Also refreshing to see fellow Corona users working on 3dsmax 2016 (at least untill Match 2020, and then some).

Once again thanks for the input everyone, very much appreciated. Will keep updated, if only for folks that might run into similar problems.


2019-11-09, 10:50:13
Reply #11

Jak

  • Active Users
  • **
  • Posts: 63
    • View Profile
A little update as promised.

After looking for the files specifically provided by bluebox (https://forum.corona-renderer.com/index.php?topic=25036.msg157683#msg157683) by KB, I decided to install all 100 updates that were pending for Win 7.

It seems that has solved the issue, I would like to thank once again to everone who helped me in this matter. Thank you for your time.

All the best.

2019-11-09, 15:08:02
Reply #12

Avium

  • Active Users
  • **
  • Posts: 6
    • View Profile
Hello. I have the same problem. Did you solve it?

2019-11-09, 16:21:00
Reply #13

Jak

  • Active Users
  • **
  • Posts: 63
    • View Profile
Hello. I have the same problem. Did you solve it?

Hello, yes I did manage to solve it. The problem was Windows 7 which had not been updated for some time. If you have a similar problem, try and update Windows 7 (from Windows Live update center).