#Can't Join or Host R2B4 (work around created, since replaced Computer)

1 messages · Page 1 of 1 (latest)

gloomy shuttle
#

When I'm host, all clients are booted to main menu during loading.
When I'm Client, I get stuck in a infinite loading screen on myside, on every one else's screen I have disconnected, including hot joining

This only happens with R2B4, No other missions have gave me this problem. I have properly been able to play other missions since first encountering this issue

The Issue as I understand it right now :

Issues found with the Checksum while entering the level

After some testing and comparing the logs of the failed checksums, we found that under the XXHASH section, my hosting would get a different LateGeomorphScan number then client, and the same deal if I was client (I would have a different number as host)

As of now I Believe the issue is caused by AMD FX 83 Series CPUs, they may be mishandling a calculation during the generation of the level, which would cause a difference in the checksum

additionally, 2 people using the same series of the offending CPU can join each other, which for a checksum error is extremely odd

Notes:
Not Using a VPN
I'm using a ethernet cable
Using a different computer on the same network works

Things I already tried:
Restarting GTFO
Verifying game files
Reinstalling GTFO
Joining a new lobby
Hosting a new lobby
Restarting steam
Trying to join with different people
Updating my GPU drivers
Restarting my computer
Loading the level first in single player, then trying to join a multiplayer match
Deleting %APPDATA%..\LocalLow\10 Chambers Collective\GTFO
Turning off my firewall
Shutting down Malwarebytes anti-virus
sfc /scannow
Using Regedit to nuke GTFO from the registry, and then nuking appdate files and then reinstalling
Nuked Modman
joining a different level with a fog Turbine and Disinfect station (joining R2C2 plus R2D1 worked)
plugging in a controller (we found something in logs)
Resyncing Windows clock
Making sure Steam reinstalls the entire game

violet canopy
#

Try deleting the GTFO Folder in %APPDATA%..\LocalLow\10 Chambers Collective

#

When you did that, open the game again and it will create a new gtfo folder, then try to join

gloomy shuttle
violet canopy
#

Yeah, your config is saved there. You can rename the folder to something like GTFO.bak and first see if that allows you to join

#

If it does, either redo your keybinds or try replacing the files

gloomy shuttle
#

alright

violet canopy
#

Hmm... if it's only this one level only thing I can think of that you can try is reinstalling the game

#

Verifying game files fixes most problems, not all. Some can only be fixed by a complete reinstall

gloomy shuttle
#

I did already reinstall the game

violet canopy
#

Oh.

#

Ah, missed that in you list

gloomy shuttle
#

all good

violet canopy
#

You're not using a vpn or anything else I assume

gloomy shuttle
#

I am not using a VPN

#

Can't Join or Host R2B4 (Not solved)

violet canopy
#

Looked if someone else had this problem in the steam forums but nope

gloomy shuttle
#

I do know of someone else

violet canopy
#

Exact same as you?

gloomy shuttle
#

Preelexo

violet canopy
#

I see.

#

So if you join a lobby set to R2B4 it won't even load the lobby?

gloomy shuttle
#

the lobby loads

#

dropping down into the mission is when the connection issues happen

violet canopy
#

At the start or when it should give you the mission briefing?

gloomy shuttle
#

during the cage drop

#

after a little bit

#

past the skippable intro

violet canopy
#

Hmm... sorry then I am out of ideas for now, if I remember some other stuff I'll let you know but I'm also stumped rn

gloomy shuttle
#

alright, thank you for the suggestion

#

you know of anyone else that can help?

violet canopy
#

Sadly not, wasn't that often in technical support as there was a lot of chaos because it was unstructured but I gave it a shot since it's in forums now so I don't know anyone directly who was active in the channels

#

I think someone might reply with a suggestion over time

gloomy shuttle
#

kk

gloomy shuttle
#

Turning off my firewall or killing malwarebytes didn't help

#

hey @jade finch, got any ideas?

jade finch
#

absolutely no ideas

gloomy shuttle
#

Rough

high falcon
#

I don't know for sure if this will help, but you could always try booting in safe mode and trying to run the game then

#

Might take some finagling, but since it seems like a very localized issue to a couple people, there could be some background program conflicting with netcode specific to the level

violet canopy
#

