It was straight-up free (as in: no tiers, just free) for a long time to early adopters of the Nvidia Shield. I can't remember when it was introduced but I think it was with the first iteration of Shield TV.
I wouldn't be surprised if there's a patent Microsoft just hasn't been willing to license use of.
I remember when the Sixaxis came out. It was missing vibration. It was because Immersion sued Sony (and ultimately won) over patent infringement of rumble motors. Sony ended up having to pay somewhere around $100 million.
I can't comment on this title in particular but if you load it on your PS5 and receive a toast which reads something to the effect of "when playing on PS5, this game may exhibit errors or unexpected behavior" then it means some part of the game is absolutely fucked up but still "playable."
For example, Star Ocean: Till the End of Time messes up very late in to the game on the PS5 where a space ship environment zooms very far out, the controls become locked in such a way where camera control doesn't work, and directional movement controls seem arbitrarily mapped. While someone more patient and talented than I may have been able to navigate through that issue, I couldn't proceed until I continued the game on my PS4 via cloud save transfer.
I've rarely considered it beyond functionality. I'll play a female in a fighting game if I like how the character plays. If the choice is purely aesthetic, I generally just choose whatever the default is. In Dark Souls III, I played a female because I thought I could make a beautiful character (and I think I did)
You're trying to get games built for a different OS (e.g., Win98) to run on your current OS. If it doesn't work out-of-the-box, you're going to need to seek a solution that either requires emulation or significant hoops to jump through. For example: if the game was built for a 16-bit machine, and you're running a 64-bit version of Windows, the game is just not going to work natively.
DOSBox may not work as it's an x86 emulator intended for MS-DOS. However, earlier versions of Windows (up to Win95) were just shells to MS-DOS. So, if the games in question were built for Win95 or earlier, DOSBox could be an option. I've also successfully installed Win98 on DOSBox but have run in to issues with drivers.
It may be best to simply list the games you're trying to get running and seeing if someone else has gotten them to run in Win10.
And did you have to explain it to him, or was that just the first opportunity he had to raise the question, and you answered right away without him having time to figure it out himself?
I suppose it was a bit of both.
It was three of us playing. I had finished the game already by the time we started. At first, we left it to him to explore the systems on his own. He got frustrated with that and would complain that we weren't telling him what to do. So, we gradually explained more and more until we just started making decisions on our own. He was still frustrated. For example, late in to Act I, he would continue to throw his cleric in to the middle of battle as a melee fighter and die. Shortly after that, we all decided to stop playing.
There are a lot of tutorials in the early game that explain so much of this stuff that you have to explicitly dismiss that they're hard to miss.
I must have missed them, then. I don't recall any tutorials explaining anything beyond the cursory "you have to be in range to attack" or "potions heal HP" type of things. In fact, I loaded up my save and perused the tutorials again. The tutorial titled "Combat" simply tells you that there's an initiative roll, combatants are listed at the top of the screen, and during a turn, a character may take an action, bonus action, and move. It's entirely unhelpful. It may as well be a fighting game tutorial which says, "use punches and kicks to defeat your opponent."
The opening moments of the game actually require you to use your movement in turn based combat in order to continue, and you can observe which enemies can reach you or not as you approach your objective.
I got through it by just running past most everyone. Sure, you can clearly see you have to move and that you have actions to take but nothing else is explained beyond that. I think that opening sequence is a great example of the lack of explanations in the game. My buddy thought he had to kill absolutely everyone on the nautiloid. We tried twice before telling him that you can continue moving past enemies. The thought never occured to him. I can't blame him, either. All you're told is that you have to connect the transponder in a certain amount of turns and narratively, there's a sense of urgency. Nothing tells you that you don't have to kill everything on the screen. That might seem painfully obvious but that's my point: things obvious to one person are not obvious to another. That doesn't make someone stupid, either. They just have different experiences and different expectations.
Nothing in the game explains that encounters are not immutable. Nothing in the game, as far as I can remember, explains the value of environmental elements and how to leverage them in combat. Nothing explains the tactical value of oil or water on the ground. Nothing explains the concept of crowd control at all. Nothing explains how to keep backline party members safe. This is all left for the player to discover.
I've been playing Larian games for a long time and I don't remember a single one of BGIII, DOS2, or DOS ever explaining these concepts. If you walk in to these games without the understanding that you are expected to be observant and play around with the game mechanics, you will have a bad time. There are innumerable posts on the Web by people frustrated with the game because they don't know what to do. My buddy is not an isolated example. People think differently.
My buddy tried fighting in melee combat as a low-level cleric. That might be a totally valid thing to do in something like Final Fantasy. My buddy thought he had to kill every enemy on the nautiloid. Maybe that's just what you do in something like Diablo. Hell, I just finished a dungeon in Star Ocean which required exactly that. (It even told me upfront that would be the expectation of the dungeon) We are taught things which influence our decision making process. Without being told otherwise, it can be hard to understand exactly what is being asked of us as players as we try to reconcile those expections with our experiences.
My buddy didn't need to be told what to do. What he needed to be told is what he can do and why he might want to do those things. In that, Larian failed him and, in my opinion as an adoring fan of their games, they have a habit of doing so.
While I agree in principle, I think a game needs to make it clear when something isn't window dressing. My buddy just couldn't understand why positioning mattered. It never clicked for him because he figured RPG combat was just "swing a sword/shoot an arrow until the other guy dies". We had to explain it to him. He also never thought to explore the UI for information as to why his movement was reduced or why he was disadvantaged, despite having icons next to his character with tooltips explaining what status effects were in play. While it may seem obvious that things are happening on screen and one could deduce that something meaningful is occuring, I think if I'm honest, I can't blame my buddy for not understanding. I've fallen victim to it myself.
Sometimes we just don't, on our own, interpret information as being meaningful. Consequently, we unduly discard it before making decisions. I think it's important to be told in one form or the other when something matters. Whether that's tutorialization or otherwise, I think it's important. I think the more complicated the game, the easier it is for a player to fall in to a trap of discarding important information and subsequently becoming frustrated.
I think even something as simple as the game making its expectations clear from the start could go a long way. Something as simple as conveying to the user that they are expected to be attentive as they play.
I love both Baldur's Gate III and fighting games but disagree. I think both are woefully inadequate at explaining their rules to players. Larian games need to not only make BGIII's rules as clear as a rulebook but also make tactics and strategies plain and clear to the user. Otherwise, it is very easy to fall back on decades of video game expectation only to realize your expectations are wrong. I had a co-op game of BG3 with a friend. My friend couldn't understand why he had to position his units anywhere. Didn't understand why inventory wasn't just immediately being teleported to a shared infinite item box. Didn't understand the basic mechanics of D&D combat (which even then, Larian changes to various degrees) Didn't understand why decisions had any meaningful consequences. Didn't even understand what he was supposed to be doing narratively despite there being a quest log and having us recap the story up to the point we were.
While fighting game tutorials have gotten better, I still have yet to experience one that explains very basic things that the FGC takes for granted. Things like health bars being identical physical lengths but representing different numerical values. Things like "waiting for your turn." Things like meter management.
Complex games are great. But complex games need to recognize that they have a larger duty to teach than simpler games. I think video game design needs to take a page out of tabletop game design and provide some analog to the tabletop rulebook: complete with not just rules but detailed explanations, sidebars, and examples of play.