AGS: Quest for Glory II Remake: Import a Hero does not work

[OmerMor]

Running the latest daily build (2021-03-03 01:44:20 downloaded on 2021-03-19) on Windows 10.

When starting the game, and pressing "Import a Hero" the game writes the following message:
"I'm sorry, there don't appear to be any Quest for Glory saved characters in this folder."

I've tried to put a qfg1 exported save file in the following folders:

• ScummVM's save path
• ScummVM's program path
• The game's folder

None of these worked.

[OmerMor]

Just confirmed that this is still reproduced is the 2021-03-19 daily snapshot as well.

[dreammaster]

Could you attach the exported save for testing purposes? Thanks.

[OmerMor]

Done.

[criezy]

This seems to work for me.

If I put your file in the game folder it is found (see screenshot in attachment).

If I put the file in the save path, I need to add the game target as a prefix (in my case "qfg2agdi-") as in ScummVM we add a prefix for all the files in the save path to avoid conflicts between several AGS games (for example several games try to create or read a 'user.cfg' file in the save path).

[OmerMor]

On my machine it doesn't work. Maybe it's a problem with the Windows build?
I have the file in my game folder, as well as in my save path.
I have it named both as qfg1-q1-abra.sav and qfg2agdi-q1-abra.sav
I still get the same "not found" reply.
I monitored ScummVM's file system access with Sysinternals' Process Monitor and saw that it does indeed scan the relevant folders and even find the save files.
However an operation of IRP_MJ_CREATE for the file returns result of NAME_INVALID.
(If it matters, loading regular saved games from this game works, so not all file system access is failing.)

[dreammaster]

Well, I confirmed that the fix I did yesterday worked when I did Downloaded all the attachments as a zip, and then extracted the .sav file. The way it works, it should list any .sav file in your game directory, and any .sav file in the ScummVM save path that has a "qfg2agdi-*.sav" form (or whatever prefix/target your game entry has).

[OmerMor]

Thanks! Verified fix in the latest daily snapshot.

[lwcorp]

Well, this apparently got unfixed, both in v2.7.1 and v2.9.0git234-g6ed3c946ffc.

What happens now is that it actually presents only its own export files, i.e. specifically those with prefix qfg2agdi- (see #14754).

Of course they can't be used (trying to click them produces "I'm terribly sorry. That doesn't seem to be a proper Quest for Glory I save file." - which is true). A temporary fix is to rename qfg1vga-X.sav or qfg1-X.sav to qfg2agdi-X.sav, and then it becomes importable.

Can someone please re-fix it to only accept qfg1vga-X.sav and qfg1-X.sav files?

P.S.
Can you allow this game's import screen to change folders like in the SCI games?

[tag2015]

Replying to lwcorp:

Well, this apparently got unfixed, both in v2.7.1 and v2.9.0git234-g6ed3c946ffc.
Can someone please re-fix it to only accept qfg1vga-X.sav and qfg1-X.sav files?

I don't think that it ever worked like this. It's clearly explained by dreammaster in his post:

"it should list:

• Any .sav file in your game directory, and
• Any .sav file in the ScummVM save path that has a "qfg2agdi-*.sav" form (or whatever prefix/target your game entry has)

"

P.S.
Can you allow this game's import screen to change folders like in the SCI games?

What do you mean? The SCI games don't allow changing folders in the import window, when ran through ScummVM

[lwcorp]

Then obviously they got it wrong. It makes no sense to show qfg2agdi-*.sav since it can't import its own exports. It should only show qfg1*-X.sav files as that's what it can import.

You're right about changing folders. It's just that in QFG3/4 ScummVM grays it out as opposed to just not show this option at all.

[tag2015]

Replying to lwcorp:

Then obviously they got it wrong. It makes no sense to show qfg2agdi-*.sav since it can't import its own exports. It should only show qfg1*-X.sav files as that's what it can import.

It was implemented like this for a reason, as mentioned in a previous post.
When an AGS game accesses the savedir all the files are expected to be prefixed with the gameid (qfg2agdi, unless the user changed it). This is to avoid interfering with other games, so you understand that the only way to list the qfg1 saves is to add some hack specifically for this game, which we'd rather avoid considering that the save can be correctly imported placing the save in the gamedir (or changing the prefix as explained).

It's true that it clashes with files exported by this game but I don't think that's much of a problem... the game tells you when the file is not a QfG1 character, and frankly I don't think there are that many users affected by this potential problem (considering that you need to complete both games, unless you cheat that is)

I think that the best idea is to add a informational messagebox when opening the import option, like in the SCI engine.

[lwcorp]

I don't understand this, do you expect people to break QFG3 and QFG4 in order to support QFG2?
Because if they rename qfg1-something.save it to qfg2agdi-something.sav then both QFG3 and QFG4 will complain trying to import from the wrong game (QFG2 instead of QFG1).

Moreover, you don't seem to care QFG4 interferes with QFG1-3's files and QFG3 interferes with QFG1-2's files, but QFG2 should be the exception?

[tag2015]

Replying to lwcorp:

I don't understand this, do you expect people to break QFG3 and QFG4 in order to support QFG2?
Because if they rename qfg1-something.save it to qfg2agdi-something.sav then both QFG3 and QFG4 will complain trying to import from the wrong game (QFG2 instead of QFG1).

You just need to copy the exported .sav as qfg2agdi-character.sav to allow importing. Also, if you don't want to mess with the saves in the save folder, what is the problem with copying the save directly to the QfG2-remake folder?

Moreover, you don't seem to care QFG4 interferes with QFG1-3's files and QFG3 interferes with QFG1-2's files, but QFG2 should be the exception?

I can't comment on the SCI engine, since I never worked on it (besides the small addition last week to fix the issue you reported). But QfG2 remake is the exception because it's a different engine, and that's how saves in AGS are handled.

[i30817]

In android you can't even see the default save dir, much less copy things off it into other folders (unless you're using cloud saves I suppose - maybe).