Windows won't load the GPU drivers in safe mode

#

Also drivers like directx or net framework will probably not work as they are not supposed to run in safe mode

gloomy shuttle
#

the issue is I'm not running any notable programs outside of Discord, steam and GTFO itself

#

and firefox

#

if it was firefox or Discord, I think we would have way more people bringing it up

high falcon
#

Hence it might be a background program

gloomy shuttle
#

I looked over

high falcon
#

Maybe a hardware monitor or something of the like
I'm just spitballing here, honestly no clue if it could be the offender

gloomy shuttle
#

what you mean by hardware monitor

#

Like Kiryu said, safe mode would mean all sorts of things would not work, I think it would be harder to make the game run under those conditions

#

I just asked the Community manager what game logs could be helpful to us

#

we'll see if we get a response

high falcon
#

Fair, game logs will likely give the answer

fiery grotto
#

Usually logs have the name of the player with date

Unity logs have the name player and player prev and are stored for 2 sessions

gloomy shuttle
#

@fiery grotto I can't upload the log here

#

no permissions

fiery grotto
#

Agh

gloomy shuttle
#

I can DM if that's ok

fiery grotto
#

Sure

gloomy shuttle
#

found something

#

"Kick player! Reason : Kick_GenerationChecksum PlayerSummary : Steam Bread Session summary > Slave GeneratingLevelDone 1 1 792484422 10875050295949054474 Profile summary > Bread : end MasterSummary : Steam Fixalated Session summary > Master GeneratingLevelDone 0 0 792484422 10875050298741346826 Profile summary > Fixalated : end"

#

"19:20:34.018 - Writing logfile to disk: C:/Users/Nicholas/AppData/LocalLow/10 Chambers Collective/GTFO\Seed_debugger_Fixalated_2022-08-12--14-20-34_GenerationChecksumFail.txt"

#

something about a GenerationChecksumFail

#

Bread was someone I was testing stuff with

#

this error is what is causing me issues

#

@fiery grotto

gloomy shuttle
#

Going to sleep. Will not be able to respond for a while

gloomy shuttle
#

awake

gloomy shuttle
#

I have done the temporary solution of clearing the level with bots

#

but I would like to be able to play with friends on it in the future

violet canopy
#

Yeah, understandable. Maybe it'll get fixed with the next hotfix but still, good luck

gloomy shuttle
#

Error found with LateGeomorphScan

fiery grotto
#

If you compare both Seed Debugger Logs - It should fail at LateGeomorphScan

gloomy shuttle
#

Main post updated

#

Can't Join or Host R2B4 (Possible Issue found, Not fixed)

violet canopy
#

Thought of something else that might be worth trying. Go to your main steam folder and select everything except for "steamapps", "userdata" and "steam.exe" and move them somewhere else while testing. Run steam.exe and it'll download all files again. Then try again.

#

It could be a problem with a steam connection manager file. Was just something that came to mind again that you could try, but well, it's kind of an odd method but who knows.

gloomy shuttle
#

I'll double tap the steam install then

gloomy shuttle
#

nope

near fog
#

I am not sure I might have a similar issue. Cant join/host in the same way that OP described.

#

22:45:25.888 - Writing logfile to disk: C:/Users/LemaBau/AppData/LocalLow/10 Chambers Collective/GTFO\Seed_debugger_LemaBau #Low_2022-11-12--23-45-25_GenerationChecksumFail.txt
22:45:25.890 - WARNING! : I was kicked from sessionHub because Kick_GenerationChecksum! 😦

gloomy shuttle
#

@near fog tomorrow can we test something

#

It's R2B4 yeah?

near fog
#

I mean the level is quite easy so I just soloed with bots but not being able to play it with friends still kinda sucks

gloomy shuttle
#

@near fog I want to see if we could join each other

#

to see if the error is making a consistent seed change

near fog
#

sure lets try that

gloomy shuttle
#

I'll get a lobby up soon

#

109775245211043859

#

@near fog

near fog
#

turns out we have basically the same processor FX 8320 and FX 8350 which could be part of the problem

foggy spear
#

A processor should have nothing to do with that

gloomy shuttle
#

Can't Join or Host R2B4 (Possible Issue found, Not fixed) (MACHINES USING FX 83 CPUs NEEDED)

