Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mvc

Pages: [1] 2
1
Work in Progress/Tests / Re: MVC's WIPs
« on: 2014-04-09, 11:59:33 »
couldn't resist a cheek little test render.

2
Work in Progress/Tests / Re: MVC's WIPs
« on: 2014-04-04, 18:19:07 »
thanks.

found some time today to do some more leather work.  bit higher res this time too.

3
Work in Progress/Tests / MVC's WIPs
« on: 2014-04-01, 19:25:01 »
First stab.  Quick test.  Materials leaving a lot to be desired still, but getting there.


4
+1 for spherical camera!

5
I'm experiencing similar issues with DR, vut rather than MultiTexture, i'm finding that DR is not reading any textures on DR slave nodes.

Am currently testing to see if this an issue with mapped network drives.
UPDATE - yes, looks like UNC pathing on the assets fixed the dropped textures.

UPDATE 2 - nevermind, i've just found this... http://forum.corona-renderer.com/index.php/topic,3148.0.html , but i notice that the fix was just to UNC everything.  can we have mapped network drive support?



6
[Max] Resolved Bugs / Re: Max 2014 - .NET exception
« on: 2014-03-19, 20:03:22 »
it runs fine. no issues at all.

7
[Max] Resolved Bugs / Re: Max 2014 - .NET exception
« on: 2014-03-19, 19:13:20 »
Initially I was unable to run it, as I had a missing msvcp120.dll, however, installing new C++ Redistributable Packages fixed this (http://www.microsoft.com/en-us/download/details.aspx?id=40784).

On running the little executable, it now works fine, performs the calculations.  However issue running Corona remains.

Same issue with A5.

Max loads fine if I remove or rename Corona2013.dlr

8
[Max] Resolved Bugs / Max 2014 - .NET exception
« on: 2014-03-19, 14:41:17 »
We have installed this on two workstations - one an i7 3770k (http://ark.intel.com/products/65523) which runs A6 Corona with no issues, and another a i7 3930k (http://ark.intel.com/products/63697) which has the issue.  Both systems have all the latest Windows Updates(i've searched manually too - no more to be found, unless I am missing something?), as well as up-to-date chipset and motherboard drivers, and the latest versions of .NET.

The .NET error that pops up in the Windows Error log when trying to directly load the plugin into Max is listed below -

Code: [Select]
Application: 3dsmax.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Runtime.InteropServices.SEHException Stack: at <Module>.TranslateAndDispatchJaguarMessage(tagMSG*) at <Module>.TranslateAndDispatchJaguarMessage(tagMSG*) at <Module>.AppUI.TranslateAndDispatchMessage(AppUI*, tagMSG*) at <Module>.MessageChecker.GetImportance(MessageChecker*, tagMSG*) at <Module>.MessageChecker.GetImportance(MessageChecker*, tagMSG*) at <Module>.AppUI.RunNonBlockingMessageLoop(AppUI*) at <Module>.AppUI.RunMessageLoop(AppUI*) at <Module>.wWinMainCRTStartup() at <Module>.wWinMainCRTStartup()

9
As it has been already said. This problem is due to the missing windows update. So you either have that update hidden, for some reason, or you use some modified version of Windows.

Both judrake and I have previously said that we have installed every Windows Update available at the problem is still occurring.

10
Any other idea what this might be?  A clash with another plugin?  VRay? ForestPack?

11
Same here - everything up to date. All drivers and Windows Updates.

12
Jono! Alright mate. How's HD going? Experimenting with Corona?

Matt

13
Fresh install of Alpha 6 into Max 2014 (not Design - if that helps).  As soon as Max tries to load Corona2013.dlr it bombs out and throws up the Max crash page.  Deleting Corona2013.dlr allows Max to load, but obviously with no renderer.

Any thoughts?

14
[Max] Resolved Bugs / Re: 5a instantly crash max on st art
« on: 2013-11-29, 10:36:10 »
i take it back. same issue. cant find a fix.

15
[Max] Resolved Bugs / Re: 5a instantly crash max on st art
« on: 2013-11-27, 17:50:08 »
managed to solve the issue by installing alpha v4, then reinstalling v5, deleting all the installed files, then reinstalling v5 again!

Pages: [1] 2