smartfoxserver.com

How annoying

But thats what release candidates are for - finding the stuff one didnt have issues with yourself.

Lets try to crack this one over here: viewtopic.php?p=37464#37464 (just to move debug talk over to a non-announcement thread)

Thanks!!

/Thomas

Exiting the FPS demo client (testing inside Unity) crashes Unity. My version is 3.0.0f5 (51258). I might tell more about the problem once I create my own client using these guidelines, but for now I have no idea what might be wrong...

Right - so there is definitely something fishy on exit. Deja vu - some connection not being closed properly. We had that thread already somewhere.

No time to debug right now though for me - going on a 1 week business trip with limited internet access now Sunday.

So keep posting and I'll give it all a spin when I get back.

Great that the UDP problem was solved though. Thanks Daniel.

/Thomas

Ah.. that screenshot reminds me of counterstrike (good old days). You guys should host that demo (once it's ready) somewhere so that we can try it out online. And since there are mostly programmers (a.k.a problem solvers) here, I'm sure they'll give you some good battle

Yeah - I hope that Marco find room for it somewhere on his public servers once the kinks are ironed out.



/Thomas

ThomasLund wrote:Right - so there is definitely something fishy on exit. Deja vu - some connection not being closed properly. We had that thread already somewhere.
/Thomas

Kicking the player out of a game (so he's forced back to the Lobby login) works without falling over, so the problem may not be exiting the Game (unless the Game is failing to close it's connection?). Closing/Stopping the app on the Lobby screen at this point will also freeze the standalone app/Unity.

Unity 3.1 freeze on stop debuging and run debug again. Net Threed not killed?

And I'm can't start created game:



And i can't to close Unity after. Only by Task Manager.

Does adding this code to the lobby scene and game scene solve the problem?

This code exists in SmartFoxConnection.cs in game scene.
Then I try to start new game, I see next screen:

And console show error:

So - besides the trouble of shutting down + UDP firewall blocking.

Had time to look at the code itself? Makes sense to all and is valuable as a learning tool? Any improvements or changes or unclear things?

Personally I am not too happy about how shot results are reported back. In hindsight I think we should have done a shotHit, shotMissed instead of sending back health update only. But code can always be improved

/Thomas

@PAX I found that I had to put the code in the scene file and not in the smartfoxconnection.cs. When I stop the game in the editor the OnApplicationQuit does not fire in the smartfoxconnection.cs. At leats for me.

@Thomas I hope to be able to look at the code in more detail this weekend. I know you have a lot in there thanks

I simply install server and open client in Unity 3.1. No code changes (only upgrade to RC1a). And I still could not run the demo

@stevets I will try... UPD: nothing changes

@PAX did you add this to the lobby

http://www.smartfoxserver.com/forums/viewtopic.php?t=8878

stevets wrote:@PAX did you add this to the lobby

Yes, to all scenes.

stevets wrote:http://www.smartfoxserver.com/forums/viewtopic.php?t=8878

I start socpol.exe with --all flag. On first screen all connections are ok. And my app is not wab oriented. Its standalone.

And Chat works:


Windows can't normaly close standalone app. Is a Threed bug i think.

GREAT!!!!

the new demo! that means happy coding