headus 3D tools

[Squid]

Hi,
Whenever i load a mesh using the cmd line switches (xsi plugin) with uvlayout set to edit uv's i get caught in a cycle of uvlayout loading the file, writing to the file, then (because the obj seems to be flagged as changed) reloading the obj - ad ifinitum.

i can reproduce the error everytime, through xsi or the bog standard cmd line.

everything is fine when uvlayout is launched normally though.

Hope you can help

thanks

/edit - slight revision :
uvlayout seems to struggle deleting the obj file after it's created the shells. it will eventually delete the file (and stop reloading) but it's taking, on average 15 or 16 loads. this lowers to around 10-12 from a normal command line launch

[headus]

Sorry about that! It worked last time I checked, but that was a while ago. I'll have a look now ...

Phil

[Squid]

much appreciated

[headus]

Like you said, UVLayout may be having problems deleting the OBJ file, so next time it checks, its still there and kills the one it just loaded and reloads, again and again. Looks like I need to handle errors on the delete a bit better, and put in some sort of minimum time required before a reload is allowed.

What it could be is that your application writing the OBJ (XSI I guess) isn't closing the file completely, so that blocks any other applications from deleting it. My suggestion (and it is hidden away there in the plugin docs :-) is to write to a temp file, then use the windows copy command to copy that to the target OBJ.

If you're already doing the copy thing, let me know and I'll rush through that code to handle the delete errors better.

Phil

[headus]

I had a closer look at the code, and it already has a 10 second minimum wait before checking for a new OBJ ... is that what your seeing, 10 seconds between your reloads?

Phil

[Squid]

my code -
if (uvlayout is running)
write to a temp obj file
rename it using the fielsystem -
actually i'm just moving the file as there's no rename func with the filesystem obj

i just tried it using the windowsshell and i get the same results.

The effect does seem more prevalent on higher res meshes. standard objects sometimes load first time.

With weld, clean and Detatch Flipped turned on it seems more reliable too...which makes me now think that this may be a bug with the fellow sat behind my computer

is there a limit to how many shells uvlayout can/will create ?

thanks for the help

[headus]

[Squid]

[headus]

Ive made the fixes to the plugin code ... its smarter now about handling these delayed delete conditions, plus you can turn on some debugging that gets sent to the shell window so you can see whats happening internally.

Just have to fix another unrelated problem, then I can upload the new installer!

Phil

[Squid]

awesome

[headus]

All done! I'm uploading the new installer now, and will post to the Update forum when its ready to grab.

Update: Uploaded. See http://www.headus.com/phpbb/viewtopic.php?p=1448#1448

Phil

[Squid]

fantastic, downloading now

[Locke]

Hey Phil, this sucker is back for me. Trying to load up a 5000 poly object using the XSI plugin and told UVLayout to use the existing UVs. I then get into the infinite loading loop but cyeat.exe is throwing this error:

"Instruction at 0x69747139 referenced memory at 0x01d20040. Memory could not be written to."

[headus]

Does the OBJ load OK if you don't use the XSI plugin link?

Phil

[Locke]

Actually, I think it's the object. It gave the same error when I did it by hand but didn't get stuck in that loop. Checking clean and weld on the load options allowed it to load.

I'll send you the mesh.