Problems loading a walking sequence

Hi guys, I just made a screen recording of what happens. Yesterday evening VS allowed me to load a sequence once, today the error occured again, no way of loading the sequence. As already said, I use PNGs with alpha channel, 500 x 800 pixels for the charakter.

http://youtu.be/91wMxsZnUiE

Seems like a mac problem. I got a similar error message on my machine. Wrote a post about it

Hi guys,

actually I just found out that I seem to be able to load the single frames for the walking animation manually, by using the "+" button ans always picking the next image in the sequence. It's more work, but it seems to work. Is there anything that speaks against this method? Will there be a problem later on?

Damn learning curve.

Cheers,
Marian

Phew! I've spent the last hour adding the the walking sequences frame by frame, I hope there will be no problems with that method later on. It was a little exhausting and very boring, but not Jacob can walk in eight directions. I hope I will be successful creating the first scene with the arrest cell background!

Sorry if annoying you, but the next problem has occured. I am following the tutorial by glenfx step by step, I was able to add standing and walking animations manually (by single frames), create the first scene with background and walkable area and so on. But when I hit "save and run", i get an error message saying "Init failed, could not load game. There ist no game file or the game file is corrupted. For more info view messages.log."
Unfortunately, there is not messages.log on my system. Any suggestions? Buy a windows PC?

Hi again,
Mumpi seems to have found a solution for the sequence problem: VS on Mac does not seem to like the spaces in the filenames when loading a sequence. I just renamed the sequence frames to names without spaces, i could load the sequence without any problem. At least for now. I will try to apply this method to the whole project and see if the "save and run" error will still be there.

And again, hello. I found out something else: To try out Mumpis solution I moved one sequence to a separate folder and I cancelled all the blanks in the filenames, like this I was able to load the sequence. Then I renamed all the filenames in my base folder, where I have all of the media. When I tried to pick a sequence there, I got the error message again. Then I gave all the sequences for each walking direction a separate folder. Now VS lets me load the whole sequence again. Now I don't know whether I need filenames without blanks and separate folders for each sequence, or just separate folders. I will find out tomorrow, I don't feel like renaming the whole sequence again today.

Oh crap, I could not go to bed. I had to try the separate folder/blank issue thing: I took one of my sequences and re-added the blanks to the filenames. VS still allows me to pick the whole sequence, as long as there is nothing else in the folder but the sequence.
So having a separate folder for every animation sequence will solve this problem. (at least it seems so at present)

Hi guys,
I finally get some success! I gave every sequence an own folder and now I can select whole animation sequences! The save and run functions seems to be working well now, too!
VS seems to be a little picky when it comes to files and folders.

This is a reply to this post, and my post about an error with the "Set object position"-tool:

Hm… I didn't use any blanks in my filenames, but the problem have disappeared or persisted by itself. What I did to remove the error message was to manually enter the position of the mark in "alignment to character (or charter as it says ) to object". So instead of using the "Set object position"-tool I used the navigation numbers (646,273) from the scene viewer. I put those numbers into the x and y position, and the mark turned up where it should be.

I did this once, and then the error message disappeared. Suddenly I can use the "set object position"-tool without any trouble or errors.

Good to know. I didn't have this error yet, but it's great that it seems to be possible to fix VS issues on Mac. I hope our postings will help the visionaire team to identify the reason for the errors and fix them. As already said, VS on Mac seems to be a little bit picky.