Grimoire Thread

[Cael]

Need to find my damn notes.

... Riffington???

 

[Haba]

Cleve at the moment:

 

[Bad Sector]

Cleve, I was able to reproduce the weird scaling/cropping issue some users were complaining about on Steam forums. The culprit is DPI virtualization introduced in Windows Vista.

Ah yeah, i had the same issue with my own engine getting zoomed in. The fix is trivial, just call SetProcessDPIAware from user32.dll right after your program starts (in WinMain). In my engine i call that via LoadLibrary and GetProcAddress so that it works even in older Windows versions (also i'm mostly using Borland C++ 5 released in 1997 which has no idea about such things so i have to load any new stuff dynamically :-P), but according to Microsoft docs this is supported since Vista so if your minimum requirements (...and compiler :-P) include that you can simply use it directly.

 

[Solanacean]

Ah yeah, i had the same issue with my own engine getting zoomed in. The fix is trivial, just call SetProcessDPIAware from user32.dll right after your program starts (in WinMain). In my engine i call that via LoadLibrary and GetProcAddress so that it works even in older Windows versions (also i'm mostly using Borland C++ 5 released in 1997 which has no idea about such things so i have to load any new stuff dynamically :-P), but according to Microsoft docs this is supported since Vista so if your minimum requirements (...and compiler :-P) include that you can simply use it directly.

Indeed, calling SetProcessDPIAware is one way to declare DPI awareness, although according to the article on microsoft.technet, using this method "is discouraged, except in very specific circumstances", because "if a DLL caches DPI settings during initialization, invoking SetProcessDPIAware in your application might generate a possible race condition". And yes, using run-time dynamic linking (importing the function via LoadLibrary/GetProcAddress) is the proper way to do it unless compatibility with Windows XP is not required, which I believe is not the case here. If Cleve decides to take this route, the following code does the job:

HMODULE hUser32 = LoadLibrary(_T("user32.dll"));
typedef BOOL (WINAPI *SetProcessDPIAwareFunc)();
SetProcessDPIAwareFunc setDPIAware = (SetProcessDPIAwareFunc)GetProcAddress(hUser32, "SetProcessDPIAware");
if (setDPIAware)
{
    setDPIAware();
}
FreeLibrary(hUser32);

The other (recommended) way to make an application DPI aware is to set dpiAware property in the application's assembly manifest file. The article I mentioned above explains how to do it in Visual Studio 2005 and 2008 (I think).

 

[Solanacean]

The manifest code embedded in the Grimoire's executable looks like this:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>

Using resource tuning tool, I extended it with this code:

<application xmlns="urn:schemas-microsoft-com:asm.v3">
  <windowsSettings>
    <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">True/PM</dpiAware>
  </windowsSettings>
</application>

This is the final result:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>
  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
      <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">True/PM</dpiAware>
    </windowsSettings>
  </application>
</assembly>

Tested it on Windows 7 and Windows XP, works beautifully.

 

[Generic-Giant-Spider]

I LOVE YOU CLEVE.

 

[Lady_Error]

generate a possible race condition

 

[sputtering fart balloon]

On a scale of 1 - 10, how hard is this game to get into if you've played like, half of two blobbers before? I want to play it for the memes but am kinda spooked since people are saying the UI is confusing and it doesn't explain anything.

 

[Lady_Error]

I'm not sure what memes you are hoping to find there.

If you never played Wizardry 6 or 7, then yeah, you may need to figure out a few things first when playing Grimoire. But it's not rocket science and there is a manual and an extensive guide:

http://goldeneragames.com/Manual_GrimoireRPG_V2/
http://grimoire.wiki

 

[Sacibengala]

Wish GOG stopped this nonsense and accept this game. It hurts the need to buy rpgs on steam.

 

[Lady_Error]

You can buy it on itch.io instead:
https://cleveblakemore.itch.io/grimoire-heralds-of-the-winged-exemplar

 

[luj1]

Solution to mouse problems - reduce mouse polling rate to 125 Hz in driver software

Solution to improper scaling - set your launch options in steam properties for the game to -w1024 -h768

Still necessary?

 

[sputtering fart balloon]

Lady Error I meant memes as in being in on Grimoireposting, but thanks, I am reading those now.

 

[Valky]

You can buy it on itch.io instead:
https://cleveblakemore.itch.io/grimoire-heralds-of-the-winged-exemplar

Also, you can pay the original true value of Grimoire of $40 on itch.io.

 

[Sacibengala]

You can buy it on itch.io instead:
https://cleveblakemore.itch.io/grimoire-heralds-of-the-winged-exemplar

Interesting, thanks.

 

[Rpguy]

Steam:

I have a repeatable fatal crash bug when my party tries to leave Tabernacle of Music.

GOLDEN ERA GAMES [developer] 19 hours ago

Sorry about this bug, it is one of the few bugs left that can cause a crash. I will be fixing it before the next update.

 

[Valky]

Are the bugfixes and updates simultaneously pushed to the itch.io version of Grimoire when the steamtard version gets them?

 

[Cleveland Mark Blakemore]

GoG was right in not publishing this shit. Your game sucks ass. Die in hell.

Are you one of the 0.1 hours reviews? How is Anita these days since she ran out of money?

 

[Cleveland Mark Blakemore]

Cleve, I was able to reproduce the weird scaling/cropping issue some users were complaining about on Steam forums. The culprit is DPI virtualization introduced in Windows Vista.

Ah yeah, i had the same issue with my own engine getting zoomed in. The fix is trivial, just call SetProcessDPIAware from user32.dll right after your program starts (in WinMain). In my engine i call that via LoadLibrary and GetProcAddress so that it works even in older Windows versions (also i'm mostly using Borland C++ 5 released in 1997 which has no idea about such things so i have to load any new stuff dynamically :-P), but according to Microsoft docs this is supported since Vista so if your minimum requirements (...and compiler :-P) include that you can simply use it directly.

That used to be in the code a couple years back. I think Shams recommended it. It was sitting in there until about 2014 when I began my final code cleanup to release it. I deleted that line when I looked up what it did.

I took it out, thinking it just more fluff trying to hitch a ride on the mean, lean Grimoire machine of basic vanilla Windows old school.

So there. I admitted it. Shams recommended it, I took it out. I messed up. I'm sorry I cannot keep up with every new version of Windows writing out fake data to fool older versions. So it appears all these scaling problems on some machines are my doing.

This is another reason I am so glad I have moved to Unity where all these issues are handled by the backend rendering engine.

EDIT : Just tried it and it fixed the problem on one of the test machines. Seriously, I really appreciate it. At least this problem will be finally fixed in the next release coming up.

EDIT #2 : ... and SetProcessDPIAware sounds like a neckbeard gay sex function stuck into Windows just to make millennials feel extra special. Can you blame me? Do you know how many of these fluff commands you could stick into your code just to try to cover every eventuality? You can just see the Microsoft guy who wrote that command chugging a monster through a hole in the wall at the local rest stop on the highway.

 

[Solanacean]

and SetProcessDPIAware sounds like a neckbeard gay sex function stuck into Windows just to make millennials feel extra special. Can you blame me?

No one is blaming you, Cleve. Certainly not me. I appreciate all the hard work you've been doing and have a deep respect for you. Please consider using assembly manifest file with dpiAware property set to true rather than SetProcessDPIAware though. It does the same thing but it's safer, cleaner and is recommended by Microsoft.

 

[biggestboss]

I'm going to buckle down and force myself to beat this game. I played this back at release having paid the full price for incline, but stopped after one of Cleve's patches destroyed my save file.

Time to stare at character creation for a couple of hours.

 

[Lady_Error]

Time to stare at character creation for a couple of hours.

The science of Grimoire character creation described in detail:
http://grimoire.wiki/index.php/Races
http://grimoire.wiki/index.php/Classes

 

[Solanacean]

I hate to say this, but I believe there's a big fat problem with Grimoire's rendering code: it doesn't seem to be thread-safe at all.

 

[Dorateen]

On this second anniversary of Grimoire Release Day, I wanted to once more praise the quality of the art used for the area transitions. Each screen is atmospheric and evocative of what the party is about to encounter. These images have never failed, not once, to color the tone for every new location.

Breaking Ahriman's hold on Kublai Axis and restoring the Khan Raji to power was one of the greatest triumphs I've enjoyed in any computer role-playing game.

 

[luj1]

That used to be in the code a couple years back. I think Shams recommended it. It was sitting in there until about 2014 when I began my final code cleanup to release it. I deleted that line when I looked up what it did.

I took it out, thinking it just more fluff trying to hitch a ride on the mean, lean Grimoire machine of basic vanilla Windows old school.

So there. I admitted it. Shams recommended it, I took it out. I messed up. I'm sorry I cannot keep up with every new version of Windows writing out fake data to fool older versions. So it appears all these scaling problems on some machines are my doing.

This is another reason I am so glad I have moved to Unity where all these issues are handled by the backend rendering engine.

EDIT : Just tried it and it fixed the problem on one of the test machines. Seriously, I really appreciate it. At least this problem will be finally fixed in the next release coming up.

EDIT #2 : ... and SetProcessDPIAware sounds like a neckbeard gay sex function stuck into Windows just to make millennials feel extra special. Can you blame me? Do you know how many of these fluff commands you could stick into your code just to try to cover every eventuality? You can just see the Microsoft guy who wrote that command chugging a monster through a hole in the wall at the local rest stop on the highway.

What happened to Shams? Is he still around?