I am using 3DFA v. 3.72 to make a game. In the game, I have two moving elements - one controlled by the user, one which is started by the user pressing a key (up arrow) and then it moves independently and randomly. When exported and viewed in the browser, the independly moving element does not move when the key is pressed, or indeed at all. I also have a collision detect set up between the user-controlled element and the independent element, which works fine in 3DFA, but in the broswer this doesn't work either.
Does anyone know how I can fix this or what is causing it?
I've had problems with collision detection in the browser too, although it works fine in 3dfa.
ie. In v4 beta 2, sometimes collisions are detected when there aren't really any, and sometimes they aren't detected when there is one. I am still investigating, but so far, I think it's related to 'friction' on the element.
I've just reported it to 'support', and I'll post a reply if I get an answer.
I never really tested this in v3.72 though, so it may be unrelated.
Does the problem element in your example have the 'friction' property set?
*thinks* well, yesterday I uploaded a Flash game with about 10 .pngs to a site...and none of them seemed to need uploading as well for the game to work.
Originally posted by white_queen *thinks* well, yesterday I uploaded a Flash game with about 10 .pngs to a site...and none of them seemed to need uploading as well for the game to work.
~Milli
When you export to flash, all your files come with the swf file, if you don't have any external MP3:s. When tou upload a movie source, you have to send with the pictures. But when v.4 releases, we will be able to attach the files to the .movie file.
Still crashes my 3dfa (Both v3.72 and 4 beta 2). I'll have to leave it to an expert.
Shame - Because it sounded like the same problem I've been having.
OK, I still can't open the file, but I am sure about my problem now, so this might help you prove where your problem lies :
As a test, remove all reference to properties like acceleration and relative_acceleration and velocity from the cat. These probably act like the friction in my example, and could be the root of the problem.
Add an action script that simply places the cat at the mouse coordinates.
ie.
cat.x=mouseX();
cat.y=mouseY{};
See whether the collision detection works without those properties set for the element. If so, then the problem is pretty much the same as mine, and you'll need to drop a mail to '[email protected]'.
Reply With Quote
