help fix connection error

please bare with me since i'm new to the nonoba api.

i can run the demos through FlashCS3 and it connects properly but when i try to load the swf in a browser (outside of FlashCS3) i cannot connect to the test server and i get the following message:

'Unable to connect to the server localhost at port 8184 due to security error'

first it thought this had something to do with the flash global security settings privacy settings so i enabled access to my whole harddrive but that still doesn't seem to fix the problem.

any ideas?

i have noticed that the FlashCS3 flash player is different from the browser version. i am able to use the FlashCS3 player and test all the demos and open multiple versions (i.e. for tictactoe demo). what is there a difference between the two players that makes the browser version fail to connect?

If you're running it locally, no matter what, you need the test server (the c# project) running. Open the project file in visual studio and click the play button, then try again.

If you're uploading it to the internet and trying to play it, this will not work either. You need to upload specifically to nonoba for it to associate the DLL file with the swf and make the serverside magical stuff work. :)

It's the wrapper you then upload to other sites.

Toby,

I have the test server running but i've noticed something funny.

The standalone flash player used by FlashCS3 works fine but this is different from the standalone player used by the web browser which doesn't work.

For one thing the one for FlashCS3 is ver 9 and the browser is ver 10. is that a problem?

i can still develop nonoba since i can use the ver 9 player but i'm just trying to figure out if i have another problem on my side.

You can't just load the swf through a web-browser while the test server is open. To use it on a web browser you have to upload it to nonoba with the .dll to assosciate the files with eachother and get the server magic working.

You can actually use the browser to test in.

As you guessed yourself you need to add the game to your list of allowed objects here.

I found that I need to do it for each file, as just enabling it for the entire drive does not work. Luckily the settings manager has a button to get the last path that tried to do something outside the sandbox.