I know that P5 want's to make connection to the internet. The use of that I do not know.

But now I was going through the logs of my firewall and I
noticed that it is not 1 attempt to connect: the longer P5
is active, the more attempts there are to connect?
I see counts in my log of 600 attempts but also 9.820
attempts to connect!!? And this in only 1 P5 session!
I allready did block this useless outgoing traffic .... but is there a way to stop this weird behaviour?
I allready did apply the "posershell.xml" trick to stop the ContentRoom.
I know the connections are directed to nothing: IP
number what is trying to be reached is 80.255.255.255, which is a combi of my own IP number and the default gateway.
Really would like to stop this because when it makes that many attempts, wasting CPU time to block it with firewall is no solution, and may even slow the computer down more.

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=1444282

Thanx Layingback ... but no luck .... did all that is described there, inluding the little prog ... but I just had P5 running for 1 minute and 382 attempts of contact were made.

Ah, to stop it... Only way is go grab a disassembler and start digging in the code to find the call. Very hard, esp. as this is a ported Mac app. Pro'ly falls under the d**n DMCA too, as it's to prevent potential infringement of the license.

Yep, stopping it: P5 can be hungry on CPU and Windows sees all this as regular network traffic and is assinging also CPU to it ... as does (in my case) ZoneAlarm. Ah well, it's not the 1ste time software has a totally useless thing it.

If you want to get a measure of the wastage, use the trick that's used in video editing - disable the Network Interface to your Internet connection temporarily. Time a render before and after, and see if the savings are worth disabling NI every time. Watch for caching effects though. You'd really need to run Poser from a fresh reboot each time, and do exactly the same steps - as Windows and Poser cache everything they can to save load times.

I think what he's saying is that even if you disable TCP/IP or unplug your ethernet cable, Poser is still going to waste CPU cycles. From what I heard, the OS X version doesn't do this, but nobody with P5X is answering that question yet.

What Mateo Sancarlos is saying is correct. I am from The Netherlands so maybey I was not clear here :o) It is all Poser that is doing this, not TCP/IP or Windows or whatever: P5 just keeps on trying to connect. Did a quick test and it comes down to around 3 attempts per second to connect.

I think you'll find if you disable your network access entirely at the OS level, then Poser will not attempt to access the net, and your performance loss - whatever it is - related to multiple-copy testing will be restored. But remember to keep Zonealarm running to correctly analyse Poser's contributory role in this - as ZA is a pretty heavy resource hog. (However if all you do is unplug the cable, then of course, Poser will still see a network capability, and attempt to use it.) So I wasn't saying remove the network to reduce the OS resource component, but in order to fool Poser into thinking you have no network connection to check out. But like everything else in Poser, you have to try it to find out what really happens... Either way I was only offering a suggestion to possibly permit the poster to further progress into analysis of an area in which they seemed particularly interested. I'm not interested enough to do the actual analysis for them! I have no other ideas on how else you can persue. Even if OSX doesn't do this what will that tell you? The variation caused by 2 different Poser builds, OS's and even system designs, has to wash out all other findings.

Since it's beyond most of us to rewrite and recompile the main Poser executable file to eliminate its connection attempts, and since it's unreasonable to disable network connectivity just due to this one "Trojan horse", there are two other options of last resort: 1. Wait for Poser 6 and hope it doesn't have a connection subroutine encoded in the main program file. AFAIK it won't, since that idea died when control of Poser transferred to Egisys. 2. Wait for Daz Studio Base. AFAIK it doesn't have a connection subroutine encoded in the main program file, but we have to wait to find out for certain. 3. I would also suggest that Egisys might be willing to replace Windows users' copies with a newer non-connecting installation version for a small fee, say $49.95. This would be a goodwill gesture with a view to increasing future sales of Poser 6.

Well, solved the many connections problem ... simply by allowing P5 to connect. When P5 is not allowed to connect, it comes in a "connection loop" ..... P5 needs to get a positive response from a router or modem and then it stops with connection attempts ..... allowing ZoneAlarm can do no harm since the only connection that is made only goes to the router or modem and not any further ... so lesson learned here: allow P5 to connect and no CPU cycles are wasted. Just 2 attemps are done: 1 at start up of P5 and one at closing P5. The fact that P5 connects to my modem only, doesn't bother me. I have no network nor multiple versions of P5. Thanx all for thinking ... it's interseting to read/learn all this :o)