Neil - all messages by user

2013/4/17 14:30:55
Double click camera window - CRASH Ember, could you please do me a favour and try something else to see if you get the same crash?

  • Right-click the camera (the 3D camera itself, not the window) and select "Edit".
  • In the dialog box that opens, there should be a "Show window" button. Click it.
  • It'll either crash the same way, or open up a new window with just the view from that camera in it.

Let me know what happens. Thanks.
2013/4/17 10:12:22
Double click camera window - CRASH ember wrote:
I don't know which .net package to install, is it ?

Yes, that's the one.

Or this one will do:

Yours is the stand-alone installer that downloads everything before you run it. The one I linked is the web installer that is a smaller initial download, then it downloads only the bits you need when you run it. Either way, they both install the .NET Framework 4.

As for the actual crash, I'm sorry that we haven't released a fix for it yet. We're really struggling to get that same crash at Muvizu Towers and until we do, we can't work out what's causing it. Rest assured we're working on it, but please be patient with us. In the meantime, please accept my apology and have a funny animation of a baby polar bear being tickled.

2013/4/16 16:45:22
saving set error fazz68 wrote:
its not the volume control, its if i click the pointer thingy anywhere outside of muvizu. (ie, anywhere on the taskbar, or if muvizu isnt full screen and i click next to it) but click back onto muvizu the sound comes back......

Yeah, we switch our sounds off if we're running in the background.
2013/4/16 15:40:07
saving set error fazz68 wrote:
hello neil.
the set was made in the first version of Play, you released the patch which was installed. i saved it in the patched version, then the 1st set save error appears (very top picture in this thread) and the other things this patch has caused (the sound problems and waveform missing)
so i thought id see what the 32bit version was like as woztoons said he didnt have the problems in that version, so i installed that version and the set saved with the error message gave me a fatal error message and crashed muvizu. (nearly there Big Grin)
so i uninstalled the 32bit version and reinstalled the 64bit version but didnt update it with the patch and that is the final picture, unknown format message. and since then ive left it alone

hope that all makes sense

edit... but if the message is lying surely the set should still load?
edited by fazz68 on 16/04/2013

Okay, I think I have a handle on what's happening so I'll try to explain.

Firstly, the error message that is lying is the "Unknown error" one with the red exclamation mark when you try to load or save a file. You can tell that it's lying because your set will still load and save correctly.

Secondly, this new (and different) error message that you're seeing about the "Unknown format" that has a picture of a folder and a question mark ISN'T lying. The problem is that you've saved a set with a newer version of Muvizu, then attempted to load it in an older version.

The file format is constantly being tweaked and updated, but we take care to make sure newer versions can still load files from older sets. We can't make it work the other way round, however. An older version of Muvizu can't know what changes we've made to a future file format, so it can't load it. There was a change in the file format for the patch that fixed the error people were seeing when loading an older set, and so now the unpatched version of Muvizu:Play v1.0 can't load sets that were saved in the patched version.

You should still be able to load your set in the patched version, and can safely ignore the error messages with the red exclamation mark when loading / saving sets.

I hope that makes sense, and I apologise for any confusion or inconvenience. We hope to get another patch out soon to patch the err... patch.
2013/4/16 14:44:18
saving set error Hi fazz68. What version of Muvizu are you trying to load the set into, and what version was it last saved in?

Regarding the "unknown error" message that is happening on loading / saving, it seems that the error message is lying and can safely be ignored.
2013/4/16 10:47:25
Superman Episode 4 is done toonarama wrote:
I think you are absolutely right about short attention spans these days


(Just kidding)
2013/4/15 10:47:24
Muvizu:Play 1.0 timeline discussion MrDrWho13 wrote:
Good luck for getting through the forum tsunami on Monday!

Thanks. I've been here all weekend in stealth mode, so it didn't take too long to catch up this morning. Now, I just need to work out what to actually do with all this lovely feedback.

Cheers everyone, much appreciated.
2013/4/15 10:28:48
Moving Favorite Characters to new Play version Your favourites should be stored in this folder: "C:\ProgramData\Muvizu\Favourites".

If you have a look in there using Windows Explorer, you should a see a list of ".FAV" files. These are your favourites.

Both the old and new versions of Muvizu (and Muvizu:Play) should be looking in this folder and reading your favourites, so there shouldn't be any need to move them over if you've got both versions installed.
2013/4/12 17:28:51
Muvizu:Play 1.0 timeline discussion I dig the separate window for the transport controls (play, stop, etc). Nice one, Woz.

