How to run a game in compatibility mode?

[futurefields]

I right click on the icon, hit properties, I expect to see a "compatibility" tab where I can select xp compatibility for this game. But there is no compatibility tab showing, so how can I get this game to run in xp compatibility?

 

[mikeymikec]

Track down the exe file and try the same thing again?

The shortcut you're using might be one of those annoying "special" shortcuts like what MS uses for MSO applications.

 

[alkemyst]

QFT, it must be a shortcut thing and not a direct executable.

Also telling us what OS would be helpful.

 

[mikeymikec]

I can see the compatibility tab on an exe file's properties window.

 

[futurefields]

Really weird. I used the 'create desktop shortcut' option from Steam and it generated a shortcut that, when right-clicked, did not have a compatibility tab. I had to go to the actual game folder in steamapps, find the application file and use that. But all my other games, which I also use the 'create desktop shortcut' option from Steam the compatibility tab is there, only Max Payne 3 is different.

 

[frozentundra123456]

Does that compatibility mode really do much? Seems like it doesn't really work well on most of the older games I have tried. Spebifically, I have tried Age of Empires 3 and Galactic Battlegrounds and they both have the same issues (aoe crashes and battlegrounds color corruption) natively in win 7 or compatibility mode for XP.

 

[futurefields]

I have used it on certain games, can't remember exactly what and when. I believe Fallout 3 has some issues that are alleviated by running compatibility mode.

I am trying to use it to fix a shadows bug on the stadium scene in Max Payne 3. But now i just read the bug is ALWAYS there when you try to reload a checkpoint on that chapter, I have to restart the chapter from the beginning and the shadows bug goes away.

Thinking on going to get a PS4 today...

 

[mikeymikec]

I've found the compatibility tab useful in the past. I believe it's possible to disconnect it from Windows with a regsvr32 -u filename.dll (it might have been appcompat.dll or something similar), perhaps that has happened on your setup somehow.