foggy spear
#

it's obviously a networking issue

gloomy shuttle
#

it's the only link

#

it's a failed Generationcheck sum

#

rn leading theory is a rounding error during level gen

foggy spear
#

hmm, I think I've seen that checksum error before

gloomy shuttle
#

If your using a FX 83 series CPU, please say so in this post. We would like to know if you can connect to R2B4 with people with this issue

#

the issue is when failed checksums happens

#

they usually fail in different ways

#

two failed checksums almost always never the same

#

expect for the fact in this case they are

#

they both failed in the same way

#

thus the machines with the issue were able to join each other

foggy spear
#

afaik, generation checksum errors will pop up if your game files differ from the ones the host have

#

The only things I can think to fix that in terms of the vanilla game are verifying the game files, or reinstalling the game

#

it would be extremely weird that you two have corrupted, working files though

gloomy shuttle
#

look at my post

#

I tried all of that and more

#

we are both generating the level in the wrong way in the same way

#

this is extremely weird

#

@jade finch what CPU do you have

gloomy shuttle
violet canopy
#

So, so far inly people that habe an AMD CPU have this issue?

#

Or rather, AMD FX CPUs

gloomy shuttle
#

specifically AMD FX 83 series

#

that and only the people that stated their CPU

#

so far

swift pecan
#

Someone in my lobby has the exact same issue with AMD FX 63 series

#

@prime vortex

gloomy shuttle
#

2nd case I have seen this happen with FX 63 series

#

@swift pecan Thank you for the report

swift pecan
#

Hope this helps clear some stuff as this issue is reproducible on other setups

(We then played another map and had no such problems, so I guess r2b4 truly is special)

gloomy shuttle
#

1st case I have seen it for prosperity

#

the way b4 generates causes something to be different on select CPUs

#

and since a check is made to make sure everything is the same, the check fails

#

which cause clients not matching host to be booted

#

if you can get JeGERdiah to join a match with me later, I would like to test connection with me and them

#

I was able to join someone with the same issue which is super weird for a checksum fail

#

but they had the same series CPU

#

I have a FX 83 Series

#

Can't Join or Host R2B4 (Possible Issue found, Not fixed) (MACHINES USING FX 83 & 63 CPUs NEEDED)

empty delta
#

Hello, I have also run into this same issue with the FX 83 series

gloomy shuttle
#

Thank you for the report

#

At some point do you want to test something @empty delta ?

#

Just want to see if can recreate 2 machines with the bug joining each other

empty delta
gloomy shuttle
#

All good

empty delta
#

@gloomy shuttle Hiya , I'm basically free from now for the rest of the day so lemme know when you want to test things sha

fallen owl
#

I'd like to contribute to this sector being buggy! My team isn't able to launch into R2B4 despite changing hosts and restarting clients/computers. Our issue is different in that we can't even reach a loading screen; whenever we all ready up, we cannot completely press the drop button (stuck at %93)

gloomy shuttle
#

Verify files

#

See if it persist

#

@empty delta sorry for taking a while to get back to you, I am ready for a test

#

do you just want to test connection or do you need R2B4 completion?

empty delta
gloomy shuttle
#

another case of 2 people with the same CPU series generating the same incorrect Checksum

gloomy shuttle
#

I will no longer be able to do tests for this issue, I'm Replacing my current rig

#

however I suspect no more would be needed, the fact we found a consistent way of 2 machine generating the same faulty Checksum on 2 different tests should be pretty telling

swift pecan
#

Has a dev reacted to this?

fiery grotto
#

I've taken it up, can't share more.

stuck rapids
#

Having same problem, FX 8350 here.

gloomy shuttle
#

that Tracks, thank you for sharing

prime apex
#

I've got the FX 8350 as well, same issue.

#

Good to know I'm not alone, just isolated that it was the mission and nothing else last night.

swift pecan
#

There's been an update apparently, does it fix the issue? @prime apex

prime apex
#

Was there a patch today?

#

I played last night and it was still happening.

swift pecan
#

Plus I don't have an FX83 anyway to test it xgxltxttl

prime apex
#

I don't see it, but I'll check when I get home!

gloomy shuttle
#

I saw nothing about a new update

#

you sure it happened? not steam sync files or whatever?

