[BUG] - Loading screen not clearing on login.

[RimBlock]

After the players character is created in game world, the loading screen does not close resulting in the player not being able to see anything but being able to move in game and others to interact with them.

What is causing it is unclear as it seems to happen quite randomly to those affected. Thread on it here ->

What I have also noticed is that logging out (back tot he server lobby), editing character data via the backend DB and logging back in to the game does not seem to pick up the edited character data. An example is when my test character was killed, whilst my client was in the server lobby I changed 'alive' in the character_data table to '1' and commited it. On login to the game again, a new character was created (in 1.0.4.2, the old character would be revived).

A server reboot clears the problem untill it reoccurs.

I am speculating the player object is not being correctly cleared up in the game world in some instances but need to debug to try and confirm.

If someone could list the login / logoff script chain then I will have a look and try to debug this as I am getting it pretty consistantly on my test server.

[uro666]

Which version of ArmaOA is this happening on?

I run 1.62.103718 on my public servers and the only time I've had something similar to this was due to an error in my mission file, damn semi-colons! ;)

I can change alive status from 0 to 1 in the DB and it still works on 1.62.103718.

From the forums most people are reporting these issues running 1.63.112555 which everyone knows or should know by now is broken, resulting in multiple and unexpected issues.

As far as I know the Epoch dev's haven't told nor recommended anyone to update to 1.63.112555 as Epoch 1.0.5 - 1.0.5.1 were not tested with it. It is not mentioned in any of the changelogs either.

Epoch 1.0.5.2 will be requiring ArmaOA version 1.63.125548 and is stated as such in the changelog, it is being tested on this ArmaOA version and code is being modified where required before 1.0.5.2 is pushed out.

[KolonelMatt]

I am not certain that it is a problem specific to 1.63.112555. I have encountered this issue on my server while using Epoch 1.0.5 and 1.0.5.1, and on Arma 2 versions of 1.62.103718, 1.63.112555, and one of the 1.63.204xxx patches. In fact, after first encountering the issue I upgraded from 112555 to the 204xxx patch and the problem remained. I then rolled back to 103718 and the problem persisted. Each was with a stock Epoch install, but with my previously working DB from Epoch 1.0.3.1.

The only way I have been able to eliminate it so far seems to be create a fresh DB and install stock Epoch. I have not added any addons since as there does seem to be a higher chance of this issue happening when addons are included and I don't want to re-break my live server and take it offline again. I have, however, had the issue on stock Epoch prior to the DB wipe I did. It seems to be all over the place. I am currently running the latest patch for Arma 2 (125548) and it is working so far, but as I said, stock everything and fresh DB

[RimBlock]

This is on the current stable build on Steam - 1.63.125548 according to my client.

I actually moved over to the stable build last night and deleted all my local content and disabled my antivirus before re-installing. Played for a few hours and didn't get stuck at the loading screen (although the gear auto closing bug appeared again). Need to play more to test it has gone away and to check the antivirus does not do something stupid when it comes back on.

[SilvDev]

Pretty much everyone on my server gets this at some point. I made a fix by detecting when their game had loaded but the loading screen was still open, it waits 10 seconds incase it's just a slow load and then forces them back to lobby. Also players gear will tend to wipe at this point so another fix must be made to prevent saving/wiping inventory just after a player logs in.

[RimBlock]

Really need to find the underlying issue. Since moving back to the stable releases, I have seen it rarely although a new install on a new machine over the weekend got hit badly again but it seems Steam also updated the client as well.

I am suspecting a client / server version missmatch at the moment.

The point about Epoch being validated on an older version of ARMA2 is very valid but if the current version is 1.63.125548 then it should really should be validated to work on that version. I appreciate 1.0.5.2 is on the edge of being released which has been validated on this version but as it is not out yet a lot of people are having this issue.

Not being able to play as you are just getting a black screen on login is pretty much a show stopper from a players point of view.

[SilvDev]

I could post a pull request with the fix I'm using. Is this needed?

[piggd]

The symptoms that have been reported on the forum in 1.0.5.1 patch 125548 is after reloging we get a blank screen and can hear movement. I posted this work around and and it is worked a 100% for my 3 epoch and 5 overpoch servers/

compiles.sqf

        if (dayz_clientPreload && dayz_authed) exitWith { 
            endLoadingScreen;
            diag_log "PLOGIN: Login loop completed!";
   };

[RimBlock]

The only problem with the 'workarounds' is that they leave the underlying issue still there and 'mask' it rather than fixing it.

The only place that seems to have a relevant "endloadingscreen" is in the player_monitor.fsm and so it seems somthing is tripping that up now and then. I may have a look over it this weekend although I have not been having the black screen since moving to the stable ARMA II OA version (rather than the betas) and updating the version on my server to match.

[BigMikeAU]

Has this issue been solved? This is THE major issue for my servers, and have been for many weeks. It happens consistently on all log ins. After a server restart, you can get in for a few minutes, but any logins after that get this issue. Basically, you are spawned and playing, but the loading screen is displayed instead of the game.

[RimBlock]

I had this issue a lot until I moved off the Beta branch and back to the stable builds. I also had to keep the server version and build in sync with the client releases. Build patches sometimes come out with little or no fanfare unless you actively scan the BIS forums.

Keeping the code synced removed the issues for me.

Of course this also needs the player's to keep their clients synced as well.

[ian76g]

I have this problem every time. Server admin has to kill me ingame - I use taskmanager to kill the game and then join again with a fresh character after the server admin cleared my files from the server,

How can I fix that?

[slayterson]

could the progressLoadingScreen 0.8; inside the end of the dedicated bracket of compiles.sqf cause any issues? seems out of place to me. as my ini is calling compiles between progress 4 and 5.

[DeputyDutch]

I am still having this same bug whilst trying to get a epoch server up to speed with other epoch servers. I've debugged many of the scripts so there is no possibility of any of my other scripts causing this error. Players are able to login once and play. Second time they log into the server they get stuck at the loading screen and can hear and move around. The above change does not seem to do anything for me but break the server so that no one can join so if there is a trick or something to getting that to work for everyone please let me know or point me in the right direction if at all possible?

[ebayShopper]

fixed https://github.com/vbawol/DayZ-Epoch/commit/547ba0018f8e71de641223397099da90f65f2d8d

[vbawol]

Rgr that, thanks!

[Evocation]

(y)