Elishi

Just now, Cody said:

I wasn't having any issues after the patch, I was one of the first back on and didn't have any issues what so ever until just now...

 

Same for me, didn't have any issues after the patch (other than my lipstick being gone), but now it says I can't connect to server so

Same here, can't connect to server after having stayed on for quite a few hours during the evening/night now

Same here, just type in my details and it says it can't access the server. Guess it crashed again

Well, hopefully sooner than later, seems to be some weird stuff with profiles and xGold happening too so

Yea, same here. Think the rouge is gone as well? At least the effect of it seems lessened on my cheeks

Still been happening to me at least, so pretty sure it's not been fixed.

Welp, spoke too soon, now it disconnected me again *laughs*

Well, I get in after that login queue at least, just that friendslist doesn't load so... yea, it's all just slow and wonky

Yea, it's definitely not very stable again, that's for sure...

1 minute ago, Xizl said:

Discord works fine for me. 

Discord dropped completely on PC for me, was working fine on phone though. But they definitely were having server issues not long ago at least, so might be related or it might not. Makes somewhat sense if both are using Cloudflare though. Discord up again for me now, however, though it shows everyone as offline even though I'm chatting with friends there at the moment.

Yea, got kicked off server just a few minutes ago, get put into a login queue when trying to log back on of about 50-200 people and then instantly disconnect again.

Logging in and then waiting literally 3 minutes on the character select screen before entering any room whatsoever actually got me in without the red disconnect box happening, before that I just got disconnected immediately on login as well.

Just keep getting the red Connection Lost: Reconnect box whenever I log in now too. Doesn't matter which room I go to or whether I go with the US Direct or EU Proxy option... *sighs* So many issues with this update...

Nevermind, doing a full restart of my computer fixed it for some weird reason, bizarre though.

Yea, when I open the app to log in it says there is no internet connection to the server or something, and 3dxchat.com is down with a "Bad gateway" error on the host side.

It worked having done :

clic on the name and hit your email

clic on the password an enter your pasword

clic on the login button

 

Do NOT ujse the key enter

 

not easy to clic on login as myu mouth curser is not visible

This actually worked, so thanks! Such an annoying bug though, can't use tab or enter on login screen. Not that it takes -that- much longer, but just another annoying hassle to go through.

