Some number of PC players may have booted up Namco/Bandai's recently-released Ace Combat 7 on PC, only to be disappointed to find that their preferred flight stick doesn't work with the game. Un-supported controllers apparently includes the very popular (and very expensive) Thrustmaster Warthog. This isn't a technical issue; it's a hardware-exclusivity deal that Namco/Bandai apparently signed with Thrustmaster and Hori. Only two flight sticks are supported by the game: the Thrustmaster T. Flight and HORI AC7 flight stick. Apparently, the same restrictions apply to the PS4 and XBox One versions of the game

If you're like me, and don't play a lot of flight sims, any flight stick that you have is likely old and obsolete. But you probably still hoped it would work with the game. It's PC, after all, and controllers are mostly plug-and-play. Worst case scenario, you'd have to custom configure the control mapping. Right?

Not so. If the game detects a flight stick that isn't on its approved list, it apparently refuses to recognize it.

I'm not exactly a huge Ace Combat fan, but Ace Combat 4 (which I played on PS2 back in the day) is on my short list for "favorite games ever". Perhaps I'll put up a retro-review of it at some point. Needless to say, AC4 was a near perfect hybrid of acrade dogfighting and realistic flight sim, and it's nuanced depiction of war might make it my single favorite video game about war -- except for maybe This War of Mine.

So I was excited that a new game was coming out. I had bought a Logitech Attack 3 flight stick some years ago for another game, and I was also excited to see how Ace Combat would feel with a flight stick instead of a game controller. So I bought the game on PC expecting the flight stick would work. It didn't, and I was pretty bummed. I bought the game on the weekend of its PC release, and when I found that my flight stick didn't work, I shelved the game and went back to Resident Evil 2 and Civilization VI: Gathering Storm. I figured I'd come back to AC7 in a few weeks, at which point, the flight stick situation would hopefully be resolved, or modders would maybe add unofficial support for un-supported flight sticks.

After a little bit of research, I discovered Steam's built-in "General Controller Settings" gamepad mapping, and that it can be used to "trick" Ace Combat 7 into thinking you're playing with a third-party gamepad. I tested it last night, and was pleased to discover that it works!

