Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

GMLive.gml

Livecoding for GameMaker: Studio / GameMaker Studio 2 · By YellowAfterlife

Unable to Import Updated Asset Package into Existing Project with GMLive

A topic by Quixottic created Dec 28, 2021 Views: 154 Replies: 2
Viewing posts 1 to 3

I was trying to update to the new release of GMLive (huge thank you for this amazing asset!!), and I am unable to get it to import into my project that had a previous version of GMLive in it. Wouldn't be surprised if I screwed something up here, but I've been unable to figure out a solution in my puttering... 

In an existing project, I deleted the old GMLive extension. And now when I try to import the new version, nothing happens... Output shows the following code: 

"cmd"  /c subst Z: "C:\Users\Michael Sherman\AppData\Local\GameMakerStudio2\GMS2TEMP\GMLiveForGMS2.3+_5ae1f70d\extract"

elapsed time 00:00:00.0289228s for command "cmd" /c subst Z: "C:\Users\Michael Sherman\AppData\Local\GameMakerStudio2\GMS2TEMP\GMLiveForGMS2.3+_5ae1f70d\extract" started at 12/28/2021 08:18:35

"cmd"  /c subst Y: "Z:\"

elapsed time 00:00:00.0877647s for command "cmd" /c subst Y: "Z:\" started at 12/28/2021 08:18:35

"cmd"  /c subst Y: /d

elapsed time 00:00:00.0259312s for command "cmd" /c subst Y: /d started at 12/28/2021 08:18:35


But I don't get the usual import asset window or any of that. 

Additionally, if I create a blank project and import it, it works fine. So... I'm guessing I screwed something up here, but can't seem to work around whatever issue that is. Any help would be hugely appreciated, because I can't live without GMLive. =)  Thank you, thank you!

(1 edit)

Posting the solution I finally arrived at... No idea why, but I had the new GMLive .yymps file saved on a different storage drive. When I moved its location to the same drive as my GameMaker install, then the import worked properly. Head scratch, but resolved. =)

Developer(+1)

If this is reproducible, it might be worth reporting a GM bug - I don’t have specific thoughts on how import could fail depending on source drive.