hugmyster wrote:


Ok, thanks. It was just to make sure it wasn't DX9 running through DX11 but its obviously not if you've no option for this. We had a known issue with DX11 crashing on exit of the application but that's not the problem your having.

Is this happening consistently? Does it only happen with some set files?

I was just fiddling about and it blew out a second time. Hmmm. In the File > Options sections there is nothing about Direct X 11. Could it be installed or is it the graphics board?

hugmyster wrote:


Might be, could you just check the File > Options dialog and let me know if you have an option to switch on Direct X 11?

Ah, yes, there was one (and only one) difference - the output codec. I was trying the Huffy YUV to keep the file size down, but the output was a bit erratic - coloured blocks and blackouts mostly. And before you ask, no I didn't keep any of it - straight in the digital bin with that lot and changed back to the Intel YUV as per usual. The sets are all set in place now, y'see, can't change a single thing now for continuity reasons. With the iYUV in place, all the sets outputted perfectly (and no crashes after save). Strange.

Hmm... is there anything else your aware of doing before that you've not done recently? Some ideas might be, edit a character? edit lights? view the timeline? edit cameras? move cameras? change output settings?

I've had a nose and it seems I'm on DirectX 9, so not the latest version. Any use?

It is with the set I sent you, but for the full effect you'd need the other 16. Anyway, I spent last night trying to replicate it as I had to load up and render out all my cameras and I couldn't get it to do it - even after loading/using/saving 4 or 5 of the same sets one after the other, I couldn't make it crash again like I did before. I don't understand! Muvizu is toying with me...

hugmyster wrote:

If you go to the about screen (the ? icon on the top right hand corner of Muvizu) it'll tell you which direct x you are using. Let us know here or you can go into the system info (click the button) and then click the copy button and email everything to use

Haven't had time to experiment fully, but I'd say yes, it does sometimes happen that way with other set files. It's just really noticable when it's predictable, I guess. All sets are latest version .20b 64 bit DX9.

I've been running this Muvizu set-up for a while, though this is the first time I've ever encountered this error. I don't know if I'm on Direct-X 9 or 11. Can I go for a halfway house and say 10?

Incidentally, I took the purple pill. I think Morbius was having one of those days...

Does this happen with other set files?
What versions have the sets been saved in? (Go to about, system info and the muvizu tab, theres a save history there)
Does it only happen following these steps?

• Copy a light
• Open a new set
• Paste the light
• Save the new set

...which involved copying the light from the source set, then pasting it into all the other versions. I make the changes, save the set, load up the next one, paste in the light, etc. I realised, after doing this for a while, that I could actually make Muvizu crash by making sure to make saving the set the very last thing I did before loading the next one. If I saved the set, then selected stuff, moved around, etc, then loaded up another one it didn't crash (mostly!).