Flamingo nXt

easy rendering for Rhino in Windows

Hello,

 

After this last update I´we been getting this error many times. Sometimes i can save the image if I resume rendering and then stop it again and save, sometimes not..

Had this same broblem in some version of nxt about a year ago.

 

Any Idea what´s the broblem now?

 

Thanks,

Janne

Views: 728

Reply to This

Replies to This Discussion

I get the same error message and fixed by chance as well. It seemed to do better when I left the resolution to match the current window res, but I really need to do higher res output. Also tried the native NXT file extension but when I tried to open it up it crashed. Hope there is a fix

 

Thanks

Jorge

Jorge -

 

Are you running in 32 or 64-bit?  Rhino 4 or Rhino 5?

64 Rhino5

 

How large of resolution would you like to do?  If you would like to send me an NXT image to try you can use the upload system:  http://www2.mcneel.com/upload/Upload.aspx and send it to scottd@mcneel.com.

 

I will test my 64-bit system here.

Janne -

 

Are you getting a crash dump dialog that comes up after the crash?  Have you filled out the email and the comment box?  We can trace those to see what is going on.

This is what I get in an error message box when I try to open up a native Flamingo NXT in the viewer

 

Microsoft .NET Framework

 Unhandled exception has occured in your application....


************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at ArPictureEditor.Form1.imageDisplay_MouseMove(Object sender, MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseMove(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
nXtImageEditor64
    Assembly Version: 1.0.4213.11981
    Win32 Version: 1.0.271.0
    CodeBase: file:///C:/Program%20Files/Flamingo%20nXt%20(64-bit)%20WIP/nXtImage...
----------------------------------------
msvcm90
    Assembly Version: 9.0.30729.6161
    Win32 Version: 9.00.30729.6161
    CodeBase: file:///C:/Windows/WinSxS/amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b...
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__...
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5447 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e0...
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f...
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c5619...
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7...
----------------------------------------
BoxIconOverlayHandler
    Assembly Version: 2.5.37.0
    Win32 Version: 2.5.37.0
    CodeBase: file:///C:/Program%20Files/Box%20Sync/BoxIconOverlayHandler.dll
----------------------------------------
BoxUtils
    Assembly Version: 2.5.37.0
    Win32 Version: 2.5.37.0
    CodeBase: file:///C:/Program%20Files/Box%20Sync/BoxUtils.DLL
----------------------------------------
BoxData
    Assembly Version: 2.5.37.0
    Win32 Version: 2.5.37.0
    CodeBase: file:///C:/Program%20Files/Box%20Sync/BoxData.DLL
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__...
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Hi Scott,

 

No I don´t, just that message with ok button. And it don´t "crash", it just dont save it, I can resume rendering or close the window and continue on rhino. But it don´t save the file.. I found one thing that helped, I closed rhino that I was workin with while rendering with another. So, no two Rhinos running at the same time.

But i´ve had that same thing before and then it had something to do with resolution, like in Jorge´s case. It was a big picture, 3-4 hours of rendering and then that notice. Few times in a row, thank god for print screen!

 

But anyway, it´s been workin now. Rhino 4, 32bit, win7

Janne -

If you are in 32-bit, running out of memory is always possible.  What is the model of?  A building?  Car? Product?

I have the same problem with 64Bits

 

before with a earlier version of nxt it happened only with a huge artificial island model, now it happened with a simple display furniture. But I thik it was that two rhinos at the same time that caused the problem.

 

Another question: Is it possible to make rhino ask "are you sure" if rendering window is closed while rendering? "stop rendering" and the window closing button are so close together, that accidents happen..

 

Thanks,

Janne

Hi Janne,

I changed the rendering engine to "Path Tracer" and that seems to do the trick. I also set my rendering restriction with time (I set it for an hour but that depends on what you are rendering) and rendered out a 10x20" @ 300DPI image that I was able to save with or without background...not sure if it's my video card but the rendering image starts out very grainy and spotty...seems like it take a lot longer to render out a clean image but at least I can save it.

 

Jorge

Jorge -

 

Pathtracer will start out very grainy, this is normal.  It also can take longer.  It is a good clue that it is only in the default tracer.  We will keep looking.

RSS

Members

© 2017   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service