And my character still seems to be breathing...

If you updated with the light version you might have to go to Tools --> Content packs to get Mandy

Assets that i had previously applied custom textures to, have gone from the models in my scene...gulp!!
That's going to annoy many i fear.

Every since I updated, whenever I open Beefy or Heroine they stay seated and can't stand up. Anyone else having this problem?

The lighting issue I was having - this release has made the DX9 version much worse, and the DX11 version much better. The Shadow Base slider is a brilliant fix, thankyou, as it means you can tweak out the flashing and strobing as you go, which is what you need when you're in a hurry. The DX11 performance also seems to have been kicked back into life, and is more on par with DX9 again, so I I'll just switch to 11 and call it sorted Certainly all works at distance now, thanks again mcmillan-ra! Check out these trees now!!

Muvizu HQ, you've made my year already, thank-you all.

Breathing fixed? BREATHING FIXED!! Well, thanks, but there's no need to go about it...

Seriously, thank you for sorting that. You have to give them an action to get them started, even just an idle, but it kicks in after a couple of seconds and they don't breathe again. Wonderful. Robots rejoice! See folks, you only have to request something repeatedly, on every single email you write, for 2 years, and then as if by magic...

Mandy! I wondered what happened to the Football Special stuff, nice to get it bundled in, thanks - she's good, if lacking attachment slots. Gotta give the tie and headset to the other characters as well though, be a pity if only the Man character gets it.

Good to hear about the movement thing getting fixed - less 'why wont this work?!' posts to answer

The lighting issue I was having - this release has made the DX9 version much worse, and the DX11 version much better. The Shadow Base slider is a brilliant fix, thankyou, as it means you can tweak out the flashing and strobing as you go, which is what you need when you're in a hurry. The DX11 performance also seems to have been kicked back into life, and is more on par with DX9 again, so I I'll just switch to 11 and call it sorted Certainly all works at distance now, thanks again mcmillan-ra! Check out these trees now!!



I haven't had any texture issues on loading these sets. I don't have any particular trick to get Muvizu to remember them on imported objects, it's to do with the way I create them, I think. I import the object to check it works, takes shadows, textures, etc, then tweak it further in Sketchup or whatever, remove the collision, and reimport. I open both property boxes for the new and old imported objects, and drag the textures from the slots on the old object to the same slots on the new object (because it takes too long to go back into Explorer each time, or search down the list, and I can't always remember what texture goes where, so it saves time). For some obscure reason, Muvizu doesn't 'forget' the texture if an object is textured this way - that's my theory anyway

Muvizu HQ, you've made my year already, thank-you all.

When I'm recording, I can't change the initial state (standing or sitting). I mean I stop the recording, change the state, and start recording again, but it just goes back to what it originally was. Am I missing something?

Clam wrote:



Well spotted Clam. I had a look into this and it seems this only happens if you install the characters as individual content packs. The solution is to download the full version (that includes the content packs) and then the characters work properly.

We'll look at fixing this for the content packs.

UPDATE:

We've updated the content pack, so you can go to Tools > Content packs then uninstall / install the packs and the characters will be back to normal.
edited by Jamie on 03/03/2015

Keep getting an error on loading (previously okay) sets :

An object's property has been unexpectedly changed and this file will not display properly
Object called NAME MISSING

I think its referring to a backdrop (because I got a similar message which identified Backdrop as the object in a related set). Can't actually find the not-displaying-properly object in question, and everything looks fine in all the sets so far, and it still loads so not a big issue but I thought you'd want to know. Also, the error goes away once the set has been saved with the latest version.

Keep getting an error on loading (previously okay) sets :

An object's property has been unexpectedly changed and this file will not display properly
Object called NAME MISSING

I think its referring to a backdrop (because I got a similar message which identified Backdrop as the object in a related set). Can't actually find the not-displaying-properly object in question, and everything looks fine in all the sets so far, and it still loads so not a big issue but I thought you'd want to know. Also, the error goes away once the set has been saved with the latest version.

An object's property has been unexpectedly changed and this file will not display properly
Object called NAME MISSING

I've long since ignored messages when loading sets - they all look OK to me.....

ukBerty wrote:

Same here. I can't remember the last time I opened a set without getting an error message but can never find anything actually wrong. I always just think "ah, there's the error message" and then go on with my work.

Can't seem to assign new Dialog tracks to characters - got my 3 (much used) 'talkie' tracks loaded, none now work the characters mouth. However, on loading a set, the first character I assign a track to is fine, the next isn't. Loading up a new sample doesn't help. Only happened since the update - thought it was a one off at first, but it isn't.

Can't seem to assign new Dialog tracks to characters - got my 3 (much used) 'talkie' tracks loaded, none now work the characters mouth. However, on loading a set, the first character I assign a track to is fine, the next isn't. Loading up a new sample doesn't help. Only happened since the update - thought it was a one off at first, but it isn't.