Number Six

Yes, the Issue 25+ engine has a lot of improvements specifically in order to make things like this possible. You'll notice the power customization screen has a new "Inherent" section that is was not present on live or the I24 beta, though there are not yet any powers that take advantage of it. One of the reasons the Paragon devs never did that was that UI work is a huge pain, but that part is done now. It would just be a matter of some Fx work to make a tintable version. There have been some internal discussions about this, as well as the idea of combining all of the prestige sprints together into a single power that you can select from the different effects (to reduce power list bloat). That causes some controversy due to the loss of the "free" enhancement slots so it's been tabled for now.

My opinion is that code should never be used as an excuse. Not to pick on this instance in particular, but there are a lot of people who quote the standard code rant in various threads and it's a bit of a pet peeve. I see a lot of assertions about things being "impossible" that are clearly not, like fixing the Pet AI without having to use hacky workarounds. On the other hand, there are a lot of things that we technically can do, but it doesn't necessarily follow that we should do. Per-AT aggro caps are technically possible with a small amount of work, but I'm not convinced that they're a good idea. The cap exists for a reason -- if you are fighting very large groups then everybody has to think about aggro management and survivability a little, and you can't completely ignore the mechanic by bringing a tanker. IMO any discussion over such a thing should be focused solely on whether or not it makes for better gameplay and is likely to produce a better result than keeping the cap uniform, considering all aspects of what makes a good game.

Oh, I meant even if it's just a link to the PDF, something that would be at the top of the thread instead of partway through that people have to dig for. i.e. just create a new topic here (https://forums.homecomingservers.com/forum/12-help-amp-support/) with the PDF in it, something like Mac OS X Guide for upgrading from Safe Mode, and I'll pin it there so that it's more visible. 😀

Do you have a standalone thread for this somewhere? It might worth putting in the tech support section so we can sticky it as a guide for people who can only run safe mode to try.

Can you try the beta client (https://forums.homecomingservers.com/topic/13159-how-to-access-the-beta-testing-server/) and submit a crash report when it pops up? That ntdll.dll reference doesn't provide any useful information, so we'll need a full stacktrace or even a dump if possible to see what the issue is.

You probably used the driver shim workaround for older Intel integrated chips on the safe mode exe. You just need to run through the same procedure except for the correct “cityofheroes.exe” in either hc-bin64 or hc-bin32, depending on which version you’re trying to run.

Same issue a lot of people are seeing of the launcher (Island Rum?) apparently passing in a -patchdir parameter to a directory that doesn't exist. After trying and failing to launch it, do you have an islandrum.sh file somewhere in your COH directory that you can paste the contents of?

Ironically, it was apparently dev signing that caused the hang (the only thing that was changed in the fixed version was removing the signature).

Please try redownloading it again. Manga had updated it with a version that has a certificate so that it doesn't break at the end of the month when Apple starts enforcing app signing, but it seems to be hanging on random machines. A version without the cert removed was just re-uploaded and seems to work... (but will break on Feb 2).

Are you able to find any log files in ~/Library/Logs/Time Sync/Island Rum? Manga says that should have a detailed activity log and may provide some clues about how it's being launched.

That one is an easy fix: Download and install the "x64" package from Microsoft. https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

Not in keymapping, what happens when you click on the controller device option to select it under "Controls"?

I'm not sure if that will solve it. The message you're seeing is just a warning, not a fatal error, and the game is switching to Windowed mode. So if you can't start it even in windowed mode, I doubt any of the fullscreen options will work. Try adding -console to your startup parameters in the launcher and see if you can screenshot the top of that console window where it shows specs and video card information.

Oh, okay, the black screen. We're going to need to get console output (from running the game with -console) somehow to see how far it gets before that screen appears. I've tried a few things with one other person I'm working with on a different issue, but so far have not had any luck getting the console window to appear on Macs. You'll probably need to engage one of our resident mac experts to try and figure out how to do that (@GM AmonRa) if possible.

There were a couple bad versions of wine that had input issues on all clients, but it was corrected in future updates, and it shouldn't just spontaneously revert to that version. @Mangawould know more about which versions of wine Island Rum is currently installing.

I don't think that's accurate, @Tahquitz. The 32-bit version of wine is broken, but wine64 does work on Catalina, and there are several players who successfully run the 64-bit game client using it. That was a big part of the push to modernize the code and make it 64-bit clean.

Can you elaborate on "don't recognize"? It doesn't show up in the list when you go to controller options to enable it? Or shows up but doesn't work? I'm really surprised your friend is having problems... the 64-bit and 32-bit clients have native support for xbox controllers using Microsoft's preferred API for them, and as a result have extra features like vibration support exclusively for xbox controllers that the legacy client (safe mode) lacks.

Have you tried borderless mode? That lets you select the monitor up front and runs full screen (but technically as a window) at your desktop resolution.

Controller/Dominator pets are on the board to be looked in phase 2, after the MM changes go live.

It will be going away at some point, but the reason for moving it to a separate manifest was to get a feel for how many people are using it and get them to report what issues they're having, so that we can work on fixing them before it goes away. The specific one you're running into seems to be related to the way it's being launched on older versions of MacOS (10.12 and earlier). I'm in contact with one other person who's experiencing the same issue and is working with me to try and pin down whether it's a problem with the game client that we can fix, or if it's a launcher issue we'll need to get the Island Rum author to address.

It's very similar in Island Rum. There should be a place to put a manifest URL somewhere in the options -- paste "http://patch.savecoh.com/safemode.xml" there.

Use the safe mode manifest from the first post in this thread. What version of MacOS?

Once we have a firm cutoff date, the safe mode client will be getting annoying pop-ups that have to be acknowledged every time it's run. So there will be ample warning.

For people who are building a budget machine: While NVIDIA cards usually work better, a 2-year-old Ryzen 3 2200 with integrated Vega 8 graphics runs the game quite smoothly. You can't turn on all of the fancy ultra mode options, but can get the important ones and for a casual player it works just fine. AMD graphics drivers aren't as good as NV's but are a lot less of a headache than say ... Intel's.

I looked at your latest crash report and it's in the PhysX DLL again, which means we have zero visibility into what's going wrong. There doesn't seem to be anyone else that I'm aware of suffering from the same issue, so the most likely cause is something system-specific that's interfering with it. One difference between the two is that the 64-bit and 32-bit clients use a slightly newer version of PhysX that is supposed to contain bug fixes. However the old one should be compatible, so I'd like to have you try copying the older physx DLLs from the root of the COH installation into the hc-bin32 directory and running the 32-bit client to see if it makes a difference. That will be somewhat difficult since Tequila annoyingly overwrites modified files every time you run it, so it will take setting up a shortcut to run it without the launcher for testing.