Author Topic: GSX 2 Crash always in y Prepare3D V.5.3 Hotfix 1  (Read 1240 times)

jorgemalrov

  • Newbie
  • *
  • Posts: 2
GSX 2 Crash always in y Prepare3D V.5.3 Hotfix 1
« on: February 28, 2022, 01:30:17 pm »
Hi all,
I fly with Prepare 3D V.5.3 Hotfix 1 and I do not why everytime I start a flight and I press F2 to activate the GSX2 Menu, my Prepare3D crash and I think to restart again the simulator. Once I press this F2 suddenly appear a black box (where I should read the GSX Menu with the different option) but the simulator crash.
I decided to download again from the beggining the GSX2 (I have GSX+Level 2 Bundle) software even using your new Universal Intaller and it happens the same.
It's true that once its intalled a window appear (scenary activator 1.11) in my computer telling me: Error in layer values. The scenary.cfg is corrupt. Press to continue.

Is there a connection bewtween this "scenary corrupt" and GSX? What can I do? Everytime I try to enjoy my flight with GSX2 experience it always crash and I do not know what to do.

I apologize my poor knoweledges in terms of teechnology and software so I will really appreciate your help.

All my best,

Jorge


virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: GSX 2 Crash always in y Prepare3D V.5.3 Hotfix 1
« Reply #1 on: February 28, 2022, 02:25:10 pm »
I fly with Prepare 3D V.5.3 Hotfix 1 and I do not why everytime I start a flight and I press F2 to activate the GSX2 Menu, my Prepare3D crash and I think to restart again the simulator. Once I press this F2 suddenly appear a black box (where I should read the GSX Menu with the different option) but the simulator crash.

You should absolutely update to HF2, this problem it's a very well know bug in HF1, which affects every application with a menu, and it has been *mostly* fixed in 5.3 HF2.

jorgemalrov

  • Newbie
  • *
  • Posts: 2
Re: GSX 2 Crash always in y Prepare3D V.5.3 Hotfix 1
« Reply #2 on: February 28, 2022, 03:29:36 pm »
Ciao Umberto. I didn't know it was well known this problem with HotFix 1. Thanks very much for your answer and your advise and hopefully it will be solved updating to HotFix 2  :) Jorge