Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - AGKorson

Pages: [1] 2 3 ... 23
1
Beta.4 is now the current build. Fixes several errors with creating new games from templates and toggling Include file options.

2
Minor error from me - the .msi file is called "WinAGI.installer.msi" but setup.exe is looking for "WinAGI Installer.msi".
I can change that to eliminate the space, which I just noticed is being converted to a '.' when the file is uploaded to github.

Slightly bigger error - when opening a previous .wag file it updates the logic files and places those in a backup folder, but copying those files back into the src folder is giving me a "invalid or corrupt game property file (AGI.wag)" in WinAGI 2.3.7.
This is by design; updating to WinAGI v3 changes the WAG file, and v3 game projects are not directly compatible with v2 game projects. The change is minimal, mostly adding and subtracting several different parameters. If you want to change it back to a version 2 project, you will need to edit the WAG file with a text editor, and change the "WinAGIVersion" property in the [General] section from 3.0 back to 2.3. Your WAG file may have some extraneous entries that version 2.3 won't use, but they can be safely ignored and the project should then open in version 2.3 again.

3
Beta.2 is now the current build. It fixes several issues with filenames not working correctly, namely the NewGame, OpenGame and ExportResource functions. Link in the title post has been adjusted.

4
Sorry about that. I didnt' realize the build was targeting ARM instead of x86. Turns out that lets it install on a Surface laptop (which I use for development), but not on other Windows systems.

I recompiled and rebuilt the installer. It should work now. Can you please try it again?

thx,

5
I forgot to mention one of the biggest additions to this version- it is 100% compatible with original Sierra syntax. It will compile all the original source code that has been made available. So if you want to go retro and program like it's 1985, WinAGI is for you.

6
Here it is at last:
https://github.com/AGKorson/WinAGI-GDS/releases/tag/v3.0.0-beta.4
(edit: this should work on all Windows systems now)

I would greatly appreciate any feedback. Feel free to either post an issue to the git page, or leave a comment here on the forum.

7
AGI Development Tools / The Plot [Pen Style] Thickens
« on: March 25, 2026, 03:18:30 AM »
I'm almost ready to release the Beta version of WinAGI 3.0. Just a bit more code clean up and a few more tweaks on the Help file.

As part of working on the Help file, I've gone back to the decompiled code to make sure I have the most accurate information possible on AGI's resources, commands, and functions. I've discovered quite a few more bugs (mostly only noticeable in specific edge cases). But the one that really surprised me the most was the evolution of the Plot Styles.

It's well documented that the Plot command (0xFA) for pictures was added in version 2.411. In that initial version, the Plot Style command (0xF9) was ignored; using it in that version did nothing, and all plot commands drew as a single pixel.

In version 2.425, Sierra added support for the Plot Style command. But it came with three bugs:
  • The pen was not reset before drawing a picture; this meant that if another picture was drawn later, the starting pen would be the last value from the previous picture, not the default of solid circle of size zero.
  • The algorithm to calculate the brush placement had an error which resulted in the larger brushes being off-center.
  • The mask data for brush size 1 was missing the bottom row of data, so circle brush size 1 was not drawn correctly.





In version 2.426 the pen reset bug was fixed, and the circle masks were refactored, but the circle 1 brush was still missing data. This affected the shape of circle 1.


In version 2.435, the brush placement error was fixed, but the circle 1 bug remained.




The circle 1 bug was fixed in version 2.439. The rest of the version 2 AGI releases all used the correct brush size and shape.


In version 3.002.086, the circle 1 brush data was changed again, but it was done incorrectly, resulting in the brush shape once again being incorrect.

The incorrect circle 1 brush remained the same for all version 3 releases.

It was a big surprise for me when I discovered all this- I had always assumed there was just one version of the plot brushes. But since most fan games probably are only ever run on modern interpreters (or are using the more common late v2 interpreters when using DOSBox) I guess it's not too surprising that this has not been noticed before.

