MV - What is "[1111/122448:WARNING:resource_bundle.cc(286)] locale_file_path.empty()"?

[ZackNH]

Back in July I made a post about how after almost 850 hours of using MV (on Steam, Windows 10) it suddenly stopped launching. I eventually became so disheartened that I stopped trying to fix it. Recently I discovered the debug.log file and how these warnings pop-up every time I try to launch MV:

[1111/103337:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
[1111/103337:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
[1111/122448:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
[1111/122448:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
[1111/123042:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
[1111/123042:WARNING:resource_bundle.cc(286)] locale_file_path.empty()

Two lines of the exact same warning show up every time, with each individual bundle having different numbers.
Does anyone know what this is?

If you're curious, here's everything else I've tried in the past:

1. Rebooting the computer (obviously, it's been 4 months)
2. Verifying integrity on Steam
3. Clearing Steam cache, then uninstalling and re-installing MV
4. Checking if I was somehow in a beta
5. Launching the program from individual project folders
6. Checking if drivers are out of date
7. Trying Windows 8 compatibility mode
8. Disabling anti-virus
9. Running Advanced System Care [Free version]

 

[Celestrium]

Back in July I made a post about how after almost 850 hours of using MV (on Steam, Windows 10) it suddenly stopped launching. I eventually became so disheartened that I stopped trying to fix it. Recently I discovered the debug.log file and how these warnings pop-up every time I try to launch MV:

[1111/103337:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
[1111/103337:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
[1111/122448:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
[1111/122448:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
[1111/123042:WARNING:resource_bundle.cc(286)] locale_file_path.empty()
[1111/123042:WARNING:resource_bundle.cc(286)] locale_file_path.empty()

Two lines of the exact same warning show up every time, with each individual bundle having different numbers.
Does anyone know what this is?

If you're curious, here's everything else I've tried in the past:

1. Rebooting the computer (obviously, it's been 4 months)
2. Verifying integrity on Steam
3. Clearing Steam cache, then uninstalling and re-installing MV
4. Checking if I was somehow in a beta
5. Launching the program from individual project folders
6. Checking if drivers are out of date
7. Trying Windows 8 compatibility mode
8. Disabling anti-virus
9. Running Advanced System Care [Free version]

I looked on the internet and found someone else had the same issues, someone had suggested downloading this to fix the issue. Below is the forum pages it is from. I have no idea if it will help, so please check out the original forum posts if you want more information. Good luck and let me know if it works!

Post from Silenity -
I fixed it by downloading this and putting it in the MV folder




https://steamcommunity.com/linkfilt...ts/grim-fandango/mesa_10_5_5_opengl32_pgo.zip

 

[Andar]

locale is a file that is used to store the language setting of the editor, but that should not be part of any resource bundle.
Best guess is that something is wrong in your accounts DLC management for MV, just check and disable all DLC there - you can reenable the DLC after you got the editor to run again


EDIT:

6. Checking if drivers are out of date

I fixed it by downloading this and putting it in the MV folder

Yes and no - the open GL version needed by MV is now very old and included in every regular display driver - manually installing the opengl library is no longer neccessary, that was only a fix for some older drivers when RMMV and its opengl version was extremely new.

however, if you made the mistake and installed a microsoft driver instead of the driver of the display chip manufacturer, then checking for newer drivers s not enough. OpenGL is a competition for DirectX and because of this a lot of the microsoft drivers do not fully support it.
you need to check not only if the driver is up-to-date, but also that the driver provider is the company that produced the chip (nvidia, AMD and Intel are the most common). if the display driver is provided by microsoft it needs to be replaced.

 

[ZackNH]

I never bought any DLC, but there are files in the dlc folder. Opening the Properties page on Steam, there is no DLC window like there is for other games/programs that I do have DLC for, so I can't disable anything. I took the files out of the dlc folder manually, but it didn't help. I also tried disabling any Workshop items I downloaded, but that did nothing.

Also, how do I check my display driver?

 

[Andar]

Also, how do I check my display driver?

you go into the device manager (either through system properties or system settings), then doubleclick on your display card. select the driver tab and you can check who programmed it (the driver itself, not the signature for it)

 

[ZackNH]

you go into the device manager (either through system properties or system settings), then doubleclick on your display card. select the driver tab and you can check who programmed it (the driver itself, not the signature for it)

I think this is it:

NVIDIA GeForce GTX 960
Driver Provider: NVIDIA
Digital Signer: Microsoft Windows Hardware Compatibility Publisher

I downloaded the newest NVIDIA update yesterday, if that matters.

 

[Andar]

yes, that's it - and it mens your driver is OK.
Only if there were "Driver Provider: Microsoft" (and yes, Microsoft programmed their own drivers for some nvidia cards) you would have found a cause for problems.

 

[ZackNH]

So, what IS the problem?
I still don't know the cause of the file path error I keep getting, and right now that seems like the only clue I have to go off.
I tried downloading some of the free DLC just so I can have access to the DLC management window, but MV won't launch regardless of if the DLC is active or disabled, and there's nothing else I can do with the window.

 

[ZackNH]

One last thing I tried was booting in Safe Mode because I hadn't thought to try that yet and I figured I might as well. Didn't expect anything, and didn't get anything. MV still won't launch. It seems I've exhausted every possible solution short of dumping everything onto an external hard drive and factory resetting my computer, but I'd rather not do that.

Unless someone has any idea what the resource bundle error actually is, it looks like I'm pretty much dead in the water on this.

 

[Andar]

@ZackNH
one idea that goes back to my post above would be to force steam to at least temporarily change the language of the editor, because that should rewrite the locale file.
which language is your windows? and which is the MV set to in steam?
If you know any of the other languages that MV is available in, try to change to that language and then start the editor. If you don't know any, just choose at random.
try to see if the editor starts with the other language setting, then go back to english and try again.
(language can be set in the steam program properties, right-click on the program in the steam client)

 

[ZackNH]

I just tried switching the languages for MV, and it still didn't launch.

 

[ZackNH]

I don't know if this might be related (I'm grasping at straws here) but Source Filmmaker also doesn't work anymore. Is there some aspect of Windows 10 that affects both MV and SFM? I've had Win10 for years but there were never any problems until recent updates this year. I've read that Windows 10 updates are sometimes the culprit, and the Win10 update in July was when MV stopped working. I didn't realize SFM was busted too until much more recently.
Running them in Win8 Compatability Mode doesn't help, but I don't know if there's something about Win10 that's overpowering it or something.

 

[Andar]

I don't even know what SFM is, but theoretically anything can be connected.
The strangest case I ever had while working in professional support was a display error (two black lines through all texts) in DOS-mode of Win98 that was caused by having the wrong mouse-driver installed under windows. That problem came up with a lot of customers who reinstalled their computer, and it took me hours before I accidentally found the cause. And it was reproducable on every computer of that series...

And the cause doesn't have to be the update - it could also be a damaged windows library that causes the wrong functions to be called, or it could be a wrong non-microsoft update (the Qt engine used by MV is also used by other programs, and if one of them overwrote some files with the wrong Qt version, then only that program will run correctly anymore and all other Qt-based programs will have problems.

 

[ZackNH]

I've never heard of a Qt engine. Is there a way to check if this is the problem?