search

MeteorTheLizard / SMITE-Optimizer

Configuration file editor for the game SMITE on PC (Windows).
https://meteorthelizard.com/projects/smite-optimizer
GNU General Public License v3.0
21 stars 2 forks source link

Array variable has incorrect number of subscripts #12

Closed SPG1091 closed 1 year ago

SPG1091 commented 1 year ago

I get this window when I go to apply with any settings. Cant create a bug dump as the program closes when I select ok. I just want my new 6800 xt to run it better than 1660ti :'(

smite error

MeteorTheLizard commented 1 year ago

Duplicate of #11

Have you launched SMITE at least once on your system before?

SPG1091 commented 1 year ago

Yes, many times.

MeteorTheLizard commented 1 year ago

I require more information to figure out what's going on.

Have you launched the SMITE Optimizer on your system before changing to your new graphics card and did it work?

Have you reinstalled your system after changing to the new graphics card?

What exactly does the program do after you start it? From your description I take that it immediately crashes upon reaching the home screen, is that correct?

DevNote: L:6062: refers to ExitLoop / EndIf - cannot be the cause of array dimensions exceeding!

SPG1091 commented 1 year ago

I have not used smite optimiser prior to installing the new GPU. I have not reinstalled, just literally took the old GPU out and stuck the new one in. The program starts and runs and I can adjust all the parameters, however, once I select verify and repair or apply changes, the loading bar starts, gets maybe halfway then displays the shown error, when I ok the shown error the program closes.

MeteorTheLizard commented 1 year ago

Have you launched SMITE at least once after installing your new GPU?

Also it should be possible to create a debug dump. You can do that in the "Debug" tab. Click the text and it will open a window where you have to select the location to save it in. Attach the file here.

MeteorTheLizard commented 1 year ago

Another potential solution would be to head into the debug tab and disable the verify/repair integrity routine. It's possible that the HIVEs are outdated.

SPG1091 commented 1 year ago

Disabling the verify and repair routine has been successful. Thank you for all your help!

MeteorTheLizard commented 1 year ago

Fixed in v1.3.5