Neil - all messages by user

2015/8/13 12:29:44
4/8/15 Release Bugs ukBerty wrote:
Transparent would be great, but that's not what I got. I used AVI uncompressed and HitFilm.

Would I be right in thinking you'll only get transparent with TGA output, rather than video?
2015/8/10 13:13:35
4/8/15 Release Bugs ukBerty wrote:
Wouldn't it be better to be able to select which layers you wish to render from the make video dialog ? That's where I want to select what is rendered.

On it again.Gotcha!

2015/8/7 12:02:44
4/8/15 Release Bugs MrDrWho13 wrote:
Does F10 do anything at the moment? I keep closing the cameras window by accident and a shortcut would be helpful to toggle it.

F10 is a standard Windows key that moves keyboard focus to the menu so you can use them with the cursor keys. I suspect no-one ever uses it like that, but I worry about overriding Microsoft's built-in quirks. It often brings nasty side effects.

I think a Ctrl+Something shortcut is more in keeping with toggling a window anyway (like Ctrl+W for the scene window). I'll try think up a suitable one (e.g. Ctrl+F15).
2015/8/7 11:48:56
4/8/15 Release Bugs MrDrWho13 wrote:
All cameras/effects/objects/characters? You mean the exit button?

Haha, love it. Logic

How about this?

2015/8/7 11:25:04
4/8/15 Release Bugs Dreeko wrote:
While your "on it" could you pick another button which will "hide all" to hide cameras, effects, objects etc(whatever we select in "hide all" check box style) too?


Since you asked so nicely, no. On second thoughts, how about F13?
2015/8/7 10:37:48
4/8/15 Release Bugs ukBerty wrote:
What would be really useful is having F9 to toggle between "view all layers even the invisible ones" and "view only the ones marked as visible".

I'm on it.

Rebel wrote:
could you fix if for me so then when I hit the F14 key, the maid brings my coffee!

But I can't do anything about this, sorry. Send me a maid and an F14 key and I might be able to take a look.
2014/1/20 12:15:06
Muvizu main screen area continuously spinning. Hi Smartypants,

Sorry for not getting back to you sooner. I was away on holiday when you came back with the problem and I've been ill since the new year. I'll look into the problem further for you, and I think I have a temporary solution that might be better than simply unplugging the joypad. I'll get back to you soon once I've investigated and I have some details.

Once again, please accept my apologies for not being able to look into this sooner.
2013/12/18 11:49:04
Muvizu main screen area continuously spinning. Hi Smartypants,

I'm glad it's back to working as expected. In my humble opinion, I think it's likely that something had been interfering with the joypad's idea of where its centre is. This could be anything from a cat sitting on it when you booted the PC to random fluctuations in the space-time continuum (I'm looking at YOU, MrDrWho13!!!).

If it comes back, then please do try out my suggestions and let me know how you get on.
2013/12/17 12:52:54
Muvizu main screen area continuously spinning. Smartypants wrote:
Could someone from Muvizu get involved?

That would be me.

Smartypants wrote:
I don't understand why the Joystick would interact with the Mouse for input?
Muvizu only uses the Mouse, correct?

We added support for Microsoft's Xbox controller in version 1.2.


Smartypants wrote:
Perhaps it might be a Muvizu programming issue, since it still says "beta."

Getting a little off-topic for a moment, but I just wanted to point out that Muvizu hasn't been in beta since the launch of Muvizu:Play v1.0 a while ago.


Right, now let's have a look at fixing this controller of yours...


There's a configuration file called "MuvizuInput.ini" that (assuming you've installed to the default place) will be in this folder:
  • C:\Program Files\Muvizu Play\MuvizuGame\Config

Open that file with notepad. Part way down, you'll see a bunch of lines that look like this:



Bindings=(Name="XboxTypeS_RightThumbStick",Command="SwitchToLookInvert")
Bindings=(Name="XboxTypeS_LeftX",Command="Axis aStrafe Speed=1.0 DeadZone=0.3 | Axis aActorStrafe Speed=1.0 DeadZone=0.3")
Bindings=(Name="XboxTypeS_LeftY",Command="GroundForwards")
Bindings=(Name="XboxTypeS_RightX",Command="Axis aTurn Speed=2.0 DeadZone=0.3 | Axis aActorTurn Speed=5.0 DeadZone=0.3")
Bindings=(Name="XboxTypeS_RightY",Command="LookNormal")
Bindings=(Name="XboxTypeS_LeftTriggerAxis",Command="Axis aUp Speed=-1.0 DeadZone=0.1 | Axis aActorUp Speed=-1.0 DeadZone=0.1")
Bindings=(Name="XboxTypeS_RightTriggerAxis",Command="Axis aUp Speed=1.0 DeadZone=0.1 | Axis aActorUp Speed=1.0 DeadZone=0.1")
Bindings=(Name="XboxTypeS_Start",Command="UI ToggleRecord")
Bindings=(Name="XboxTypeS_Back",Command="UI TogglePlayback")
Bindings=(Name="XboxTypeS_DPad_Left",Command="UI ScrubPrev")
Bindings=(Name="XboxTypeS_DPad_Right",Command="UI ScrubNext")
Bindings=(Name="XboxTypeS_Y",Command="UI Timeline")


