2 Ways to get the game lunched. Way 1 is more confortable then way 2:
1) You can start the game just with the FC3Updater.exe or FC3Steamupdater.exe without changing anything.
Just make you a shortcut of the exe on your screen.
Also the name of the exe depends to what version you have.
Ubisoft or Steam. Its working with both.
You not have to rename but you can rename the shortcut on your desktop into Far Cry 3 and all is fine.
2) The compatibility mode for the Far Cry3.exe works, if you change to compatibility mode to Win 98 / Win Me.
You find both exe in the installation folder. They are in the folder bin.
to those who this didnt work for, there are 2 .exe files, if the main file does not work use the one that says something about directx11. right click into properties go to compatibility change it to windows 98/ me. open that .exe and run as admin, once in game click options/video/directx, it might say directx 9 change that to direct x 11 close the game and the regular .exe file should work if its compatibility is set to windows 98/meOriginally Posted by WID992007 Go to original post
This makes it even worse for me.Originally Posted by onlymistergreen Go to original post
I have F3 Deluxe Edition on Steam. When I launch the game, Uplay opens and a seperate window asks if I want to run the normal version, or the Deluxe Edition. Setting farcry3.exe to windows 98/ME + run as admin, makes the Normal version work, but not the DE. Selecting DE gives this Uplay message:
"Starting game
Unable to start the game. Please check that your game has been installed correctly. If the problem persists, please contact Ubisoft Support."
If I do ANYTHING with the farcry3_d3d11.exe file (any compatibility mode, or run as admin, or any combination), this results in the following error:
"Far Cry 3 Updater
Failed to execute command: farcry3_d3d11.exe (error 740).
Please make sure this executable file exists".
Unchecking both compatibility mode and run as admin, removes this problem again.
Files checked, game reinstalled twice. Whatever I do, the Deluxe Edition will simply not run.
Hi there, sorry you are experiencing this issue while launching your game. If the above steps do not assist with your query could we first ask that you attempt our basic troubleshooting steps as outlined here.
If you are still receiving this error after completing these steps, could you please provide your system reports by following the steps in this FAQ.
Got mine working eventually. Had to run the Farcry3.exe file in Win 98/ME compatibility and also tick "run as administrator" .
If you cannot see the compatibility tab for the exe file go to "File Explorer", click on "View", and make sure the "File Name Extensions" is ticked. There's no logical reason why this makes the compatibility tab appear...but it did for me.
Hope it works for anyone else reading this.
Well that was short lived. Game refused to load again until I R-clicked FarCry3.Exe and selected "Run as administrator". just having that instruction ticked under properties isn't good enough apparently.
But then, when playing the game it would periodically drop to single figure fps for no reason I could see. I think I'm giving up on this one.
To iamblued, TimThomm44 and others...
Yep looks like UbiSoft Support has no idea or likely even any contact with the technical incompetents who released this garbage port to an unsuspecting public via Steam via a duped management team and publishers. And that includes third parties such as Steam.
UbiSoft is still releasing this faulty version through Steam after a whole year and this obviously needs to be fixed ASAP...
According to the FC3 doco there's SUPPOSED to be a "gamerprofile.xml" located somewhere in your downloaded installation, which is the initial configuration file to launch FC3. For all those who are still having problems I bet you won't find this file anywhere - either in the FC3 Installation folder or under your W10/Users/... /Documents/My Games... folder tree or similar.
Moreover, just a guess, but I bet this is the "missing file" that Steam reports (over and over and over ad finitum) when you try to do a Verify Integrity Check on the FC3 Local File folder.
UbiSoft and Steam need to work together on this one and cough up a patch for Steam users and/or those with modern machines.
The responsibility for fixing this problem on all system configurations begins with UbiSoft to solve, not the purchasers of this dodgy corrupted product.
The trouble with going direct to UbiSoft Support is all you'll get back from them is irritatingly generic, insulting and condescending tripe like the 'advice' Ubi-Litten regurgitated in the post above.
Not only have UbiSoft not been able to fix this rubbish software in over a year, but in the past their 'advice' has caused almost irreparable damage (long story) to my system through their incompetence and complete misunderstanding of the issue here. So folks, be very wary of their so-called 'support'.
Yes I was able to get my previously stable system back again... but through my own efforts and technical knowledge, which is something this fake support group seems to lack.
The motto here is..."Customer Service is an action, NOT a department"
OK problem getting FC3 to launch at all appears to be essentially solved for me with the workaround below.
It seems that if you have a very modern CPU (eg Intel Core X-series CPUs or Ryzen Threadripper series) with very high core/thread counts that shipped in the last couple of years, you'll need to restrict the number of CPU cores enabled to even launch the game.
In Windows 10, use Search to locate and launch 'MSCONFIG'
Go to 'Boot' menu
Click 'Advanced options' tab
Click 'Number of processors:"
Use the drop-down to restrict # of processors to 15 or less (ie 15 logical HT processors <=> 8 physical cores)
Click 'OK' 'OK'
Reboot Computer
Retry FC3
More info here: https://steamcommunity.com/app/29811...4337786119483/
This fix also applies to a number of older Tomb Raider games including 'Tomb Raider-Underworld', 'Lara Croft and the Guardian of Light'... and wouldn't be surprised if fixed problems with quite a number of other games released in that era that have trouble launching on modern machines.
No doubt, the software developers of the day would now be aware of that legacy core count limitation, though it was never an issue in the past since very few even hard-core gamers would've used machines with such high core/HT counts.
Pity none of the techies at UbiSoft ever passed this increasingly relevant information on to the hapless UbiSoft Support teams.