I have never stopped having these crashes either, I just couldn't be arsed to post more of the same type of crash reports as I've done in multiple posts in the past as there was not a SINGLE reply from a dev about any of it. I can't remember the patch number it started happening off the top of my head, but I think I mentioned it in one of the previous posts in the bug thread. If staying in Sin's it takes about 2 hours now for the client to crash out, go to a private room with just a few people and it's perfectly fine. A bug that probably doesn't matter much for a majority of the illiterate shitheads on 3dx really, but for those of us that actually enjoy taking a long time with RP (as in it lasting 2+ hours, which isn't really that long either to be honest) it's a pain.

Nothing will probably happen though as they seem to either need to revert back to an older version of Unity or get to a much newer one. As for what is happening with patch 371 that just came out today, and if the issue still persists there, I cannot say as the game doesn't even let me get past the login screen right now. So, hurrah for bug fixes? The crashes that happen after 2 hours at Sin's also only started after a patch that was said to be bug fixes, so guess fixing bugs means that they're introducing more of them? *shrugs*

Haven't had the same exact issue. It just hangs up on the log in screen for me and wont go any further. Can't figure out why either.

Same thing happens to me, done a full reinstall both from the 369 install and the 371 install. Type in login details and hit the login button and nothing happens other than the login button getting greyed out. Happens with both US Direct and the EU proxy. And, yes, running as administrator on Win 10.

Not that this seems to be even acknowledged by the devs, but client crashing still happening. At least update to a newer version of Unity or something when compiling to try and get rid of this.

2017-09-19_000442.zip

Guess we'll be back up and running in the morning hours EU time then. If the last time is anything to go by at least

Still the same crashes as before, really wish you could fix at least this since it's something that was introduced in the patch that was supposed to give stability fixes.

2017-08-14_125134.zip

Bunch more crash reports since more is probably just better for this kind of stuff. Seem to average 2 or 3 crashes per day or thereabouts.

2017-07-16_222022.zip

2017-07-17_005012.zip

2017-07-17_223928.zip

2017-07-18_005908.zip

2017-07-18_155808.zip

2017-07-19_000714.zip

2017-07-19_132508.zip

2017-07-19_163558.zip

2017-07-20_160332.zip

2017-07-21_133544.zip

2017-07-23_053828.zip

2017-07-23_220558.zip

2017-07-24_000454.zip

2017-07-24_215332.zip

2017-07-25_142436.zip

2017-07-25_221730.zip

2017-07-26_122912.zip

2017-08-02_161414.zip

2017-08-02_212532.zip

If that is the case then the game should definitely be either rolled back to the same engine version as 363 (no idea if that is possible or not), or they should make sure that it's upgraded to a more recent one where this bug/crash doesn't occur.

Definitely not, but that would attest to some coding error, no? That would be the most sudden memory leak I've ever experienced in any program at least if it suddenly decides it needs -that- much out of the blue.

Whatever it is it seems to have been something happening in the 364 patch at least. Don't want to speak for the others it's happening to, but I'm pretty sure we all started getting this exact same crash behavior after that patch, while we never had it in 363 or before.

Well, did anything change between 363 and 364 then? 363 did not have these crashes, but after the 364 patch, the patch that was supposed to bring stability fixes, (and now in 365) these crashes have happened and keep happening.

The fact that my memory usage is at about 1200 MB or so when 3DX crashes seems to indicate a fault in how the game uses the memory rather than a pure memory leak as such though or? I would have assumed a memory leak would cause it to completely run out of memory which would have to make it spike from 1200 MB to past what I have available in an instant so fast I don't see it happening in the task manager in that case.

If they are related to PhysX would that mean that it could be caused by the Nvidia drivers?

Based on the output log this is what seems to happen when it crashes

DynamicHeapAllocator allocation probe 1 failed - Could not get memory for large allocation 2147483648.
DynamicHeapAllocator allocation probe 2 failed - Could not get memory for large allocation 2147483648.
DynamicHeapAllocator allocation probe 3 failed - Could not get memory for large allocation 2147483648.
DynamicHeapAllocator allocation probe 4 failed - Could not get memory for large allocation 2147483648.
DynamicHeapAllocator out of memory - Could not get memory for large allocation 2147483648!
Could not allocate memory: System out of memory!
Trying to allocate: 2147483648B with 16 alignment. MemoryLabel: Physics
Allocation happend at: Line:168 in
Memory overview

[ ALLOC_DEFAULT ] used: 1379971012B | peak: 0B | reserved: 1457855752B
[ ALLOC_TEMP_JOB ] used: 0B | peak: 0B | reserved: 6291456B
[ ALLOC_GFX ] used: 26901048B | peak: 0B | reserved: 37748736B
[ ALLOC_CACHEOBJECTS ] used: 449096B | peak: 0B | reserved: 10485760B
[ ALLOC_TYPETREE ] used: 348104B | peak: 0B | reserved: 4194304B
[ ALLOC_PROFILER ] used: 0B | peak: 0B | reserved: 0B
[ ALLOC_TEMP_THREAD ] used: 32768B | peak: 0B | reserved: 3276800B
Could not allocate memory: System out of memory!
Trying to allocate: 2147483648B with 16 alignment. MemoryLabel: Physics
Allocation happend at: Line:168 in
Memory overview

[ ALLOC_DEFAULT ] used: 1379971012B | peak: 0B | reserved: 1457855752B
[ ALLOC_TEMP_JOB ] used: 0B | peak: 0B | reserved: 6291456B
[ ALLOC_GFX ] used: 26901048B | peak: 0B | reserved: 37748736B
[ ALLOC_CACHEOBJECTS ] used: 449096B | peak: 0B | reserved: 10485760B
[ ALLOC_TYPETREE ] used: 348104B | peak: 0B | reserved: 4194304B
[ ALLOC_PROFILER ] used: 0B | peak: 0B | reserved: 0B
[ ALLOC_TEMP_THREAD ] used: 32768B | peak: 0B | reserved: 3276800B

 
(Filename:  Line: 999)

User allocator returned NULL.
 
(Filename: ..\..\foundation\src\PsFoundation.cpp Line: 240)

Crash!!!

Which seems to be the game having a null pointer access to me.

(Though I have no real knowledge of coding or how Unity works)

Well, it should still show that I actually have some memory installed though, shouldn't it? According to all the crash logs it just says I have 0 physical memory -and- 0 free memory. Based on most of the other Unity game related crash reports I can find it at least seems to recognize that there is some free memory left.

Memory usage in task manager peaks at about 1600 mb for in 3DX, though generally before the crashes it seems to drop to somewhere between 1000 and 1200, so it's not like it's using up all the RAM it has available either. And again, these crashes happening for me at all ONLY started happening after patch 364 which was the supposed stability and bug fix patch, so it seems likely something was introduced during that that causes all of these crashes to happen for me at least.