To see if your flight stick will work (and it's no guarantee), perform the following steps:

Open Steam and select "Steam -> Settings" in the top menu.

In the Settings panel, click "Controller".

In the Controller Config panel, click the button that says "GENERAL CONTROLLER SETTINGS". A big, blue menu with several check boxes should appear in a new window.

If your flight stick is plugged in, and the PC is registering it, you should see it in a list of "Detected Controllers". Click it.

This should take you to a key binding screen. Set up your key bindings as you see fit. You do not necessarily have to map every single button, as most flight sticks may not have enough buttons.

Click "Save" and a dialogue should appear asking you if you want to "Share this controller definition?". You can name the controller anything you like. The important part here is that there is a drop down labeled: "Select the type of controller:". You must select "Generic Gamepad" from the drop down! You can then click "No, Thank You" if you do not wish to share the settings.

You should now be able to boot up Ace Combat 7, and the game should now believe your flight stick is a third-party gamepad (rather than a forbidden flight stick), and it should function based on the bindings that you specified.

You can configure your flight stick as a "Generic Gamepad" in Steam's Controller Settings.

UPDATE 28 JANUARY, 2019, 6:44 PM (PST)
Twitter user @HillardHouseDan referred me to a gamefaqs post at gamefaqs.gamespot.com/boards/179835-resident-evil-2/77419853 that has a work-around for this issue. That post claims that disabling HDR (High Dynamic Range) in the PS4's video settings will allow you to stream and capture Resident Evil 2 footage. Commentor Jon had also posted the same work-around just as I was loading up RE2 to test it. So thanks readers!

I had actually come across this post last night, but had dismissed it because it was specifically about "Share Play" and not about streaming. I have been streaming Red Dead Redemption II for two months with HDR enabled without any problem, so it didn't even occur to me to test that setting.

Besides, the message was telling me that the scene was "blocked", so I had assumed that Capcom had blocked it as a "spoiler" section. Games in the past have done this for screens in which players enter email accounts, passwords, credit card numbers, or other sensitive information (which is the only acceptable use of blocking share functionality!). But Atlus had also recently blocked streaming of Persona 5 in order to prevent spoilers from leaking onto the internet. I was assuming that Capcom was doing the same thing. Atlus had patched Persona 5 to remove the streaming block for after about a week.

So, long story short: If you disable HDR on the PS4's video settings, you should be able to stream Resident Evil 2. You'll be playing at lower resolution, and with less color range, but it'll be playable and streamable. I guess I'll have to chalk this one up to a bug for now? Maybe Capcom will fix it with a patch. I can't imagine that they had deliberately blocked HDR or 4k streaming, but left non-HDR and regular HD enabled.

So pending any other setbacks, I do expect to play Resident Evil 2 this week, and will hopefully have a review out in a couple weeks. I'm leaving the rest of this post intact for posterity. Some of the points about fair use and blocking functionality of the console are still valid for situations like Persona 5, so maybe this blog will serve as a cautionary tale for any publishers or developers who do try to pull something like this deliberately.

UPDATE 26 February, 2019:
I have a full review up for the game now. I have also adapted that review into a video critique on YouTube:

I have adapted my review into a video critique on YouTube.

I was really looking forward to this remake of RE2.

After having to wait all of Saturday night for Resident Evil 2 remake to download and install on my PS4 (and playing Red Dead Redemption 2 to pass the time), I tried booting up the game on Sunday and played 15 minutes, only to find that the entire game is blocked from streaming. Even the built-in "capture" functionality (of the last 15 minutes of gameplay) of the PS4 console is disabled! I didn't even know games on the console could disable the built-in capture.

This realization sent me into a rabbit-hole of digging through the internet to find out if there was a work-around. I couldn't find one. Apparently, only the PS4 version of the game suffers from this problem. Players on Steam and XBox One do not seem to have any issues streaming.

I was very exciting to play this game. I really loved the REmake that was released on PSN a couple years ago, and I've been looking forward to an "RE2make" ever since. Resident Evil VII was also pretty damned good, and a return to form that made me optimistic about the series moving forward. But the game being blocked from streaming and capture put a damper on the experience that makes me not want to play the game. Basically, my night -- and my weekend -- were ruined by this petty decision from Capcom (and the fact that Sony even allows this bullshit on their platform).

This makes blogging about the game much harder

Why is this such a big deal? Why can't I just play the game and not stream it to Twitch? Well, the reason is that I use the streaming and capture functionality to get screenshots (and occasionally video) for use on this blog. After playing the game, I go through the archived footage to get relevant screenshots for blogs, strategy guides, analyses, or whatever I happen to be writing about the game -- all of which is legally protected under fair use!

It isn't just streaming that's disabled; even the capture function built into the PS4 is disabled!

I could maybe have lived without the Twitch broadcast, as I usually prefer to save important footage using the PS4's built-in capture function. The captured footage is much higher quality than what is saved by Twitch, and so it's essential for getting good screenshots of action segments. But the PS4 only saves the last 15 minutes of footage, so I have to make sure to remember to capture any video that I feel I'll need. I use the Twitch stream as a backup in case I forget.

It's tax season, which is not something that I ever write about on this blog. But this year, I had a very irregular experience. It wasn't with my taxes; rather, it was with my dad's attempts to use this year's TurboTax software. He'd been using TurboTax for years with no problem, but this year, the program wouldn't install. He's not exactly tech-savvy, so he had to call me to help him troubleshoot.

TurboTax fails to install due to some unspecified issue with the .NET Framework.

Upon attempting to install the program, he gets a very un-descriptive error message that simply states there was a problem installing TurboTax. Then a dialogue pops up stating that TurboTax is attempting to fix the problem by checking the file system, registry, and .Net framework. It's the .Net Framework step where TurboTax fails with yet another very un-specific error.

We tried updating Windows, disabling anti-virus software, and even opened up the registry to make sure that all the requisite versions of .Net Framework were installed. No luck.

Unable to resolve the problem itself, TurboTax referred us to a troubleshooting web page.

TurboTax referred us to this troubleshooting page, which includes instructions for downloading and running various .Net Framework repair tools and other system file integrity tools. In my dad's case, none of this stuff worked. As a last resort, the troubleshooting guide referred me to a blog post by Microsoft developer Aaron Stebner, who wrote about a .Net Framework cleanup tool that could potentially be used to resolve the issue...

If you get this error message, then training will stop working completely, and will just hang on an infinite load screen.

Is your Madden 17 franchise getting hung up on an annoying bug that prevents you from doing weekly training? Are you getting a dialogue saying "Training is not ready. Ensure that you have focus players selected."? I had this happen to me, and the resolution is not immediately obvious. I searched the EA troubleshooting forums and Reddit and only found partial solutions that didn't work for me. Apparently, this "glitch" has a couple different causes.

Most of the solutions that I had read online involved adjusting the user team's depth chart. In some cases, users said that the problem was caused by not having enough active players in a specific roster position. By signing a player at the necessary position, the problem was resolved, But this fix wasn't applicable to all users. I specifically encountered this bug in week four of my franchise's preseason. It happened right after installing the 1.04 update, and I feared that the update had hosed my save file. Fortunately, I found a resolution.

First, I tested the fix suggested above by ensuring that I had players at all roster positions and that all depth chart positions were filled, but didn't have immediate success. After a little bit of extra troubleshooting, I found that it was because I had too many players on my active roster. I had signed an extra player to replace an injured player. The injury was only for 3 weeks, so wasn't worth putting the guy on IR, but the new player put me over the roster cap. Since it was preseason, the game apparently doesn't enforce a roster limit, but I noticed that the Week 4 activities included "Cut 11 players". Usually in week 4, you're only supposed to cut 10 players. So I cut some dead weight (so that the activity now says "cut 10 players") and the training loaded...

So, Chichian and I have both recently had issues with Steam that required us to create a support ticket. Steam has a rather obtuse system for support tickets, and for many users, it apparently doesn't work at all.

First and foremost, Steam's support requires that you make a separate account just for support. You don't log into Steam support using your existing Steam account. Supposedly, this is because the most common ticket is to retrieve access to a lost account. Either the player forgot their account info, or it had been hijacked. So in order to prevent people from having to make a whole separate Steam user account just to create a support ticket to retrieve their old Steam account, they set up this system in which support is its own separate account to begin with - for everybody. So even if you have full access to your Steam account and only want to report a bug in the client or have an issue with a purchased game not showing up in your library, you still have to go to the trouble of creating a completely separate account.

You then have to go through the email validation process. After you create an account, they'll send you a verification email. Pretty common stuff. Unfortunately, many users (including myself and Chichian) never get these emails. The same might apply for email requests to reset a password if you forgot your support account's password. The email doesn't go into a spam folder. It doesn't go to the wrong account. It doesn't show up two days later because their emailer services are slow. The emails simply never show up. You're not crazy, there is an explanation.

Apparently, some email providers completely block Steam Support from sending emails to their users for ... some reason. I guess they think Steam Support is some kind of spammer or malware threat? Usually, you'd expect such an email to get sent to a spam folder. But not in this case. It's really annoying that providers are able to simply refuse traffic from specific sources, especially a source that is legitimate like Steam.

Use a gmail account for Steam Support.
It works ... for now ...

So bottom line: if you are having issues with creating or accessing a Steam Support account, you're not alone. If you're waiting for validation or password reset emails that simply never show up, it's probably because your provider is blocking them. Chichian's Steam Support emails were blocked by Hotmail and Yahoo. Mine was blocked by AOL. It appears that gmail does not block Steam Support though. We were both able to receive the emails when we created an account using gmail. So if you are having issues, I recommend using a gmail address to create your Steam Support account. It will save you some confusion and frustration.

A gamer's thoughts

Welcome to Mega Bears Fan's blog, and thanks for visiting! This blog is mostly dedicated to game reviews, strategies, and analysis of my favorite games. I also talk about my other interests, like football, science and technology, movies, and so on. Feel free to read more about the blog.

And check out my colleague, David Pax's novel Without Gravity on his website!

Featured Post

Yes, you can MAYBE play Ace Combat 7 with an un-supported flight stick!03/14/2019Some number of PC players may have booted up Namco/Bandai's recently-released Ace Combat 7 on PC, only to be disappointed to find that their preferred flight stick doesn't work with the game. Un-supported controllers apparently includes the very popular (and very expensive) Thrustmaster Warthog. This isn't a technical issue;...