A new version is available on Steam and TGC servers.

This should resolve problems when broadcasting.

Thank you

The TGC Installer for this version thinks it is installing v2021.10.11 but the version installed is actually v2021.10.19. All very confusing.

@Orvillian this probably needs adding to your check list if it isn't already on there.

I get "Invalid depot configuration" when trying to update from Steam.

@adambiser what platform are you installing AppGameKit on?

@Orvillian: Windows

EDIT: Looks like it's working now.

Orvillian

It says

v2021.10.11

Ummm, think I'll wait, I'v done nearly a gig of data on AppGameKit updates this month call me when the LTS is ready!

The latest updates have certainly been lacking a bit of quality control and testing!

The latest updates have certainly been lacking a bit of quality control and testing!

This update had some very significant changes under the hood that would be difficult to sort out (or even encounter) prior to a broader release. And there may be some internal development changes taking place that could further explain it. Happens all the time with software. I for one am pleased with the continued support and response time in getting reported issues that did surface after the latest updates fixed across two separate product lines as quickly as they were. So thanks Orvillian and any others involved, your efforts are very much appreciated.

@SFSW I completely agree with you about the amount of effort that has been put in on these updates and the quick response time and I really appreciate that Orvillian is continuing AppGameKit development now that Paul is working on Gameguru max.

My comment about quality control was because the latest TGC releases have the wrong version numbers, files not signed and something as fundamental as the broadcaster not working etc. These are not difficult things to pick up before releasing a update and did not need a broader release to identify.

The only change that may have been difficult to detect internally was the Java path.

My comment still stands "The latest updates have certainly been lacking a bit of quality control and testing"

Point well taken. I'd agree on the version number and broadcaster, that could get missed or assumed operational when going from one line to the other. I'm sure it'll be accounted for in future updates now. Coming new into a project, it can be difficult to automatically know the dev environment, settings, etc, so something like unsigned binary's could easily be missed since testing against a bunch of A/V solutions wouldn't be very practical and local tests would all work fine. That's also likely part of the update roll out plan now, so here's hoping it's smoother sailing from here on out

Yes, Orvillian appears to have been dropped into the deep end with the Appgamekit updates and I'm sure that the next updates will go more smoothly.

I can't find the "linux" section on OS-related so i'll drop it here : since i updated (i run the system offline mostly due to paranoia) steam + appgamekit on linux i get the error described here

https://steamcommunity.com/app/325180/discussions/0/3086646248551443403/

here is a link to a steam support page in the error message and I have tied everything in it. I have a file called geany in the folder that my file manager say is a shared library but no geany64.

its been 13 days but b/c i'm only online sporidally to update the elder dev-rig i only noticed today

starting geany manually does not help

and after two weeks there's no fix ...

??

anyone ?

should i just can it until fixed or is there a way to rollback to a version that works ?

is there a way to rollback

find Classic in your steam library then Manage (settings/gear icon, lower right).
then Properties>Betas and select a previous version from the pulldown menu, there.

The Linux version on Steam looks for "geany64", but there is only "geany".

@Virtual Nomad

lifesaver

rolling back to v2021.07.14 it boots geany .... now heaven can wait, thanks !!!

the "real" release thread (vs this patch release) is getting buried; see Classic Version 2021.10.11

The Tier 2 templates still require VS 2017 and SDK 8.8, which is silly when SDK 10 *which includes 11) is available. Yes, it's easy to change those requirements in the VS Properties for the solution and save the template, but really updates should reflect latest practice.

It would be enormously helpful if the .lib files for Windows could be provided as a stdcall DLL with unmangled names. That would massively broaden AGK's scope for use in languages other than C++, which I personally abhor. Or, at least, producing an OMF library for static linking would be helpful.

It would take the development team about five minutes to do either of those. The required interfaces can easily be generated from the .h files for any other language.

Any chance?

Finally got it to work.