I've bolded the bits that control the dead zone that Ziggy is talking about. Try changing each of those so that they have a bigger number (e.g. "DeadZone=0.5" or "DeadZone=0.9") instead. Save the file in Notepad and launch Muvizu again.


Please let me know how you get on and if it fixes your problem. We don't have one of those Logitech controllers in the office to be able to diagnose the problem without your assistance but hopefully with a little patience and perseverance we can get this fixed for you. Thanks, Smartypants (love that name, btw)
2013/12/6 10:26:23
Suggestion: Drag from Prepare to Timeline Imma just leave this here...

2013/11/27 14:18:00
Render not working.... ukBerty wrote:
Hope this clarifies things....

Very much so, thanks.
2013/11/27 10:04:01
Render not working.... ukBerty wrote:
Ziggy - you can create a folder from within Muvizu - when it asks for the file name you can right mouse in the right pane and do new. It would save you clicking around quite so much.

Do you not have a "New folder" button in the "Save As" file selection dialog box that opens up when you click the "Make video..." button? That would the usual way of making a folder in this scenario.

Also, while you're in that dialog box, the default name is "Muvizu.tga" but you can type in a different name here. For example, I just changed it to "Test.tga" and it generated a bunch of files called "Test0000001.tga", "Test0000002.tga", etc.

So, I apologise again, but I'm still not seeing what it is you're wanting Muvizu to do that it doesn't already.
2013/11/26 10:54:23
Render not working.... ukBerty wrote:
Lev - not that I really understand this, but the link you supplied says we should only hit the 2GB limit on Windows 95/98. I'm running on NT 4.0 but still have the issue ??

ukBerty, the important bit from that web page is this little paragraph:
Many applications, especially older ones, use the Video for Windows architecture, which limits AVI files to 2 GB in size. Standard AVI files can be up to 4 GB in size if other methods of handling AVIs are used. However, those other methods are rarely used.

We're using "Video for Windows" which has that 2Gb limit. We want to replace it with DirectShow which will fix this, but it's a massive undertaking and I'm sure you've all heard about our enormous post-it covered to-do list.

But anyway, the reason I'm chiming in here is this...
ukBerty wrote:
Could we have it so that it automatically stores all the .tga files in a sub-directory called the name of the set? Otherwise each make video produces an unmanageable amount of files.

Have a tick both on the make video format selection which defaults to maintaining the existing behavior so users can carry on as they are if that's what they want.


Could you please clarify what it is you're wanting here? Can't you just make a new folder yourself and output the TGAs to that folder? I'm clearly not understanding something, but I'm not sure what.
2013/11/7 10:04:13
Paint tools don't work as expected. The dropper samples pixels on the screen, rather than the colour of the object under the mouse. Therefore, it'll be affected by lighting and shadows, etc.

The easiest way to copy colours between objects is to "drag and drop" the colour from one property to another...

When you edit an object, a dialog appears with all the object's properties appears. The object's colours are shown as rectangles with the colour inside them. Move your mouse over that colour and hold down the left mouse button. You can now drag that colour over to another of those rectangles and let go of the mouse button to drop it onto the new one.

I hope that helps.
2013/10/23 10:02:18
Camera editing primaveranz wrote:
Why can't you delete the first Camera segment in the Timeline while in "Direct Camera Cuts"? The only way to get rid of it seems to be to drag the second camera segment over on top of it.

Because you always need to have a camera that is recording. If you delete the first block, no camera will be recording your movie until the first block (segment as you called it) and your movie would just be a black screen.
You can change which camera the first block is referring to using "Prepare camera cuts" or by right-clicking the block and editing it.
2013/10/8 15:34:56
using a joystick Pssssst... If you have an Xbox 360 controller plugged into your PC, try it on the new v1.2 release of Muvizu.
2013/8/8 13:21:25
Tiny SOFTWARE UPDATE: Set Compatibility If you send us a set, we can narrow it down to the particular object(s) that are causing the problem, but then we'll need the original .ASE file and the import settings that were used.

If you've already sent us a set, then just hold tight for the moment and we'll get back to you with the info we need. I haven't received a set from you yet, but the submission process can take a while.
2013/8/8 10:22:59
Tiny SOFTWARE UPDATE: Set Compatibility Hi ukBerty,

We're aware of this issue and working to fix it. The problem appears to be related to .ASE objects that have been imported, then saved along with the set. There's something about certain .ASE objects that don't like being reloaded inside a set file.

What would really help us is if you could work out which .ASE object is causing it, and what settings you used when importing it. I realise you have particularly complex sets with lots of objects and if that seems like an insurmountable task, we can help with the first part.

If you have a set (the smaller the better) that gives this error on loading, could you please send it to us at bugs@muvizu.com and we should be able to narrow it down to the particular filename of the .ASE object. If you then send us that .ASE file, along with the import settings, it would be a great help to us.

I apologise for the inconvenience, it's something we're working to fix as quickly as possible.
2013/8/6 10:16:20
KOBRA AND THE LOTUS (animated film clip) I love it. Amazing video, and a cool song too. I'll have to check the band out.
Well done!
Kneel!
2013/8/1 9:57:55
Visual C++ Issue toonarama wrote:
Reinstalling Muvizu 32 bit solved the issue - thanks for your help!

Glad to hear it, thanks for reporting back.
pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19