Some time last year, I had them on a status bar that permanently sat at the bottom of the window. It had the usual controls in there, plus a slide for scrubbing backwards and forwards through time. It was great, it made the timeline so much easier to use. But there was a technical problem (isn't there always) and it had to be removed. I think there might be a way to bring it back for only timeline / directing modes.

That's a task for next week though. It's Friday evening. I'm tired, drained and emotional so I'm going home. Please keep the feedback and suggestions coming over the weekend, I'll try to check in occasionally. Seeya Muvizuers. Thumbs Up

PS: I've had some success with only showing animated things in the timeline as per Dreeko's suggestion. It needs some work, but I think it's a goer.
2013/4/12 14:22:49
Muvizu:Play 1.0 timeline discussion urbanlamb wrote:
Yes I have its just I am repeating myself at this point so its feeling a bit frustrating

We've heard you. Please don't be frustrated, you've made your points very clear and we're working hard to address them.
2013/4/12 10:33:20
Muvizu:Play 1.0 timeline discussion urbanlamb wrote:
Anyhow I am beginning to worry my muvizu days are over as it seems that my please to have a functional complicated timeline are going unheard.

Urbanlamb, your pleas aren't going unheard. I've responded in the forum with a long post detailing exactly where we are, what we're trying to do, and specifically asking the community for their input on how to improve things for you. Please continue to contribute constructively.

Dreeko wrote:
Surely it would be better to only have the timeline for an object etc created once it has been animated ( or directed as we call it) rather than the second in appears on set?

Dreeko, that does sound ideal in principal. We tried something similar to that in development, but there were issues with it. I'll revisit it and see if we can get it working.

2013/4/12 10:16:34
Muvizu:Play (V1.0) Feedback I've created a new thread to discuss suggestions for improving the timeline as this thread is getting quite bogged down with it and I don't want other feedback from v1.0 to get lost in the discussion.

If you have any feedback or suggestions on the new timeline in Muvizu:Play v1.0, please post them in that thread. Thanks, everyone.
2013/4/12 10:13:57
Muvizu:Play 1.0 timeline discussion I've started this thread to discuss suggestions on how to improve the new timeline in Muvizu:Play 1.0. The discussion has been taking place in the v1.0 feedback thread, but the timeline has created enough discussion on it's own that I thought it deserved it's own thread. We can use the original thread to discuss other feedback from v1.0 without getting bogged down on the timeline.
2013/4/11 15:01:04
Muvizu:Play (V1.0) Feedback ukBerty wrote:
One last tiny issue, but really annoying. When loading a set you still get the "Object too small to import" error (although it still all imports) but now the "close" button is directly over the "abort" button which will stops the set loading. This can lead to a lot of swearing.

ukBerty, do you have a small set you can send to me that has this problem? If so, could you please send it to with a note to forward it on to me. Thanks.
2013/4/11 14:25:32
Muvizu:Play (V1.0) Feedback Thanks for all the feedback, folks. I'm endeavouring to tackle some of the UI issues that have been discussed here. Some of them were already fixed but didn't make the deadline, some have been fixed as a result of your feedback, and others will be addressed shortly.

I wanted to take the time to get you up to speed on where we're at, plus I have a few questions that you can help me with. I also want to thank MrDrWho13 for helpfully collating them all into a handy list. Seriously dude, if you ever want a job as my personal assistant, gimme a shout.

MrDrWho13 wrote:
Timeline to have all options closed at start and opened by user individually

I can see how showing everything by default can be frankly a bit poo if you have a large set, but we have to consider the opposite problem of an inexperienced user opening the timeline for the first time and seeing it completely empty and not knowing how to (or realising they can) make things visible.

I wanted to ask what people thought of this. Is hiding everything by default the way to go, or would it be confusing? Is there a third option we haven't thought of?

In the meantime, I've added "show all" and "hide all" buttons to the filter dialog so you don't have to untick everything. Longer term we're looking at ways of saving the ticks into the .set file so they'll be remembered when you save and reload it. Hopefully we'll get a new version out to you soon with this in. They should've been there originally, but we overlooked them. Sorry about that.

MrDrWho13 wrote:
V0.23b compatibility issues

We've isolated the problem and already fixed it. Again, we hope to get a new version out soon with this fixed. We're sorry about this too.

MrDrWho13 wrote:
textures not showing when you go to add a texture you are already using

I'll be looking into that soon.

MrDrWho13 wrote:
dialogue with 4 characters only the 1st dialogue part you do shows up in the time line until you untick the next character and tick again in the filter

I'm pretty sure this has already been fixed, but I'll check.

MrDrWho13 wrote:
Other issues related to the timeline

I think we're talking about Ziggy's issue with the font and button sizes. If not, help me out here, what have I missed?
Everything in the timeline is intentionally small and doesn't have a lot of margin so you can see more of what you're working on as we've had criticism before about having too much wasted space in the timeline. Did we go too far?

MrDrWho13 wrote:
recent scenes do not show on start up

MrDrWho13 wrote:
tutorials message won't hide

There two are already fixed.

MrDrWho13 wrote:
Double click on camera window crashes app

We haven't seen this one here at Muvizu Towers and we're working to find out the cause. Please bear with us and if you're having this problem, please work with Jamie and his team to help us diagnose it.

MrDrWho13 wrote:
when zooming with scroll button, it's difficult to get back to where you were

I confess I'm not really sure what this means. Gimmick, could you expand on what you mean here, please? Do you mean zooming in the timeline? Feel free to PM me, or discuss it here.

MrDrWho13 wrote:
"close" button is directly over the "abort" button - see ukberty's post

I'll look into this one personally as we can't have ukberty swearing. This is supposed to be a family friendly forum.

MrDrWho13 wrote:
'ERROR Lipsync data could not be processsed'

This one's new to me. InsaneHamster, can you expand on how to get this error message? Feel free to PM me, or discuss it here.


Phew, that was quite a list. Hopefully that's given you some insight into where we're at. Please bear with us while we address these issues, and please keep the feedback coming (both good and bad). We're here, we're listening, and we haven't stopped beavering away.
edited by Neil on 11/04/2013
2013/4/9 12:23:36
Is it ready yet? Dreeko wrote: know?

He knows. I know. You know. I know he knows you know. We're all good.
2013/3/25 13:32:07
help - PUBLISHING VIDEO - please!
2013/1/11 12:05:20
Moo Marco_D wrote:
That made me laugh Flashing images of cows driving pimp-up cars at high speeds on my mind now!!

2013/1/4 10:53:40
Happy New Year HayManMarc wrote:
Doomsday has been going to happen for quite some time now:

Oh yeah, the world ends a lot. When I was a kid it was all about Nostradamus.
2013/1/4 10:12:02
Happy New Year urbanlamb wrote:
2013 is one year of bad luck for those who are are superstitious I suppose.. Big Grin

Nah, all the superstitious ones left the planet in 2012. If Rapture v1.0 or v2.0 didn't get them, the Mayan Apocalypse would have.

Happy New Year everyone.
pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19