prpc beta tested needed

[TromNek]

Here's a version of the server daemon that sends a dummy message to itself on startup.

[acanthis]

Here's a version of the server daemon that sends a dummy message to itself on startup.

Hmmmn.  Now that's interesting.  This version doesn't fix the problem, but the version that you posted before, the one that pops up the highly useful connection message, does!!!  btw Confirmed the issue is with the first connection after boot up, not the first connection after Poser start.

I actually like that message. How hard would it be to integrate that into a status bar for the PRPC control panel?  (I wouldn't want to have to keep dismissing a popup dialogue)  I like to know when things are happening, and as we all know, Poser is not the fastest kid on the block

[TromNek]

Here's another debug version. This one pops up the info window after data is completely recieved.
Tell me what it says.

re: status bar
I've been thinking about having various levels of debug/info messages.
A status bar thingy might be perfect. It could display the first 40 chars of a message like:
Info: Connection from IP:127.0.0.1 port 25234, data=c:\Program files\Curiou.....

And include a button that you can click to pull a window with the entire message.

Maybe I'll try and implement this in version 1.35.

[Dizzi]

Here's another debug version. This one pops up the info window after data is completely recieved.
Tell me what it says.

Booted, Started Poser & AL, sent to Poser without PRPC loaded. Loaded PRPC, sent from AL -> Message Size 0 on first try, correct size on 2nd try and it loaded the prop then.

[TromNek]

Ok.
It gets the connection but not the data.
I'll need to think on this.
Gotta go now before the wife kills me.

[TromNek]

Here's another try.
This one will make an extra attempt to read data from the connection if the first attempt returned nothing.
If this doesn't work, I can try to wait a half a second before the second attempt, but I'd rather not
introduce any delays.

Boot, Start Poser, run this script, start AL and send something.

Dizzy and acanthis,
Are you running a firewall on your local machine? If so, try disabling it and testing with the normal server daemon.
If that turns out to be the issue, I still need to find a workaround, but at least I'll know where the problem is comming
from. If so, send me a message (not a post) letting me know whose firewall you use.

[acanthis]

Here's another try.
This one will make an extra attempt to read data from the connection if the first attempt returned nothing.
If this doesn't work, I can try to wait a half a second before the second attempt, but I'd rather not
introduce any delays.

Boot, Start Poser, run this script, start AL and send something.

No change. Is this perhaps an XP thing? Is it doing some kind of sparse resource allocation so that the loopback interface doesn't exist until the first time somebody tries to use it, and then there's a delay while the world's most powerful, performance-tuned operating system grinds into action?

Couldn't you send yourself something on the LO to kick the thing off?

[TromNek]

I tried that with debug02prpcd.... version.

I'll make another version with a delay. It seems like the 4 second window worked
so maybe we'll start with a one second delay.

[TromNek]

Here's on that will introduce a 1 second delay then retry reading the data again.
It should pop up a quick window (the 1 second delay).

It should only introduce the delay if no data was received. Thus you should only
see this message the first time you send something to the server daemon.

[Dizzi]

Did work for me

[acanthis]

Did work for me

Confirmed. That works for me also. On the very first attempt, I briefly see the dialogue "Please Wait. Going to try again" then the object loads. And, as expected, susequent loads work fine.

[TromNek]

OK.
Just but up another (hopefully last) beta with that fix at SourceForge.
I was shooting blind on this problem because I couldn't even simulate that problem fully.
Thanks for the help.

I'll be going on vacation next saturday, so I plan to make a public release after the new year.
Hopefully this will be the end of version 1.34 and I'll start work on 1.34.

Plans for 1.35.

Add logging ability to the server daemon in conjuction with a 'status bar' that displays
the last message (info, warning, error, exception) along with a button that will pull up
a list of the last 100 messages. This way I can get better diagnostics from people who
are having problems or helping me debug stuff.

Clean up the entire code base and isolate Poser specific stuff into a separate class.
This will allow me to use alot of the same code for a similar project for Vue Infinite.
I also want to do this with Shade 8 if e-frontier included tk/tcl in that version.

Begin two way communications with external applications. At least provide a 'ping' that will
return the server daemon version. Possible add some elementary query abilities.

Begin working on network animation rendering. I don't do animations so I'll need some people
who are interested in this to help me.

thanks again

[acanthis]

Thanks. Downloaded and installed (confirmed: it still fixes the first time load problem)

I'll be using this version from now on and will report any problems I find, but so far everything seems to be working.

[TromNek]

Just uploaded the general public release of the project, prpc version 1.34.33 at SourceForge.

I need a Pro Pack tester!

[radstorm]

Can't say I am a beta tester, but I do use Pro Pack

Here is what I get when I run the py script..it runs..scrolls down a bunch of commands..but at the end it displays:

RuntimeError: Maximum recursion depth exceeded.. sooo I dunno.. and when I click a link in AL it asks if the script is running..I assume it looks for it..coz it IDs the script..?