WinAGI v3.0.0 BETA is now officially AVAILABLE!

[Paladinlover]

I made a thread about this and I should have posted it here...

Any way I can run this on Linux Mint? Wine and Bottles isn't working, or maybe I need the settings.

Thanks for any help.

[AGKorson]

I guess no news is good news. I recompiled Tonight the Shrieking Corpses Bleed and played through it fully. Nothing seems to have broken. I should do the Tex McPhilip games next.

Thx for the feedback. Did you find anything else that you can comment on- anything with any of the editors or tools?

[bokkers]

I'm late to the party (as usual), but wow! Installing it right now, high hopes that will help me speed up graphics creation for my current project. Will post feedback as soon as I have it up and running. Already a massive thanks for making new stuff for AGI developers in 2026!

EDIT/ADD:
Installed it, poured some .net framework into the pan, and it works like a charm. Opening my current project, it throws 48 warnings concerning my sloppy copy-paste-and-then-some scripting attitude, nice! Sound editor is so refreshing. About the pic editor: I am a sucker for dithering, always losing time by drawing tons of diagonals. How can I speed this up with WinAGI? Automated dithering maybe? Just copy and paste of certain dithered regions would also help me. Any quick advice maybe? Guess I'll hit the documentation now.

Great work mate! Very refreshing to give DOSbox a little rest, and have everything under one roof now.

[AGKorson]

I'm glad it's working for you. So far no major errors or issues? That's good to hear.

I've done some dithering myself from time to time, and you're right- it can be time-consuming. I will look into adding a dithering tool. I think it can be done relatively simply. It may take me a while to get it up and running though.

[bokkers]

No errors or issues at all. (Windows 10, 64bit version with the latest updates, on an HP laptop) After installation I got pointed to the .net framework version I needed, just had to click the download link, smooth and easy. Thanks for looking into the dithering thing! A dream tool would be to be able to flood-fill a colored surface with the second dithering color.

I understand the copy-and-paste feature for the pic editor now, and that is already a very good step forward. I love the dithering method as it pushes the look slightly into SCI territory.

Will do some scripting in the coming days and post feedback here. Cheers from the bakery!

[vapidlapwing12]

There were two things I spotted with the beta - first, when working on a picture, I found it very useful in the previous version to scroll through the command list and see the picture update as I scroll. In the new version the picture is only updated when I stop scrolling.

I think I see what you mean- when holding down an arrow key, in 2.3.7, the picture updates as each draw command is selected; in v3, it only updates when key is released. Is this what you mean?

I can look into that- I should be able to restore that behavior.

That's exactly the thing, thanks!

The second thing (and it's really minor) is that the increased font size and extra whitespace in the command list means you can't see as many entries

Not huge problems by any stretch, but I found the earlier version to be a little better in those respects at least.

I see what you mean. In v2.3.7 the font for forms and controls is MS Sans Serif and can't be changed. In v3, I have added the ability to change the font for forms and controls (which is the same font used for previewing logics, which can be changed on the Logics tab on the Settings dialog. The default is Consolas. I also restrict the available fonts to only mono-spaced fonts otherwise the preview text box won't work correctly. In addition to the Picture Editor draw commands list, other controls that use this font include the resource list, word editor, object editor, view editor list and several others.

The controls used in v3 also add some extra padding to the listbox items; not sure I can control that - it's a VS/C#/WinForms thing.

You could try choosing a different font/font size on the Settings dialog. Consolas at 10 pt or even 9 pt are a closer match to v2.3.7.

I could also see about using different fonts for the logic previews and forms/controls; then you could choose non-monospaced fonts for the forms and controls at a smaller size but still leave the preview logics as monospaced and at a different size as needed/desired. Let me know if you feel strongly about it and if so I'll see what I can do.
[/quote]
I didn't realise there was a possibility to change the fonts - I'll give that a go. Thanks again!

[AGKorson]

OK, v3.0.0-beta.39 is now available (see link in first post).

Notably, it adds the updating-on-scroll feature for picture editor requested by vapidlapwing12. And it adds a dithering tool to the picture editor requested by bokkers.

[bokkers]

Wow, that's amazing! Just seeing this now. Thanks so much, gonna hit the update right away!

[pabuslem]

Hey, everyone!

Andrew, first of all, I want to thank you and congratulate you for the great amount of time and effort you've put, and continue putting, to build such a amazing tool as WinAGI is.

I began using the 3.0 beta 39 version and I have to report an issue. I've created new games using AGI versions 2 and 3 (I haven't tried the PowerPack nor the SierraSyntax versions) and everytime I try to import a View resource, it gives me the "Something went wrong. Unable to load View(View_number)" pop-up window.

I've tried to import View resources from "King's Quest III," "King's Quest IV" (AGI version), Larry 1, "Police Quest," "Space Quest" and "Space Quest 2," and it gives me that error or another one every single time. When I try to import Picture resources, it works like a charm every time. I haven't tried importing Logic nor Sound resources.

I've done the same tests in WinAGI 2.3.7. version, and it imports both Views and Pictures flawlessly every single time.

I'm using Windows 11 Home edition, 64-bit, operating system, build 26200.9168.

I hope this information comes useful to fine tune an already superb tool!

Cheers!   

[AGKorson]

Sorry about that. The error message is not very helpful- I should have included more information as to why it failed.

I can't seem to replicate the issue. Can you describe exactly how what you were doing to get this error? Did you use the Import View menu, or the Import View toolbar button? After selecting the imported view's filename, did you choose the 'Open new resource for editing' option? If so, have you tried NOT using that option? Does it happen after you've done other things to the game (after creating a new game is importing a view the first thing you tried, or did you do anything else?)

Can you use the Details option on the second error message and provide me all the data from that?

Beta.58 is available (see link in first post above). I added additional information to the error message that should help me understand what's going on. Can you try again with version beta.58?

[pabuslem]

Hi, Andrew!

The error happens when I go to "Resources," "Import Resource," "View" in the main Window of WinAGI, right after creating a new template game, or after opening that new created game. It happens whether I choose the "Open new resource for editing" option or not.

I couldn't replicate the error window with the Details message, but I managed to get it after choosing the button "Open Don't Import." I copied all that text in a text file, which I'm attaching. I'll try the new beta version (.58) and tell you what happens.

Thanks again for your work!

Cheers!

[pabuslem]

Hi, Andrew!

I just wanted to let you know that WinAGI 3.0 beta version .58 is running flawlessly for me, so now I'm able to import both Views and Pictures.

I'm sorry I hadn't tried the most recent version of WinAGI 3.0 beta.

Cheers!

[AGKorson]

That's great to hear. I'm glad you're up and running.

I think I know what was causing the second error (the one complaining about the NullReferenceException)- I made a change to support a new (to me) form of loop mirroring, but missed a check that resulted in attempting to access an object that wasn't set yet. I fixed that in beta.48.

Still a little unsure about the first error though (the one saying 'Something went wrong'). I'm not sure how that could occur. But if it does come back, hopefully the updated error message will be more useful.