Number Six

Can you give us any details other than "Doesn't support it". The only reference to this I could find on the forums is this: However there doesn't seem to be much there beyond "it doesn't work, use safe mode". Can you provide some details about exactly what you've tried and what happens? Doesn't show up in the controller list? Shows up but doesn't respond to input? Buttons don't map properly? Something else? We need detailed information to have a chance of solving the problem.

Is it on sloped / irregular terrain? The one remaining thing that can cause the AI to close to the target's actual position is if it loses line-of-sight (it will abort and stop if a power becomes available for use before it gets there, but that doesn't always happen due to power recharge or wonky geometry in the way).

The beta server is getting its own manifest so that people who aren’t interested in it don’t have to download the files whenever there is an update, letting us do updates to it more frequently without having to take that into account. Final verification is in progress and the link will be posted shortly.

It's in the registry, under HKEY_CURRENT_USER\Software\Cryptic\CoH

Without a dump I can't tell which one, only that the code path is login screen -> text block -> font rendering -> texture atlas. It would be one of the ones in the pigg files -- not a system font. If you've already tried a fresh install, I'm not sure what could be causing that.

Based on the stack trace, you've got a corrupt font file somewhere. Have you reverified files? Also the crash handler isn't running, so there's probably antivirus or something interfering. That might also prevent all the files from downloading.

Exit the client completely? Those aren't saved anywhere except memory.

Yes, that stack trace tells me that it's a corrupt texture swap list in a scene file, which probably means a malformed scene file. Do you have any overrides in the 'data' directory? Make sure there is not a data\scenes folder under your COH install. You may want to try deleting homecoming\scenes.pigg, and if that doesn't work, piggs\misc.pigg and letting them get re-downloaded.

Check and see if you have the icon for a day job in your buff bar -- when you're in the day job volume for a university or police station you should get the zero countdown. It may be the case that the volume doesn't cover the entire interior.

Check and see if you have a “Crash” directory under your CoH install. That’s part of the new crash reporting feature - we haven’t turned on the upload feature yet until the lawyer-approved privacy policy is in place. But the report files are still saved there and if you can manually get the contents of one it may help track down the cause of what you’re experiencing.

Yes, you actually need the 2017 runtime, but 2015, 2017, and 2019 are all the same download. Make sure to download the "x64" one.

Even Paragon dropped support for older operating systems at some point -- I remember some yelling when they dropped Windows 2000 support and updated the minimum requirements to XP Service Pack 3. We're not even doing that. We're attempting to maintain support for those older systems, and have jumped through a lot of hoops to do it. The 32-bit client is built with newer tools, but built in a way that it should be compatible even on XP and old versions of wine on Linux/MacOS. That's the compatibility path going forward, while the 64-bit client is intended for newer systems. Unfortunately we don't have the resources to actually test on all of those old systems, so sometimes things break and I understand that's why some people are still running the legacy ("safe mode") client. What we need from those people is to stay engaged, make sure we know that they're having problems (some of you are already doing this, thanks for letting us know!), and help in tracking down the issues. Right now it's a manual process, though once the new crash handler is fully rolled out and activated there will be an easier way to gather data from those who choose to opt in.

What happens when you run the 32-bit version on XP? It's not really officially supported, but we do build the 32-bit client with XP support and it was working a while back AFAIK.

If you're still using the safe mode client and unable to get the 32-bit client to run, please post what OS version you're running, what version of Island Rum, etc. We need to try to get these resolved as soon as we can, as maintaining the legacy client is holding back some features.

Removed the hard limit, and the soft limit. MAX_COSTUME_PARTS is gone, so unlimited lag costume parts here we come! In all seriousness, the first application of this tech will probably be something boring like fixing the customizable weapon slots that conflict with customizable epic pool weapons. That was the primary motivation for removing all the hardcoded limits to begin with; extra auras are just a bonus. Then maybe separate path auras out. I also have some ideas for how to do things like eye/hand auras in a sane way to allow them to be set independently without overloading the costume UI, but that's a bit further off because it involves reworking the costume creator a bit, and the way I'm thinking about doing it actually wouldn't have required expanding the part limit.

Yeah, a whole month is too much I think. We have some ideas for next year to make the event more dynamic and less of a drag, while still providing a large window of opportunity for players who can't log in every day to participate.

Minor font rendering differences are probably a result of upgrading the FreeType library the game uses from some ancient version that was last updated right around never ago to the current version. But that wasn't in this patch, it's been out since at least the one prior to it. IIRC FreeType changed at some point to autohint (snap to pixel boundaries) vertically but not horizontally, similar to ClearType and other technologies that take advantage of subpixel rendering.

That’s something @Cipher was working on... he showed me a prototype of an HSL picker a couple months ago. There’s a few niceties we would want in such a tool, such as remembering color swatches already used in the costume for easy matching. The UI code is a bit of a pain to work with so I think it got backburnered while we deal with some other things that need attention. But I’m sure it’ll come back to the forefront at some point.

Certainly doable. I was playing around the other night and did this as a silly proof of concept. Took a few hours because I had to rework the database schema to remove the hard limit on 30 costume pieces and fix the absolutely awful way they were stored in the database, but now we can add as many as we want so that opens up a lot of options. As you can see taking things too far makes the UI a little... difficult to see... so some careful thought will have to be placed into the best way to have maximum flexibility and still have it be usable. Maybe splitting off path auras into a separate slot for starters. Ideas are welcome.

The link you posted is for the Visual Studio 2010 runtime, which is an older one that won't work. We're using VS2017, so you need the first download on this page: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads Make sure to download the 64-bit (x64) version.

Also wanted to try to avoid confirmation bias in people reporting whether or not it helped with the crash issue, but okay, point taken. Edit: There, done. 😉

It would quite literally be the “bug fixes and performance improvements” patch note that everybody hates on mobile apps. The only change is a minor adjustment to particle physics to try to prevent the crash to desktop issues a number of people are experiencing. But since we don’t have any good method of reproducing the crash, it may not actually fix the issue. So... no visible changes = no patch notes.

The pre-ED values are useful for knowing how much enhancement value is being wasted and can tell you if you've overslotted a particular attribute.

If there is anyone who is consistently experiencing this crash, is comfortable enough with file management to drop in a test client, and is willing to help us out by submitting crash dumps, please shoot me a PM.