gametechmods

Robot Arena => General Support => Topic started by: Yeastisbeast on October 08, 2018, 01:19:17 PM

Title: Crashing and then startup
Post by: Yeastisbeast on October 08, 2018, 01:19:17 PM
No clue what happened here, was battling on DSL 2.2, and it crashed. I opened it up again and it showed the first start-up screen with my laptop's loading icon and closed itself. I tried restarting my laptop, same result.
Title: Re: Crashing and then startup
Post by: Billy5545 on October 09, 2018, 03:38:11 AM
Is there any ra2.cfg file in the broken copy of your RA2? If not, then it's the problem. You must try to reinstall a new .cfg, by copying one from the RA2 zip that you used to install, or another version of RA2 you have, like DSL or IF
Title: Re: Crashing and then startup
Post by: WeN on October 09, 2018, 03:43:52 AM
it's must be your cfg disappeared/broke. or something. Try replacing broken cfg with new one.
Title: Re: Crashing and then startup
Post by: Yeastisbeast on October 12, 2018, 11:13:18 AM
I tried copying a ra2.cfg from the zip file (my RA2 did have one) like WenXiang suggested, still no success unfortunately. Sorry for not replying for a while
Title: Re: Crashing and then startup
Post by: FOTEPX on October 12, 2018, 01:43:45 PM
I tried copying a ra2.cfg from the zip file (my RA2 did have one) like WenXiang suggested, still no success unfortunately. Sorry for not replying for a while

One problem I've had quite a few times is the teams.txt - replacing it'll get rid of your current teams, so back it up in case that's not the issue, but I've had it before where that document getting corrupted's locked up an entire game. Try replacing it with one from another copy of RA2.
Title: Re: Crashing and then startup
Post by: kix on October 12, 2018, 04:37:59 PM
Your teams.txt is borked either in AI or Teams folder
Title: Re: Crashing and then startup
Post by: WeN on October 12, 2018, 08:00:16 PM
agree with FOTEPX.
The "teams.txt" must be broken, replacing it will work.
Title: Re: Crashing and then startup
Post by: Yeastisbeast on October 13, 2018, 09:57:15 AM
Thanks guys I fixed it it was the teams problem