Log In  
Log In  

I'm unable to get PICO-8 0.1.5 running on 64bit Windows 10 pro with the latest updates installed.
Program icon just quickly flashes on the task bar, but the console doesn't appear.
The machine itself is a Lenovo X200 and it has Intel's GPU.

Log file contains the following:

codo_init
  platform: Windows
  codo_system_init
  codo_reset_timer
  codo_gui_init
  codo_keys_init
  codo_text_init
  codo_video_init
  codo_mouse_init
  codo_joystick_init
  codo_joystick_init
    found 0 joystick(s)
  ok
ok
codo_set_screen 580 540 8 100
P#19398 2016-03-25 04:14 ( Edited 2016-04-10 07:49)

:: Scathe

Windows is up to date, but are all of your drivers? I'm running Pico-8 on Windows 10 Pro x64 as well, and no problems here (AMD processor, nVidia GPU).

Some troubleshooting things to try: 1.) Have you rebooted (I know this is an obvious one, just want to cover all bases)? 2.) Try running Pico-8 as an administrator. 3.) Try enabling compatibility mode for Windows 7 or 8 (although I don't have to do this, but it's worth a try). 4.) Delete Users/<you>/AppData/Roaming/pico-8/config.txt to reset everything to default. 5.) Make sure you aren't running Pico-8 with command line parameters added. 6.) Make sure your graphics and sound card drivers are up to date. If all else fails: 7.) uninstall and reinstall Pico-8.

Have you had it running on this system before? If not, and none of the other suggestions work, maybe the installer itself is corrupted. Try redownloading the installer and reinstalling from that.

P#19399 2016-03-25 10:27 ( Edited 2016-03-25 14:37)
:: tolja

I haven't been able to get it running on this machine with Windows at all and none of the tips above didn't change the situation.

Pico-8 starts nicely when running on Linux, but that isn't a viable solution this time.

P#19405 2016-03-25 13:28 ( Edited 2016-03-25 17:28)
:: Scathe

Ok, so I was finally able to test this on an old netbook just to see. The netbook has Windows 10 Home (32-bit), 1GB of memory, 1.6 GHz Intel Atom CPU, and Intel graphics, Same symptoms as tolja - icon quickly flashes up on the taskbar, then the application silently crashes.

P#19642 2016-04-08 00:03 ( Edited 2016-04-08 04:18)
:: Scathe

Here is the Windows error log for the crash:

Faulting application name: pico8.exe, version: 0.0.0.0, time stamp: 0x56b4c41e
Faulting module name: SDL2.dll, version: 2.0.2.0, time stamp: 0x531a9ec1
Exception code: 0xc0000005
Fault offset: 0x000c2eee
Faulting process id: 0x16f0
Faulting application start time: 0x01d1918f35fda030
Faulting application path: C:\Program Files\PICO-8\pico8.exe
Faulting module path: C:\Program Files\PICO-8\SDL2.dll
Report Id: 79eb9ae5-c113-47f6-8f0c-d6eee524f03a
P#19646 2016-04-08 08:14 ( Edited 2016-04-08 12:14)
:: Scathe
1

Ok, I got it working. The problem appears to be with the SDL2 version included with Pico-8. Is it possible that you have 32-bit Windows instead of 64? Because the error that was thrown in my particular event log indicated that there was a null pointer, which may be an exception that happens when a 64-bit DLL is being accessed from a 32-bit system.

Anyway, just go here, download the SDL2-2.0.4-win32-x86.zip (32-bit Windows), and extract it to C:\Program Files\PICO-8. This will overwrite the SDL2.dll file that comes with Pico-8 and allow it to run.

P#19647 2016-04-08 08:38 ( Edited 2016-04-08 12:38)
:: tolja

Got it working with the DLL, thanks.
The OS is indeed 64bit but pico-8 is installed under Program Files (x86).

P#19672 2016-04-10 03:49 ( Edited 2016-04-10 07:49)

Voxatron 0.3.5b wouldn't run on Windows 10 Pro Build 18305, but after replacing the SDL2.dll with the one Scathe advised using, it worked right away, Thank You!

P#60462 2018-12-31 15:12

i'm having the same issues as the original poster. Pico-8 opens a window and then closes and nothing else happens. I'm on a 64 bit system and i tried to replace the SDL2 like they did above. What else could i check to find out what's going on?

P#61598 2019-02-07 01:04

Here's the log I currently have:

codo_init
  platform: Windows
  codo_system_init
  Compiled against SDL version: 2.0.2
  Linked against SDL version:   2.0.4
  Built-in video drivers:   0 windows   1 dummy  
  Current video driver: windows
  Built-in render drivers:
  Renderer direct3d:
    Flags: 0x0000000E ( |  | )
    Texture formats (1): ARGB8888
  Renderer opengl:
    Flags: 0x0000000E ( |  | )
    Texture formats (1): ARGB8888
  Renderer opengles2:
    Flags: 0x0000000E ( |  | )
    Texture formats (4): ARGB8888, ABGR8888, RGB888, BGR888
  Renderer software:
    Flags: 0x00000009 ( | )
    Texture formats (8): ARGB8888, ABGR8888, RGBA8888, BGRA8888, RGB888, BGR888, RGB565, RGB555
  codo_reset_timer
  codo_gui_init
  codo_keys_init
  codo_text_init
  codo_video_init
  codo_mouse_init
  codo_joystick_init
  Reading controller mappings: C:/Users/C/AppData/Roaming/pico-8/sdl_controllers.txt
  searching for joysticks
    found 0 joysticks
  ok
ok
codo_load_pod: C:/Program Files (x86)/PICO-8/pico8.dat ok 
codo_set_screen 128 128 8 100
 set pixel_perfect 1
 window size: 640 480
P#61599 2019-02-07 01:10 ( Edited 2019-02-07 01:10)

Found my problem. Putting it here in case anybody else needs help with this. I had to update my display drivers. I opened the event viewer, and I could see a bunch of errors where Pico8 tried to open. The error message looked like this:

Faulting application name: pico8.exe, version: 0.0.0.0, time stamp: 0x00010000
Faulting module name: ig9icd32.dll, version: 23.20.16.5018, time stamp: 0x5aba5eb5
Exception code: 0xc0000005
Fault offset: 0x0001dd2b
Faulting process id: 0x25e8
Faulting application start time: 0x01d4be82fdf61464
Faulting application path: C:\Users\C\Downloads\pico-8_0.1.11g_windows\pico-8_win32\pico8.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64_kbl_kit127397.inf_amd64_e1da8ee9e92ccadb\ig9icd32.dll
Report Id: ce7be402-0822-4b1a-82b8-77efa48710e3
Faulting package full name: 
Faulting package-relative application ID: 

i looked up "ig9icd32" online and it sent me to an intel forum that said i needed to get the latest update. I downloaded the update and everything worked fine. Thanks to everybody in this thread for the help! I wouldn't have known how to tackle this without you guys!! :)

P#61600 2019-02-07 01:28 ( Edited 2019-02-07 01:28)

[Please log in to post a comment]

X
About | Contact | Updates | Terms of Use
Follow Lexaloffle:        
Generated 2019-03-25 01:34 | 0.016s | 4194k | Q:30