Author Topic: AVA test terrain  (Read 524 times)

Offline captain1ma

  • Aces High CM Staff
  • Plutonium Member
  • *******
  • Posts: 14384
      • JG54 website
AVA test terrain
« on: March 16, 2018, 08:08:00 PM »
hi all, I need a little help. if you get a chance can you pop into the AVA arena and
see if you can get in or if it boots you to desktop. I had some trouble with it on Monday night
and want to see if its fixed. thanks.

Please jump on here and report back. thanks.


<S>

Offline Spikes

  • Aces High CM Staff
  • Plutonium Member
  • *******
  • Posts: 15721
    • Twitch: Twitch Feed
Re: AVA test terrain
« Reply #1 on: March 17, 2018, 08:57:23 AM »
Jaeger,

It lets me in for only a few seconds before AH crashes. Same symptoms as the AvA night. Not sure if I can provide any log files or anything.
i7-12700k | Gigabyte Z690 GAMING X | 64GB G.Skill DDR4 | EVGA 1080ti FTW3 | H150i Capellix

FlyKommando.com

Offline captain1ma

  • Aces High CM Staff
  • Plutonium Member
  • *******
  • Posts: 14384
      • JG54 website
Re: AVA test terrain
« Reply #2 on: March 17, 2018, 09:00:16 AM »
thanks that's what I'm trying to find out!

Offline captain1ma

  • Aces High CM Staff
  • Plutonium Member
  • *******
  • Posts: 14384
      • JG54 website
Re: AVA test terrain
« Reply #3 on: March 17, 2018, 09:05:44 PM »
ok I made a few changes, if you guys can go in try it again, id appreciate it. try crashing into one of the spires also. im looking to see if crashes you to desktop.

Offline captain1ma

  • Aces High CM Staff
  • Plutonium Member
  • *******
  • Posts: 14384
      • JG54 website
Re: AVA test terrain
« Reply #4 on: March 17, 2018, 10:52:24 PM »
I pulled down the terrain. we'll use something different for Monday night.

Offline captain1ma

  • Aces High CM Staff
  • Plutonium Member
  • *******
  • Posts: 14384
      • JG54 website
Re: AVA test terrain
« Reply #5 on: March 18, 2018, 04:33:00 PM »
hi all, I've reloaded the Monday night madness terrain in the AVA. can you please jumping in it again. we think we found the problem. thanks

<S>