prime apex
#

Definitely no patch on my end.

#

I did the mission solo with bots... 😅

trail knot
#

a joke made by someone

#

those like 'r3 comes tomorrow'

swift pecan
#

........

#

I see

rain belfry
#

@sharp bay

sharp bay
#

@rain belfry thanks

swift pecan
#

Oh well it's coming this week

low spade
#

Still having this issue with another player. Both of us have AMD processors. Mine is Ryzen 5 5600X, and his is RX 6300. I can load in with other players but he always gets kicked. When he hosts I get kicked.

gloomy shuttle
#

3rd case on rx 63

tame tapir
#

Yeah I’ve experienced this yesterday

#

Whenever I host R2B4 I always get in but my teammates get kicked out and can’t join back in

#

One of my teammates tried hosting the lobby and we all couldn’t get in

#

When I left they managed to start it and get into the area

#

I tried to join but it wouldn’t let me

#

I do have AMD processor as well

tame tapir
#

Since this is a problem multiple users are experiencing, hopefully the devs would find this thread and possibly make a solution?

gloomy shuttle
#

Check device manager @tame tapir

#

Please tell us exactly which CPU you have

tame tapir
#

@gloomy shuttle AMD Radeon R9 200 Series

gloomy shuttle
#

@tame tapir uh that's a GPU

#

I need the CPU

#

click on that

#

tell me what it says

tame tapir
#

AMD FX(tm)-6300 Six-core processor @gloomy shuttle

gloomy shuttle
#

thanks for sharing

#

sadly 10 Chambers needs to deploy a fix for it to be solved

#

or you need a new CPU, which is far from ideal

zinc cloak
#

same issue with FX 6300 here

swift pecan
#

Tfw contacting amd for a fix would probably be more reactivate that the devs

feral agate
#

I have this exact problem and i have no idea whats causing it

#

AMD FX(tm) 6350 six core processor here. but seem to ba able to play other levels fine, its just R2B4

gloomy shuttle
#

Read above

#

@feral agate the issue needs to be fixed by the devs, or you need a CPU that does not encounter this issue

swift pecan
#

Did anyone fill out a bug report?

#

I can fill it

#

GTFOPUB-8784

gloomy shuttle
#

I made sure that 10 chambers knew about the problem

#

But I see no harm about filling in that

lime terrace
#

Have you checked Mobo bios?

rain belfry
#

Because its so low risk.

gloomy shuttle
#

specifically the AMD FX 83 and 63 series

lime terrace
#

I have had Bios updates that increase efficiency and temperatures on a CPU. The two devices work hand in hand. The CPUs have been out since 2012. Who knows the last time you've done a Bios update.
Couldn't hurt 🤷🏼‍♂️

gloomy shuttle
#

This will not fix the issue, the only ways I can see how this issue is fixed is if ten chambers fixes the issue on their end or the effected people change their CPU to one that does not have this issue

random estuary
#

Experiencing this too with an AMD FX 8370

#

Precisely it was caused in the generation of LateGeomorphScan

gloomy shuttle
#

Yep

hollow vessel
#

It is absurd that a Dev hasn't even addressed this post yet given so much has been investigated and made evidently clear.

gloomy shuttle
#

I imagine because I brought it to them

#

And considering the issue, the lack of new info from them is likely because they have not found any solutions

#

It's likely base instructions on very specific CPUs having oddities causing a rounding error

#

I was warned a while ago a solution might not be found

#

The devs know

#

And sadly it might end at that if they have no luck fixing it

hollow vessel
#

Right, but at least submitting a response to show acknowledgement would be a good start.

bold quest
#

I'm having this same issue with multiple modded levels and now with some alt/R levels, I also have the FX8350, Im glad someone has finally figured out what could be the problem

fickle compass
#

anyone else getting "no network connection" error on start up?
Also getting a steam cloud sync error for some reason

gloomy shuttle
#

Not related, go to a relevant thread or start a new one @fickle compass

gray sandal
#

Hey me and some friends have gotten back into GTFO after a really long time and one of my friends ran into this issue, everything that has been mentioned tracks, he has an FX 83 series CPU as well, we prefer doing stuff together in terms of GTFO so I'm trying to look into potential options that haven't been mentioned (if they have been mentioned already I really do apologize) but somethings that I can think of:

