This game won't even load. It crashes before the initial screen loads. Upon looking in the Windows event logs I see this error: Faulting module path: C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\overlay64.dll. I researched this and here I am after finding this thread. This very old thread for an old game, yet the same issue.
My days of tolerating hours of jumping through hoops to get a game to work has been long gone for some time (I'm an older gamer). I did want to post some information though. This is not a hate post. I've been enjoying Ubi Soft titles since the 90's. In fact the first thing I want to say is in defending their support and hopefully explain many users gripes of tickets.
I did both hardware and software support for over 10 years. I'm A+ certified and even had my own business for a few years. Support throughout this thread states what a customer with an issue really doesn't want or need to hear (read). "Open a ticket!". This is the worst thing in the world to have to read when you buy something that doesn't work. We shouldn't even have to research why it isn't working let alone open a ticket that won't come close to a quick remedy to something that is "not our problem". If it truly is Nvidia drivers still after all this time then I can only wonder why they ignore it. I have 22 new games that I've bought in the last 3 months. New as in new to me. At least half are around the age of Far Cry 4. None have issues other than Far Cry Primal. Bugs yes, failing to starti or crashing like this, no. My belief is (cannot be) 100% Nvidia's or ATI's drivers. More than likely it's code that doesn't play nice with their drivers or simple issues with direct draw at time of launch. In any case this is an ancient issue to a $70 dollar old game.
Now for the understanding to support. I worked for 3 companies that were fixated on support tickets. ALL of us in support hated them as much as our client base and I know dozens of support techs still in the industry that can't stand them. In fact I don't know a single one that likes them. A forum is a knowledge base. The term "Necro" is very misused and rarely understood. If one searches the net for overlay64.dll issues and they find a thread like this, it's relevant and new information should be added to it as a knowledge base. CEO's, investors, QA, basically anyone other than support use their tickets as a pulse of their biggest issues. An upper tier support technician can swear to their boss that the biggest issue is A, but if their are 3 tickets for issue A and 7 for issue B then issue A will not get developer or QA time. For them it's something they can quickly run a crystal report on and present data on pie charts and what current issues are. It's a failed system because from my years of experience I can easily say that most people will not open support tickets. One thing we did in support to help things on both sides was to spend a fair chunk of our time open tickets ourselves. It cost the company a combined 80hrs a week I imagine but their need for their ticket system forced it if we were going to have accurate data. Their own fault in other words. In the higher echelon way of thinking goes "If there are no tickets, there must be no issue". I feel the pain of support but it's a failed system and if it weren't for forums, gaming companies wouldn't stand a chance at all.
So no my information. Basically same as others but my specs are:
Titan Z
i7 5960
128gb ram
MSI Godlike MB
Win 10 Pro 64 bit
Far Cry Gold bought and run via Steam (thus Uplay launcher).
Steam, and all of my games and applications are not installed in my C drive and I have full ownership (admin rights).
Game starts to launch and just as it tries to tell Direct X to go full screen I get the overlay64.dll error. I tried all of normal approaches to fixing it such as compatibility and disabling shadow play but I didn't, and will not uninstall any usb devices for something that is being said to be a nvidia driver issue. I wouldn't do such a thing if my $3k Adobe suite stopped working or CAD said it was the only fix. That's for QA or a beta team, not a customer. It's been years since I've seen what I think it is, but after a couple dozen attempts it's obvious it crashes during direct draw initialization (when direct x starts to take code and go to GUI). I read through all 17 pages and see many users use surround gaming or have high res monitors. The questions were never asked of them but in many cases I've seen issues where this is the issue and the way the launcher starts the app it doesn't do so initially for a single monitor setup. All apps should to rule out amateur code issues with direct draw and users like me that have multiple monitors but not intended for gaming (different sizes, resolutions). Direct X takes control in full screen and back years ago games would have a separate launcher for settings PRIOR to running the game. This was key for troubleshooting and just the ability to first tell a game to try windowed before launch would point to the issue in seconds, not years. I didn't snoop around to find a config file a could edit to test some theories but I don't have time or patience for verbose diagnostics for a game anymore.
I have their Far Cry Primal and it at least ran. It didn't work correctly however and again, I see it as really amateur or old code. Loved the game but from start to finish I was never able to change a setting such as changing screen resolution without it crashing.I played the entire game at a low resolution (the default). If this game at least ran as Primal did I would keep it. I would not like it, but I wouldn't have got a refund like I did with FC4. Easy to do when it's easily proved with Steam that you have less than 2hrs play time (in this case, 0 seconds).
Companies need to post known working solutions and not block them from public use without a ticket. Both the customer and support would be much better off and the higher ups can save their reports in seeing doing such a thing would greatly increase their client base and profitability.
Sorry for the long winded post (no, I'm not) but wanted to help and I'm waiting for a video to render
