Printable View
http://www.aquadasoft.com/LacewingBanner.gif
MMF2
* Lots fixed in the server
* Miscellaneous fixes and tidying in the client
* Server extension and Flash version now contained in the same ZIP
* Lacewing is now global in Flash
* Server messages are now received in Flash
C++
* Loops fixed
* Miscellaneous fixes and tidying throughout the library
Server, C++ library, extensions
Whoo Hoo! A new build! Great job, Jamie. :D
Great job Jamie :D Cant wait to download ;) What should I do with the "Lacewing.dat" file in the Flash Folder?
Nothing, it's the flash version of the extension. You need the SWF exporter.
A bug still exists Jamie. I think its the server itself. In my game I connect to a channel, then connect to another channel (lobby) and switch back to the previous channel (game). This works fine with the slower klikfarm server, but not in the aquadasoft server.
The Klikfarm server was written by me (it uses Lacewing.dll) but the aquadasoft.com server was written by Mathias (it uses pylacewing).
is it not possible to fix? Should I talk to Mathias then?
Yep.
YEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAH
And the on ping failed option is Still not working :(
Changing the client name server side (in a name set request) doesn't seem to work anymore, in the end, the name is still the name the client asked for.
EDIT : This seems to fix the server send to channel action, thank you very much Jamie !
Oops - I'll sort it out for the next build.Quote:
Originally Posted by Corentin
http://jamie.ath.cx:8030/SS-2010-05-03_19.16.16.pngQuote:
Originally Posted by DJFuego
?
It must be my code. a clean app runs the ping just fine. My existing one doesn't. Never mind; I take it all back now. You are my hero :D
If anyone starts to get errors with this again, please make a post about it. I'm not quite sure why it's happening, so I'll try to debug it properly the next time it starts to bug!Quote:
Originally Posted by Sumo
EDIT: I've found the bug! Basically, channel IDs were returned twice to the channel ID pool, so I'm going to fix that now ;)
Cool. Thanks Mathias :)
Should be fixed now! :)
I think received stacks aren't automatically cleared in the lacewing client extension... I don't have much time to test it at the moment, but I tried to save to file and I had a constantly growing file (without using append option, and restarting app reset the size back).
I think I found a bug (this was in previous versions);
The lacewing server (the .exe) refuses to update itself, even though I set the autoupdate value in the .ini to 1.
If that was in the previous versions, why dont you download the new lacewing version that comes with an updated LacewingServer.mfx and check it outQuote:
Originally Posted by JIMJ316
The auto update has never been implemented. It was in OINC, but I lost the source to OINC and never got round to reimplementing the auto update in Lacewing.
Sorry about my last post, I reported a false error : client recieves stacks ok, it's the server "automatically clear stack" that doesn't work anymore in this latest version. Clearing manually works perfectly.
Ah yes, you're right! Thanks :)
Fixed in the next build.
Good job ;)
Thanks
Silly mistake in the server causing a random crash (every day or so) fixed in build 15 (if you're finding it's crashing).
You have in Lacewing condition "On peer disconnect"
and I have sugestion to add 2 new condition: "On peer >peer name< disconnect" and "On peer >peer id< disconnect".
What are you thinking about this?
You can just do -
On peer disconnect
+ Peer_Name$("Lacewing") = "Some name"
or
On peer disconnect
+ Peer_ID("Lacewing") = 1337
Just use Compare two General Values and compare the Peer name$ or Peer ID# to whatever you want.
EDIT: Oh darn, beat by Jamie for thefirst time eversecond time >_<
I know that.
Btw it's so easy to crash Lacewing by condition Allways-> conect to "localhost" 6121.
Somebody who know my IP adress can crash my server. :(
That crashes the server? Are you sure?
Jmaie, I recall issues happening when you connected while you were still connecting before but hadn't yet made a connection.
Yes, I found another condition too when I try change another peer name by another application...
Application 1:
On text message from peer on subchannel 0 (sent)-> Set name to Received$( "Lacewing" ) and Send text "I successful changed my name" to peer on subchanel 0.
Application 2:
Button is clicked and edit box <> "" -> Send text Edittext$( "Edit Box" ) and loop peer on channel.
You're sure that crashes the server and not the client?
Don't you think that the process wasn't successful until the name changed condition is triggered? For all you know you could be saying "I did it!" moments before the server tells you that name could not be set.Quote:
Originally Posted by QS
Yes, you can check it by yourself...
[Problem signature]:
[Problem Event Name]: APPCRASH
[Application Name]: LacewingServer.exe
[Version of application]: 0.0.0.0
[[Application Timestamp]: 4bdf1a4d
[The name of the module with an error]: Lacewing.dll
[Version of the module with the error:]: 0.0.0.0
[Timestamp module with an error]: 4bdf1a32
[Exception Code]: c0000005
[Transfer exception]: 0001d157
[OS Version]: 6.1.7600.2.0.0.256.1
[Locale ID]: 1045
[Additional Information 1]: 0a9e
[Additional Information 2]: 0a9e372d3b4ad19135b953a78882e789
[Additional Information 3]: 0a9e
[Additional Information 4]: 0a9e372d3b4ad19135b953a78882e789
i change it to:
Application 1:
On text message from peer on subchannel 0 (sent)-> Set name to Received$( "Lacewing" ).
On name set-> Send text "I successful changed my name" to peer on subchanel 0.
Application 2:
Button is clicked and edit box <> "" -> Send text Edittext$( "Edit Box" ) and loop peer on channel.
Still crash...
@Edit:
When I use lacewing.mfx (build 14) and LacewingServer.exe (build 14) then the crash occurs but when i use Lacewing mfx (build 14) and LacewingSerwer.exe (build 13) then it's works great...
It would be on name changed, wouldn't it?Quote:
Originally Posted by QS
Actually I don't think that matters if it's crashing.
Jamie, I confirmed the server crash. The client is fine, but the server does indeed crash with this simple thing:
Always: Conenct to "localhost" on port 6121
The client does not experiance a crash even after a few minuites, but the server crashes after a second or two. "LacewingServer.exe has encountered a problem and needs to close"
Wait, I ran the test again, and this time the server held up just fine! The client froze this time! Here is the server log until the client froze:
[22:51:18] Client ID 0 connected from 127.0.0.1
[22:51:18] Client ID 0 disconnected
[22:51:18] Client ID 0 connected from 127.0.0.1
[22:51:18] Client ID 1 connected from 127.0.0.1
[22:51:18] Client ID 1 disconnected
[22:51:18] Client ID 0 disconnected
As you can see, the same client conencted twice with different IDs. Apparently this can either cause the server to crash or the client to freeze. :\
Ahh wait, that crash. It's already fixed in build 15 (which isn't released yet, if you're wondering..)
Quote:
Originally Posted by Jamie
Yes and I can't change peer name when I use server build 14. so I must use server build 13.