Running GTFO as an admin
updating the processor drivers or reinstalling them

There is a potential theory I have but I don't know what the fix would be which is:

Potentially a driver installation required in the FX 83 and 63 CPU's are "defensive" in that they're refusing to load something

#

If I can have my friend test some things whenever he gets the time I will but wanted to throw out somethings here to hopefully get a fix for everyone soon

gloomy shuttle
#

No testing with drivers has taken place but I doubt it will solve the issue

#

As far as I'm aware, we have zero examples of the CPU generating the level correctly

#

And I can think of at least 4 examples from 4 separate fx 83 series cpus

#

On top of my head

#

You are welcome to try, knowing for sure if drivers will or will not solve the issue is useful info to have

gray sandal
#

Yeah if my friend gets the time I'll test it with him

gloomy shuttle
#

Realistically thou, you might want to look into alternative means

#

Such as your buddy using a different comp

#

Or regrettably replacing the CPU

#

The devs might fix it

#

But no means 100% going to happen

#

I wish I had a good answer for you, best of luck with the driver experiments

gray sandal
#

tyty will update if I find anything

swift pecan
#

That would be rad if it was "just" a CPU microcode problem

gray sandal
#

Update tried it unfortuantly didn't work I also tried having my friend run GTFO with -USEALLAVAILABLECORES command and run as admin and still nothing same error happens

gloomy shuttle
#

Thank you for checking at least

#

If you want to do the level together, you have some options, none of them great

#

If your buddy has a different CPU or machine he can use to play the level, that would work

#

And for some reason you have the same CPU laying around, that would also work

#

2 people with the offending CPUs can join each other, at least with the fx 83 series

#

Sadly the only other option is skipping the level for the time being

#

Whatever you do, best of luck

gray sandal
#

gotcha tyty

opal tapir
#

Have any of the affected machines been overclocked?
And did anybody try increasing the voltage?
Those old AMD CPUs sometimes need a little more voltage to be stable
You can also try increasing the memory voltage slightly

#

also, anything useful in event viewer when this happens, like kernal errors?

gloomy shuttle
#

When I had that computer, I didn't encounter any similar issues with anything else with my ~8-9 years of using it

#

@opal tapir this leads me to doubt anything would change if the over clocks happened, but if someone is willing and able, it should be tested

#

I have since parted out that computer

tight minnow
#

i believe the same issue has happened to me for R6D3(not host), loading into the level then suddenly back to lobby screen, my cpu is amd fx 8120

opaque folio
gloomy shuttle
#

Isn't most or all of R1 storage?

#

None of those levels had the issue

opaque folio
#

But I mean, it doesn't change that r2b4,r4a2,r6d3 are all storage (r6d3 I think it's storage,dig site, refinery same for r4a2)

gloomy shuttle
#

yeah

opaque folio
#

I'm not saying that's the case, just a coincidence that I wanted to point out

gloomy shuttle
#

possibly a specific room?

vernal fossil
#

Bit of a strange version of this issue, but we're having the same issue with R2B4 on an M2 Pro Macbook running the game via Apple's game porting toolkit (an x86 DX11 to ARM Metal translation layer)
all the other levels load fine, just like everyone else

#

It's not running on a supported platform, granted, but it's definitely a "you have a wierdo CPU" bug

#

given every other level we've tried from R1 to R7 has run fine through the translation layer on the unsupported platform

#

Unfortunately having read through the various threads about this bug it'll probably never be fixed

gloomy shuttle
#

That's new

#

Thank you for sharing

west vault
#

We've been getting the same issue with R2B4, R4A2, and R4C3. No FX8 series for us, I have an intel and my partner has a FX6300

#

frustrating to have to skip those levels for sure

fiery grotto
gloomy shuttle
#

FX6300 is best to my knowledge affected in a very similar way to FX8300

#

I restrained myself to say affected in the same way since we have not tested if a user using Fx6300 can connect to another user with a fx6300

#

On that note, I am curious if a user with a fx6300 can connect to a user with a fx8300

gloomy shuttle
opaque folio
#

I think R3C1 also has that issue but I could be wrong, again, interesting to notice that those are all "Storage" environment levels (precisely, R4A2 is storage/dig site/refinery and R4C3 is storage/dig site)

