PathOfBuilding icon indicating copy to clipboard operation
PathOfBuilding copied to clipboard

Path of Building not launching

Open UpsetAlpaca opened this issue 3 years ago • 2 comments

Check version

  • [X] I'm running the latest version of Path of Building and I've verified this by checking the changelog

Check for duplicates

  • [X] I've checked for duplicate issues by using the search function of the issue tracker

What is the expected behaviour/value?

When i open Path of Building, the launcher opens and should load into the program

What is the actual behaviour/value?

When i open the launcher:

SimpleGraphic v1.0 x86 Release, built Dec 30 2021

Executing SimpleGraphic/SimpleGraphic.cfg Executing SimpleGraphic/SimpleGraphicAuto.cfg Warning: config file not found Executing C:\Users\ialex\AppData\Roaming\Path of Building Community\Launch.cfg Warning: config file not found

--- UI Init --- Script: C:\Users\ialex\AppData\Roaming\Path of Building Community\Launch.lua Script working directory: C:\Users\ialex\AppData\Roaming\Path of Building Community Initialising Lua... Running script...

--- Render Init --- Pixel format: need 32,24,0

How to reproduce the issue

Opening the program. If i run troubleshooter and open with Windows 95 it works. not sure why

Character build code

SimpleGraphic v1.0 x86 Release, built Dec 30 2021

Executing SimpleGraphic/SimpleGraphic.cfg
Executing SimpleGraphic/SimpleGraphicAuto.cfg
Warning: config file not found
Executing C:\Users\ialex\AppData\Roaming\Path of Building Community\Launch.cfg
Warning: config file not found

--- UI Init ---
Script: C:\Users\ialex\AppData\Roaming\Path of Building Community\Launch.lua
Script working directory: C:\Users\ialex\AppData\Roaming\Path of Building Community
Initialising Lua...
Running script...

--- Render Init ---
Pixel format: need 32,24,0

Screenshots

No response

UpsetAlpaca avatar Aug 20 '22 20:08 UpsetAlpaca

Try https://github.com/PathOfBuildingCommunity/PathOfBuilding/issues/4736#issuecomment-1211478087

QuickStick123 avatar Aug 20 '22 22:08 QuickStick123

@UpsetAlpaca also, I had the same thing happened, and after updating my nVidia graphic drivers to latest version, (or restarting the graphic driver) the problem went away.

Please confirm if that works for you.

Nostrademous avatar Dec 06 '22 15:12 Nostrademous