I am now very curious to know if there are any older Sierra games that used the plot commands in the versions with different brushes; are there some that are being drawn incorrectly in modern interpreters when compared to their original release? I'm guessing there aren't that many Sierra games released that used the affected plot commands often enough for the error to be noticed.

Regardless, I do plan on adding the option to use the version-correct brush sizes when drawing and displaying pictures in WinAGI. It'll give a true representation of what pictures would look like if they are used in the original Sierra AGI version they are targeting.

8
AGI Development Tools / Re: WinAGI Version 3.0.0 Progress Updates
« on: January 31, 2026, 10:15:48 PM »
I believe I'm finally done with adding support for original Sierra logic syntax. I have tested it on several different sets of original Sierra source code packages and they compile as-is, with no changes needed.

https://github.com/AGKorson/WinAGI-GDS/releases/tag/v3.0.0-alpha21.3

This work required a lot of digging into CG.EXE- Sierra's compiler. CG.EXE does not do a lot of syntax rules enforcement. I guess they just assumed their programmers would write good code. To maintain 100% compatibility I had to add some of that 'looseness' to WinAGI. But it does provide you with feedback on how to write cleaner code.

The help file contains very detailed explanations of CG.EXE, OBJECT.EXE and WORD.EXE, tools used by Sierra to compile logics, OBJECT and WORDS.TOK files. You may find that interesting. Or maybe not...

Regarding DLL calls, WinAGI uses them primarily for supporting custom clipboard formats and sound generation. At this point, I'm not very interested in figuring out how to make a build that doesn't use them. If anyone else wants to take a look and make some suggestions, the code is on Github.


9
Everything-Else / Re: What's up peeps!
« on: January 28, 2026, 07:00:12 PM »
Still working on WinAGI v3. I was hoping to have the beta release out by now, but as I continue to work on the Help file, I keep finding more and more things that need fixing or refactoring, especially older code when I was first starting. I do see the light at the end of the tunnel though, so hopefully it'll be done soon.

10
Why is this topic pinned?

11
AGI Development Tools / Re: WinAGI Version 3.0.0 Progress Updates
« on: January 10, 2026, 05:49:16 PM »
There are a handful of API calls. Most were added early when I didn't have much experience with C#. I've gotten much more efficient since then. I can take a look at them to see if they can be eliminated.

12
AGI Development Tools / Re: WinAGI Version 3.0.0 Progress Updates
« on: September 25, 2025, 02:19:25 AM »
Text screen editor is done. All code from VB6 version has been ported.

https://github.com/AGKorson/WinAGI-GDS/releases/tag/v3.0.0-alpha21.0

Now I'm working on integrating help, and doing a lot of code cleanup and refactoring. A Beta release is just around the corner.

13
AGI Development Tools / Re: WinAGI Version 3.0.0 Progress Updates
« on: September 02, 2025, 03:23:28 PM »
Layout editor is complete. Only the menu editor and text screen editor are left. Those shouldn't take too much longer.

https://github.com/AGKorson/WinAGI-GDS/releases/tag/v3.0.0-alpha19.0

14
AGI Development Tools / Re: AGI AI Agent
« on: September 02, 2025, 03:10:54 PM »
That's pretty cool!

You should give your project a name. Might I suggest Artificial Larry - 'AL'. (An homage to Larry's creator!)

So how do you expect AL to improve? Do you have to change the interface, or is it just a matter of letting the AI just keep trying? As the AI learns, where does its new knowledge get stored? If someone else was to try the same thing, would the AI remember what it learned from your project?

15
AGI Development Tools / Re: WinAGI Version 3.0.0 Progress Updates
« on: August 06, 2025, 02:07:28 PM »
Layout editor loading/saving/displaying is done. Now working on editing functions. Continuing to fix bugs throughout as I find them.

https://github.com/AGKorson/WinAGI-GDS/releases/tag/v3.0.0-alpha18.1

Pages: [1] 2 3 ... 23

SMF 2.0.19 | SMF © 2021, Simple Machines
Simple Audio Video Embedder

Page created in 0.039 seconds with 19 queries.