The Last Outpost

Gaming Divisions => RPG-X => Development Discussion => Topic started by: Jack Telford on May 21, 2016, 02:26:42 PM

Title: Instability on Admin menu options
Post by: Jack Telford on May 21, 2016, 02:26:42 PM
On singleplayer and on my private server when ever i click the chreate char button to create a charecter or create forcefields my game gets unstable usually crashes depending on how many charecters or forcefields.
Title: Re: Instability on Admin menu options
Post by: Telex Ferra on May 21, 2016, 02:48:39 PM
Is this a clean install of RPG-XUE or did you change any settings? What operating system are you on?
Title: Re: Instability on Admin menu options
Post by: Jack Telford on May 21, 2016, 03:52:16 PM
Windows 10 I have changed settings before but it was unstable before I changed then
Title: Re: Instability on Admin menu options
Post by: Telex Ferra on May 21, 2016, 04:15:09 PM
Not sure I can reproduce this one. Can you give us a crash log from a crash caused by this? It might shed some light on the issue
Title: Re: Instability on Admin menu options
Post by: Jack Telford on May 22, 2016, 02:55:15 PM
Where are the crash logs? When it crashses the screen just flashes and crashes
Title: Re: Instability on Admin menu options
Post by: Telex Ferra on May 22, 2016, 04:56:22 PM
So it doesn't ask you if you want a console dump? Hmmm

I'm running Windows 10 and I'm not seeing this problem at all. Does it happen on the first try spawning a char, or is it only after a while?
Title: Re: Instability on Admin menu options
Post by: Serris on May 22, 2016, 04:59:52 PM
I can vouch for forcefield creation being unstable. There was an incident on the server within the last few months where I accidentally placed an admin forcefield and everyone in the area suffered a client crash.
Title: Re: Instability on Admin menu options
Post by: Telex Ferra on May 22, 2016, 05:19:50 PM
Quote from: Serris on May 22, 2016, 04:59:52 PM
I can vouch for forcefield creation being unstable. There was an incident on the server within the last few months where I accidentally placed an admin forcefield and everyone in the area suffered a client crash.

Do you remember which map and where you placed them. I've seen this before too, but I'd like to have a sure-way to reproduce this so it'll be easier to track down and fix.
Title: Re: Instability on Admin menu options
Post by: Jack Telford on May 22, 2016, 06:33:18 PM
It happens on Station Iowa I know for sure but that's also the map I use the most with my friends. Station Vanderbilt as well. I'm pretty sure almost any map would work though.
Title: Re: Instability on Admin menu options
Post by: Martin Thompson on May 23, 2016, 02:18:20 AM
Its possible it only happens under certain conditions,  problems we cant reproduce are very hard for us to fix. Any specific details are always welcome.

@ Telex, perhaps we should have a bug report template here on the forum with a few fields asking for specific info we could use/need. I could then copy those issues over to github.
Title: Re: Instability on Admin menu options
Post by: Serris on May 23, 2016, 10:42:46 PM
Quote from: Telex Ferra on May 22, 2016, 05:19:50 PM
Quote from: Serris on May 22, 2016, 04:59:52 PM
I can vouch for forcefield creation being unstable. There was an incident on the server within the last few months where I accidentally placed an admin forcefield and everyone in the area suffered a client crash.

Do you remember which map and where you placed them. I've seen this before too, but I'd like to have a sure-way to reproduce this so it'll be easier to track down and fix.

The bridge of DH_RPG_USSAurora, near the viewscreen.
Title: Re: Instability on Admin menu options
Post by: Telex Ferra on May 23, 2016, 11:00:22 PM
Quote from: Serris on May 23, 2016, 10:42:46 PM
Quote from: Telex Ferra on May 22, 2016, 05:19:50 PM
Quote from: Serris on May 22, 2016, 04:59:52 PM
I can vouch for forcefield creation being unstable. There was an incident on the server within the last few months where I accidentally placed an admin forcefield and everyone in the area suffered a client crash.

Do you remember which map and where you placed them. I've seen this before too, but I'd like to have a sure-way to reproduce this so it'll be easier to track down and fix.

The bridge of DH_RPG_USSAurora, near the viewscreen.

I'll try this out tomorrow.
Title: Re: Instability on Admin menu options
Post by: Jack Telford on May 24, 2016, 08:17:22 AM
For the character thing it happens a lot when its like trying to do it with an emote. Like typing on a console. It sometimes happens with only one or sometimes happens with multiple. Forcefields normally happen after multiple are placed down.
Title: Re: Instability on Admin menu options
Post by: Telex Ferra on May 24, 2016, 07:34:29 PM
So the console emotes? I'll give it a shot. Does this only happen on your local server? If you raise the hunkmegs and zonemegs on your server, does this problem persist?
Title: Re: Instability on Admin menu options
Post by: Telex Ferra on May 24, 2016, 08:49:03 PM
Quote from: Telex Ferra on May 23, 2016, 11:00:22 PM
Quote from: Serris on May 23, 2016, 10:42:46 PM
Quote from: Telex Ferra on May 22, 2016, 05:19:50 PM
Quote from: Serris on May 22, 2016, 04:59:52 PM
I can vouch for forcefield creation being unstable. There was an incident on the server within the last few months where I accidentally placed an admin forcefield and everyone in the area suffered a client crash.

Do you remember which map and where you placed them. I've seen this before too, but I'd like to have a sure-way to reproduce this so it'll be easier to track down and fix.

The bridge of DH_RPG_USSAurora, near the viewscreen.

I'll try this out tomorrow.

So I tried it on linux on both the develop and master branches and could not reproduce the crash. I made maybe 10 ffs all over the bridge, some of which extended out through the viewscreen, and did not see a crash. Since some of the game settings aren;'t in the git repo (and wouldn't be reverted by a branch change) I'm guessing either the crash doesn't happen at all on linux, or the CVAR changes we made already prevent this.