- Apr 26, 2019
- 2
- 1
By design. She gained confidence from her fighting experience and she's still disobedient.I found a problem, after a colosseum fight this slave: was able to refuse a collar and a nipple chain she had since a few days here's the before/after:
Yes and yes.If lactation is green S+, does that mean it cannot be increased any further? Is it possible to achieve green S+ lactation without perfect inputs?
That's very strange. The engine doesn't do anything on the network at all to my knowledge. Before I dive into investigating this, could you try with the latest development build? I just recompiled the engine the other day and it would be helpful to know if you experience issues with the current version.Hi, guys.I have a problem. Recently, I have been experiencing a sudden increase in short time lag when playing multiplayer games. Today, through the delay monitoring software, I found that once I opened jack-o-nine-tails-v2-2-3, the local network lag would rise to 999+ and then fall back to normal every 5 seconds.
edit:I test the whole game file,qsp ok,many file ok and last
the engine folder
and as i copy-psate another"FastQSP"in it and play,there is no lag
So,I hope someone could answer my questions and ask if the engine folder that comes with the game itself is OK
edit:testedmy old game file:
1.75:fine
2.1: fine
2.2&2.2.3: lag 999 occur about almost every five seconds
Thanks for your prompt reply, I will start testing immediately (I learned from the traffic monitoring software that jack.exe does not seem to use any traffic, and I am also very curious about how it affects my network latency).That's very strange. The engine doesn't do anything on the network at all to my knowledge. Before I dive into investigating this, could you try with the latest development build? I just recompiled the engine the other day and it would be helpful to know if you experience issues with the current version.
Direct link to latest dev version:You must be registered to see the links
From 2019 it shouldn't have this problem if 2.1 was fineSeems like all the engine builds we have in our current repository (going back to 2019) exhibit this behavior.
That's because what I used is not the "original" source code of the engine. I never found that. So I used something someone else had as my starting line.Seems like all the engine builds we have in our current repository (going back to 2019) exhibit this behavior. Confirmed the old engine from 1.2.1 doesn't. I actually no longer have the engine from 1.7.5 on my machine but I'll take your word for it. Anyway, since I don't have the engine source code from 1.7.5, I'm not sure what changed. Lokplart, do you have the older engine source code?
The only reference I see to the network is the QT Network module which is referenced to set up the webView network access manager (the engine code we have implements a local proxy for this). This gets called whenever we display any images since they have to be loaded from disk. But I see the process spamming network registry queries even if the local proxy isn't being exercised (before a qsp file is even loaded) so I'm guessing the QT network module is spinning around simply because it got loaded. Maybe if we upgrade to a newer version of QT it would behave better, not sure if that's viable. Or we need to dig into QT and figure out how to calm it down.That's because what I used is not the "original" source code of the engine. I never found that. So I used something someone else had as my starting line.
I think it was this repo:You must be registered to see the links
I definitely didn't add any network code so if there is any, it should be in here.
Quite a lot of the functions and libraries used in the engine now are deprecated in newer versions. Which is also the reason why I point to that specific version of QT and why I have that last part in the tips.The only reference I see to the network is the QT Network module which is referenced to set up the webView network access manager (the engine code we have implements a local proxy for this). This gets called whenever we display any images since they have to be loaded from disk. But I see the process spamming network registry queries even if the local proxy isn't being exercised (before a qsp file is even loaded) so I'm guessing the QT network module is spinning around simply because it got loaded. Maybe if we upgrade to a newer version of QT it would behave better, not sure if that's viable. Or we need to dig into QT and figure out how to calm it down.
It's on the top left of the window.Is there a way to save in this game? It's greyed out to me.