love.exe and hello world code won't run. No reaction at all.

[alinnert]

Hi,

I'm new to LÖVE, but not new to programming in general. I just want to try something new and wanted to give LÖVE a chance. But something seems to be very wrong, because I can't start love.exe or use it to run my code.

First of all: I'm on Windows 10, 64 bit.

Things I've tried:

• The 64-bit installer and the zipped package (added to PATH)
• Running a project from the console and via drag'n'drop on love.exe
  • yes, I've dropped the project folder containing the main.lua on love.exe
  • I've tried running

    Code: Select all

    love .

    and

    Code: Select all

    love C:\projects\löve\testgame

    from inside the project folder
• A VS Code extension that sais it runs LÖVE games via a command

All of them result in basically nothing. No error window. No error message or any output in the console. No quickly opening and disappearing window. No ping sound. I don't even see a process flashing up in the Task Manager.

Running love.exe directly from the Explorer shows the same behaviour. I've heard it should open a placeholder window if you do that. That doesn't happen for me.
Running love --version from the console prints: "LOVE 11.1 (Mysterious Mysteries)". So at least that works.
Running lovec.exe from the console prints the following error message:

Code: Select all

Error: [string "boot.lua"]:253: Failed to initialize filesystem: no error
stack traceback:
        [C]: in function 'init'
        [string "boot.lua"]:253: in function <[string "boot.lua"]:249>
        [C]: in function 'xpcall'
        [string "boot.lua"]:641: in function <[string "boot.lua"]:639>
        [C]: in function 'xpcall'

Does anyone have an idea what the problem could be?

Many thanks,
Andreas

[Link]

Just a guess, but have you tried changing C:\projects\löve\testgame to the ASCII C:\projects\love\testgame? Wondering if the Windows command line has legacy issues with Unicode characters.

Also, if you run simply "love" (with no arguments) via the command line, do you get a placeholder window?

[alinnert]

@Link: Yes, I just did that and it doesn't help. Also, running "love" alone doesn't bring up the placeholder window. But I just noticed, running "love" or "love ." on Git Bash in ConEmu I also see the error message "Failed to initialize filesystem..." I've posted above. So, this error seems to be raised at all times but some consoles just don't print it. Now I'm confused...

[harrisyu]

Yes, I can comfire that. very weird problem. And I download 11.0 is the same, but 10.2 and below is working.

[Murk]

I'm having the same issue.

Running Windows 10 Pro x64 17723.1000, issue appeared with 17713 as well - both are insider preview versions, so I'm suspecting that since I'm having some other unrelated issues as well.

[alinnert]

@Murk: 177xx is a preview build, right? I've reinstalled Windows on my machine, but this time the stable build (1803, Build 17134.228). Love2d 11.1 works just fine now. So maybe there's a problem in the preview build of Windows.

[Astorek86]

*Bump*, because I have this issue too^^.

A few Days ago, everything works fine on my PC. Then, Windows-Update 1809 appears... And after that, LOVE works no more. It's exactly the same Error that alinnert describes. Happens on both 32- and 64-bit-Version. Reinstalling LOVE doesn't do anything about it...

[slime]

Windows 10 version 1809 changed the behaviour of an API love uses during startup, unfortunately. There's a build with a fix here until an official release happens: https://bitbucket.org/rude/love/issues/ ... t-48155677

[Styrac]

I don't understand fully what the problem is or how to bitbucket link helps fix it, but I'm experiencing this problem too and could use some help

[Astorek86]

Jep, the Download-Links are gone. Couldn't find other mirrors^^.