Without that 'just do it yourself' rings a bit hollow.

[i30817]

Moreover I quite like the ability to place games in read only locations (like a DVD or a squash file).

[tag2015]

I think you all have made your points, thanks.
I'll see if it's possible to implement it cleanly, but I'm puzzled how this issue went without discussions at all for 3 years...

Anyway, please note that is not a common usecase, basically you expect to move files between different engines without user itervention. I don't think this ever happens anywhere else in ScummVM.

[OmerMor]

Replying to tag2015:

Anyway, please note that is not a common usecase, basically you expect to move files between different engines without user itervention. I don't think this ever happens anywhere else in ScummVM.

It could happen again in the future if ScummVM adds support for QfG5, which used another engine as well.

[lwcorp]

Replying to tag2015:

I'll see if it's possible to implement it cleanly, but I'm puzzled how this issue went without discussions at all for 3 years...

Because this is a bug that appears after the endgame, and until last week's release it was impractical to play through the entire game due to #12998.

Anyway, please note that is not a common usecase, basically you expect to move files between different engines without user itervention. I don't think this ever happens anywhere else in ScummVM.

Like you wrote above, you didn't work a lot on SCI but over there every QFG game does it. QFG4 accepts only QFG3-*.sav, QFG2-*.sav and QFG1-*.sav files. QFG3 accepts only QFG2-*.sav and QFG1-*.sav files. The original QFG2 accepts only QFG1-*.sav files. And when #14754 becomes official, QFG4 and QFG3 will even accept qfg2agdi-*.sav files. If QFG5 become supported it will also accept QFG4-*.sav files. But none of them accepts their own files.
This is even though QFG4 in infamous for actually accepting its own files (which is a cheat). But in ScummVM one has to rename them to a previous game to make it work. That is, ScummVM disabled a direct legitimate cheat for the mere principle of not accepting the game's own files.

[tag2015]

Like you wrote above [...]

What I meant is that accessing saves created on another engine is not a common situation. You already explained how the other QfG games work, but those are all part of the SCI engine.
QfG2AGDI just happens to be one of the games that is supported by the AGS engine (which supports thousands of other games). We didn't implement it individually, that's why it should follow how the rest of the engine behaves.
Anyway as I said, since multiple people are asking for this "fix", I'll try to implement in a clean way.

[tag2015]

Fixed in commit ​015937d

Should be in tomorrow's daily builds (master only, if there are no problems I may also backport to 2.8)

[lwcorp]

Thanks so much for making an AGS exception for this game!
It seems to work well in v2.9.0git1795-g98c92916825 (Feb 1 2024 04:49:03), even adding a screenshot, so do you want to have the status changed from pending?

[lwcorp]

The new import alert

[tag2015]

Thanks for testing! Closing the bugreport then