UpDEnhanced support thread

[jharp]

In recognition of the issues with 4.6.0, I have lowered the price by 33%.

Get your whole party to be protected from updates until you are ready to face it as a group.

Jason

[Morenu]

I have been stuck on this screen for 20 minutes (I did restart a full update and then downloaded and reinstall the 1.07 file from Github)
Update.png

[jharp]

I have no idea why i dont get emails for these posts. I'll take a look.

Jason

[jharp]

I have no idea why i dont get emails for these posts. I'll take a look.

Do you own a license?

Jason

[jharp]

If you own a license then I will need some logging. If you don't own a license then it is supposed to popup a window that says you need to buy a license. Obviously, that is not happening.

If you own a license then please locate the following file - ...\FGUpdaterEngine\BepInEx\config\BepInEx.cfg
Edit this file so that under [Logging.Console] it is:
Enabled = true

instead of the current :
Enabled = false

When you run the updater the next time, a console window will appear. Please DM that for me to review. That log does contain some private information, including what products you own so a DM is likely the best approach.

Thanks,
Jason

[Lo Zeno]

I have a suggestion for a small enhancement, if you want to consider it:

At the moment, after clicking "Update...", the next window has all the modules/extensions/dlc/core components listed and grouped in 4 groups (Core, Base, Purchased, Forge), but unless the user expands each group and scrolls through them looking for the rows where the build numbers are in yellow (where build latest doesn't match build local) they don't know if anything actually needs updating; if possible, it would be useful if the group name itself would turn yellow if at least one element inside that group is yellow (= needs updating), for example if no ruleset under Base needs updating the Base name stays black, if instead the 5E ruleset needs updating then the Base name is yellow.

It's not a massive change, and it's not like it's necessary, but it gives a nice immediate feedback when opening UpDEnhanced since if all the group names are black then the user knows immediately that there's no actual update to do, and if only one or two modules have updates they don't need to expand all four groups but they can go and expand only the ones that are marked in yellow. Saves a tiny bit of time.

[jharp]

i like the idea - i will try to implement.

jason

[jharp]

i still like the idea and will look at it.

However, i reread your post and i think you may not realize that you can sort the columns by clicking the column header you want to sort. To find updated items quickly, click the match column header. It will sort those by seeing which are out of date.

Hope that helps.

Jason

[Lo Zeno]

You're right, I wasn't aware of it. Likely because there is no visual cue of the fact that clicking the columns makes them sort the data - cue that does appear, in the form of a triangle up or down, right after I click one.
That might be another small QoL/usability update

[jharp]

Version 1.0.9 is out on github.

- Fixed hang when you have multiple copies of a product.