Latest posts for the topic "Welcome to the Help forum"

Welcome to the Help forum

matt — GMT

If you've got a problem with Moviestorm, you've come to the right place. Feel free to ask. Don't be embarrassed - we're a friendly bunch. What we would ask is: - Do have a look in the support forums first to see if your question has already been answered. - Give us a few days to respond. If we don't reply, it's probably because we're busy, or on holiday, not because we're ignoring you. (We don't generally work nights or weekends.) A friendly nudge is usually sufficient to remind us. - Be polite. We're more than happy for users to reply to questions. In fact, we'd encourage it! If you do reply: - Don't pretend to be one of the dev/support team if you're not. - Be nice. Thanks!

Re:Welcome to the Help forum

Ben_S — GMT

Sometimes you may encounter bugs, and there are certain files we will want to see to help us fix them, or to help you to work around them. Logs Moviestorm creates two sorts of Log files, one as it is running, and one if it crashes. LOG.txt is the normal log file, created as moviestorm is running. It is found in WinXP: C:/Documents and Settings/[your win username]Moviestorm/ Vista: [your win username]Moviestorm/ hs_err_pid###.log is the crash dump, if moviestorm crashes. It is found in the instal directory: eg C:/Program Files/Moviestorm Your Movies Sometimes there are problems which are specifically related to a movie. Your movies are stored in: WinXP: C:/Documents and Settings/[your win username]Moviestorm/Movies Vista: [your win username]Moviestorm/Movies - in a directory named after the movie name. The file movie.mscope is the most important part of them, and contains details of how your movie does things. Diagnostics Sometimes it helps us to see information on your computer system. Most people will have directX installed, which has a useful diagnostic program. To get a dxdiag.txt report, please go to File - Run and type in dxdiag This will start the directX diagnostic program, and click Save All Information. This creates a text file called DxDiag.txt which we will want to see.

How to write a bug report

johnnie — GMT

HOW TO WRITE A BUG REPORT There are more Moviestorm users every day, and a lot of you are keen to help out by reporting any bugs or issues that you encounter while working with the program. We're extremely grateful for that, and we read them all and try to act on them as best we can. Often, though, we'll ask for additional information that you didn't initially provide, or we'll ask for clarification of something that was unclear from your post. This post is meant as a guide to follow when filing a bug report. Follow the steps below as best you can, and we're more likely to be able to reproduce and act on the issue. Your bug report should contain the following sections: (1) Description of the issue Describe the error concisely and accurately. Be sure to specify why this behaviour is a problem if it's not obviously detrimental. Don't speculate as to possible causes for the behaviour - that can be included later. Specify what the issue affects and what it doesn't (the "scope"), as best you can. For example "affects chair objects only" or "affects all scalable objects". (2) Steps to reproduce You should list the steps that we should take to replicate the problem, from scratch. Please be as detailed as you can - don't assume that we know what intermediary steps you took. (3) Hardware/Software specification This bit is crucial. Please supply the version of Moviestorm you're currently running (which can be found by clicking "Help" on the main screen, and then clicking the Version Number link). Please also tell us your Operating System (Windows XP, Windows Vista, Mac OS X Leopard, etc). You should also list as much of the following as you can: your processor make and type, your graphics card model and the graphics drivers you're using. (4) Attach your log files Please attach your log.txt file, and other crucial files as detailed by Ben_S in the post right above this one. Please use the "attachment" facility to attach the files to your post, rather than including them verbatim in the text of your post. (5) Suspected cause (optional) If you think you know what was causing this problem, feel free to speculate. There's no need to include this stage though - finding the cause of the problem is our job, not yours! This post isn't intended to frighten or criticise anyone. We're just trying to save you (and us) additional effort. All bug reports are gratefully received, so please don't stop posting! Code:

AN (ENTIRELY FICTIONAL) EXAMPLE BUG REPORT

Description of issue:
	Moviestorm turns pink when placing hedges.

Steps to reproduce:
	(1) Start a new movie, and choose the "Mall" set. Do not choose any pre-existing characters.
	(2) Switch to the Set Workshop.
	(3) Open the Object Browser
	(4) Select the "Hedge Medium" object
	(5) Place the hedge anywhere on set
	(6) The Moviestorm interface turns a garish pink, with lime green polka dots.
	
Hardware and software specification:
	Moviestorm 1.0.1, running under Windows XP Professional Service Pack 2 (build 2600).
	2.80 gigahertz AMD Athlon 64 X2 Dual Core
	NVIDIA GeForce 8600 GT
	NVIDIA drivers 6.14.0011.6371

Welcome to the Help forum

emorris2u — GMT

When I place a character in the scene and then when I joom in or out the character becomes a glob of color. Is that a graphic card driver or ram issue ? Thanks

Welcome to the Help forum

Spong3y — GMT

emorris2u wrote:

When I place a character in the scene and then when I joom in or out the character becomes a glob of color. Is that a graphic card driver or ram issue ? Thanks

emorris2u, I would recommend posting your question in a new thread, because this thread is specifically made to tell users how they can ask questions in this forum. However, I will be glad to answer your question. The problem seems to persist with your graphics card. Do you use an ATI card? If so, downgrade or upgrade your Catalyst Driver to 7.11. It removes most of the problems in Moviestorm such as blotchy characters and crashing. As for RAM, the graphics will not be affected even if you don't have a lot of memory. However, RAM of 2GB or more is recommended while running Moviestorm. 1GB is the mininum spec, and you can encounter slowdowns early when using low RAM.