gloomy shuttle
#

Does all levels we know for sure has the issue storage/digsite

#

Or does one of the levels not have dig site

opaque folio
#

R2B4 is only storage I'm pretty sure

gloomy shuttle
#

Yeah that's right

opaque folio
#

On the other hand most R1 levels are storage and they dont have the same issue, R1A1, R1B1, R1C2

gloomy shuttle
#

That hallway leading to the 2 possible turbine sites is storage?

#

The tube hallway

west vault
opaque folio
robust pumice
#

So are people with an 8320 or fx series CPU just condemned to either solo the level with bots or change their CPU? Cause there's at least one or multiple levels for every rundown apart from R1 and I believe R3 that can't load

fallen haven
#

Same issue happend to me. Starting playing with friends. But this got us. They can continiue, me solo/ find people here D:

Mine are - AMD FX(tm)-6300 Six-Core Processor 3.50 GHz

desert sigil
#

You and the guy above (or anyone else with an AMD FX processor) can play these levels together I think. Otherwise you'll have to complete them yourself. Comprehensive list is: R2B4 R4A2 R4C3 R5D1 R8E2

robust pumice
#

I believe i read above thst two people with an fx series tried togheter and it didnt work no?

desert sigil
#

Two people with the exact same CPU can play the level together iirc. I'm not sure if different AMD FXs can, however.

fallen haven
#

So, have time tested with friend

Me host. Friend send into menu....

Friend with Intel(R) Core(TM) i5-9500F CPU @ 3.00GHz 3.00 GHz

#

Other friend have Ryzen 5 5600 and he was kicked in menu too

#

Maybe trouble in something different?

opaque folio
gloomy shuttle
#

The issue is those CPUs are generating a different check sum

#

As a rule, client that don't match the host's check sum gets kicked

gloomy shuttle
#

Can't Join or Host R2B4 (Unfixed, some closing details needed)

#

With the wrap up of GTFO's dev cycle and the fact this bug is likely never going to be fixed, I'm going to gather up some details about this bug and post it anywhere where people could look to see what could be causing them this issue. That way in the future if people encounter this bug, they can hopefully easily get answers, as grim as those answers are.

#

one thing I don't know off the top of my head is a exhaustive list of what levels are effected

#

If someone can provide them, that will be extremely helpful.

#

R2B4, R4A2, and R4C3 are the levels I know that are having this issue

#

but idk if other levels past that are effected

#

the PC I had this issue with originally was parted out quite awhile ago, so I can't test this myself

#

if you have a FX 6300 series or a FX 8300 series, you have this issue

desert sigil
opaque folio
#

R2B4 IIRC is strictly Storage and also the only one that is just storage

#

On the other hand I think R5D1 has very few zones that are storage

gloomy shuttle
gloomy shuttle
#

Can't Join or Host R2B4 (Unfixed, since replaced Computer)

swift pecan
#

Holy shit R8E2? Oh

spiral bough
#

Hi, Is there anyone here who has an FX 6300 series or a FX 8300 series processor?

robust pumice
#

Comprehensive list is: R2B4 R4A2 R4C3 R5D1 R8E2 R6D3 aswell

opaque folio
#

Only thing I can think about is that all of them have storage tiles

swift pecan
#

Apparently 10C closed their public Jira board? (asking @torn ocean cause maybe you know why?) so I have no idea if they ever answered the ticket I made (GTFOPUB-8784)

torn ocean
swift pecan
#

Aww, absolutely missed it. Tyty

opaque cargo
gloomy shuttle
#

Thank you for Sharing this, I'm going to go update some posts

robust pumice
#

yo andocas

#

you're insane

robust pumice
#

you're insanely goated

opaque cargo
gloomy shuttle
#

Can't Join or Host R2B4 (work around created, since replaced Computer)

swift pecan
#

Common Andocas W

gloomy shuttle
#

@turbid oar can we make this a known issue with a modded patch?

#

It's a known bug where people with certain AMD FX CPUs fail to load levels correctly and thus can't play with anyone that does load the level correctly

#

a example of a level with this issue is R2B4

#

the bug happens with 100% consistency, and the mod is needed to fix it

#

or get a new CPU