Hi,
Based on previous threads and code examples such as:
http://forums.cgsociety.org/showthread.php?f=98&t=1006144&page=1&pp=15
I have 2 issues with viewport capturing in 3dsMax:
- ForcecompleteRedraw() or completeRedraw() sometimes randomly crashes the code below
- .NET memory is not freed even though this struct is instantiated each time its used. I have to exit 3dsMax to free the memory.
Any ideas?
fn ResizeViewport width height=
(
compensation = 4
ViewportHwnd = for w in (windows.getChildrenHWND #max) where w[4] == "ViewPanel" do exit with w[1]
source = "using System;
"
source += "using System.Runtime.InteropServices;
"
source += "using System.Text;
"
source += "class assembly
"
source += "{
"
source += " [DllImport(\"user32.dll\")]
"
source += " public static extern bool SetWindowPos(IntPtr hWnd, int hWndArg, int Left, int Top, int Width, int Height, int hWndFlags);
"
source += " [DllImport(\"user32.dll\")]
"
source += " static extern bool GetWindowRect(IntPtr hWnd, out RECT rect);
"
source += " public struct RECT
"
source += " {
"
source += " public int Left;
"
source += " public int Top;
"
source += " public int Right;
"
source += " public int Bottom;
"
source += " }
"
source += " public int[] getWindowRect(IntPtr hWnd)
"
source += " {
"
source += " RECT rect;
"
source += " if ( GetWindowRect(hWnd, out rect) )
"
source += " {
"
source += " return new int[] { rect.Left, rect.Top, rect.Right - rect.Left, rect.Bottom - rect.Top };
"
source += " }
"
source += " return null;
"
source += " }
"
source += "}
"
csharpProvider = dotnetobject "Microsoft.CSharp.CSharpCodeProvider"
compilerParams = dotnetobject "System.CodeDom.Compiler.CompilerParameters"
compilerParams.GenerateInMemory = on
compilerResults = csharpProvider.CompileAssemblyFromSource compilerParams #(source)
assembly = compilerResults.CompiledAssembly.createInstance "assembly"
assembly.setwindowpos (dotNetObject "System.IntPtr" ViewportHwnd) 0 0 0 (width+compensation) (height+compensation) 0x0026
ForcecompleteRedraw()
)
Hi Mike,
What is it you are trying to do with this code, get a viewport thumbnail?
Hi Pete,
Screen grab but at a high resolution, so after scaling down, the image looks good at something like 1024 768. Thumbnail size is no good for my needs, so I can’t take a different route such as .Net rip the file thumbnail.
Mike
Cant you just use max tool maximize and then grab the viewport resize the image and restore viewport layouts?
That’s how I’d do it, but maybe Mike needs a capture bigger than HD?
Yeah, I thought about it too, and I guess he needs to capture a res higher the one setup for the display, from what I understood.
Another quick “hack” would just use quicksilver to render the thumbnail in whatever resolution you need.
Thanks guys. Higher res is indeed the challenge here.
Anyway, after lots of testing by a colleague of mine + combined with a bit of a random thought/head scratching and it would seem that changing the 3dsMax graphics driver to OpenGL has now stabilised the code. I have a sneaking suspicion that the Direct3D driver and its directX caching of textures/viewport was causing an issue when it came to a forced refresh.
We have some more testing to carry out, but at least we think we are on the right tracks to squashing this bug now.
Sorry, I should add, that we still haven’t got to the bottom of why .NET memory isn’t purged when the struct is thrown away. [insert another sarcastic reason why I love 3dsMax/mxs]
Thanks again for your comments.
Mike
Hey Mike. Hope all is well!
Have you tried disposing all the dotNet objects in the struct, undefining it, and then running a garbage collection?
gc() or gc light:true
Hopefully that should clear some memory.
You can also tell the dotNet system to do its own specific clear-up, this might do the trick:
gc light:true
(dotnetClass "System.GC").Collect()
If that doesn’t do the trick, this might?
gc light:true
(dotnetClass "System.GC").Collect()
(dotnetClass "System.GC").WaitForPendingFinalizers()
(dotnetClass "System.GC").Collect()
Hi Tim,
Yep, tried both these options and all .Net objects are also disposed off prior to this as well. So, at the moment, it looks like a combo of graphics driver in 3dsMax and a later .NET function which resize’s the screen-grabs is causing the issue. We are running more tests today…
Thanks,
Mike
first of all you shouldn’t create a new assembly every time you resizing viewport… it will save the memory
second you have to return viewpanel in normal size … and it helps to protect the max from a crash
see my post http://forums.cgsociety.org/showpost.php?p=7108699&postcount=10