http://www.aquadasoft.com/LacewingBanner.gif
Happy new year!
Server, C++ library, extension
OINC MFA -> Lacewing patcher
Printable View
Awesome... If ICMP Ping is fixed then I can continue work on my project. Thanks for your hard work.
Just tested ICMP Ping, still locks up the application. :(
I think only UDP is fixed in this one. New build soon to address any other remaining issues.
Yay finally a new build! Thank you very much :)
I use ICMP Ping to detect when players are lagging / approaching disconnect. If a message is not received when it should be, the program pings the server, if it gets no reply, it displays 'you have disconnected'.
Can you suggest a work around until this is fixed? I waited patiently in hope this would be fixed in BETA #6. I'd like to avoid delaying my project for another month.
You can't rely on servers to respond to ICMP ping.. most routers drop it by default to block denial of service attacks. Couldn't you just use "On disconnect"?
"On Disconnect" doesn't work if the person physically disables their internet, ie. in the case of disconnection without closing the application first. The game will assume the person is still active and keep sending and expecting data.
I'm sure I'll come up with a work-around, maybe have the player send a message to their own username, and set up a counter to time the response. Thanks anyway.
This Lacewing (working on UDP) still crashing ;/
I'm guessing Web Interface isn't working yet?
If you want a packet that does nothing (and should make it realise the connection has been severed) try sending an empty server message. The Lacewing protocol does actually have a ping/pong mechanism, but it's not implemented in the extension. I'll see about doing that in a future build :)Quote:
Originally Posted by Ryan
Not as far as I know, but that's a non-essential feature.Quote:
Originally Posted by Crazy_Ivan
Thanks, that helps so much with debugging. How is it crashing? When? Why? Do you have an example?Quote:
Originally Posted by BoYY
Thanks your work, Jamie and AquadaSoft developers!
Yay! A new build! :D
*Downloads while yelling in delight*
Stephen1980
pylacewing supports pinging, actually :grin: Just set 'ping' to True in the ServerFactory, and it'll send pings automatically :)Quote:
Originally Posted by Ryan
I should probably post the bugs I found, right? :P
"On name changed" doesn't work.
Stack messages don't work.
Sometimes, when I close client 1, client 2 might crash.
Peer looping doesn't work.
Application crash when I restart application and close first client (second crash).
Hmm, I think there's some stack corruption somewhere causing erratic behaviour. I'll check it out.
Crashes when trying to start a server within mmf. Also crashes when trying to connect to the exe server using localhost
Bugs I found:
-Peer_PreviousName$( "Lacewing" ) doesn't seem to return anything, after a peer changes a name.
-On name changed doesn't trigger.
Most functions seem to work though :)
I don't seem to be getting UDP stack bugs...
I haven't come across any bugs yet, but I'll keep looking.
Ch33r5 J4m13!!!111!
I'm sorry. I had to. This is my 1337 post.
When attempted to run the movement example found here:
http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Number=128853#Post1288 53
I ran the server, I connected just fine to localhost for one application. I ran another application to try and connect two clients to the server and several seconds after I move in the second client, the first one crashes and spits out this error:
http://www.konidias.com/lacewingerror.png
Is it because I'm trying to run multiple clients on one machine? Seems like whichever application is receiving the movement data is the one that crashes. The application that currently has focus (the one I'm moving around in) doesn't crash.
I'm behind a firewall but I really don't think it has anything to do with it. I disable it and nothing changes.
Yeah, we've had quite a few problems with MFAs converted from OINC to Lacewing. I guess the IDs or parameters aren't exactly the same (I did my best, but it was all an educated guess really).
Are there any examples for Lacewing like there are for OINC? (simple chat/players moving around/lobby)
If it would help users, I could make a few Lacewing examples and share them. :)
Stephen1980
YESSSSSSSSSSS!
Hi. Sorry to bring this up again, but I've recently released a beta of my game utilizing lacewing instead of moo. And I've gotten reports from 3 people that the game crashes on the same event I reported before - when you receive a couple (or a lot) of messages at the same time. It freezes and/or crashes. And this makes the game (or any lacewing game/app for that matter) unplayable.
I don't have this bug anymore since I formatted my computer. There is definitely something wrong, but it's not an easy reproducible bug, since it involves some kind of compatibility issue. From one of my betatesters, this is the message from the error window
AppName: lacewingtest.exe AppVer: 3.0.249.0 ModName: msvcrt.dll
ModVer: 7.0.2600.2180 Offset: 0001a573
(I got this too, but I can't produce the bug anymore)
Since now it seems that people other than me encountered this bug, I'm pretty sure there are more people that (will) have this issue :/
Yeah, it's been a persistant problem since the early days of OINC (albeit with reducing frequency). Once I can reproduce it here with a debug build I'll be able to fix it, but until then I'm pretty much stuck.
I have found a bug in the server that will be fixed in the next beta. There may be some fixes in the client too.