The Mighty Quest for Epic Loot Forum

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

Stuck at loading screnn

So i downloaded the crosstie and started the game, i installed it,logged in yadda yadda yadda but i was stuck at the first loading screen where you see floating castles and it says mighty quest for epic loot loading and then nothing happened i let it remain like that for about half an hour and still nothing, help D:

You can probably force quit it. Make sure that nothing is running in the bottle (use the Quit Bottle button), then try running the game again.

It did not run for me either on the first try. Gave me an error about not being able to connect to the server and then it just sat there. I killed it, ran it again and it worked.

Still doesn't work :(

Alright, let's start troubleshooting, cuz it works for me.

Please tell me about your system, are you on Mac OS X or Linux. What version/distro? If you're using linux how did you install? What video card do you have? What driver version if not on Mac OS X, how much RAM?

I am on Mac osx 10.9.1
Intel HD 3000 and 4 GB Ram and i like to point out that it doesn't really freeze but it just keeps loading with no result, sometimes i can even hear a narrator telling the backstory and i think it happens to some windows users too so it may not be a problem from crossover

Oh the dreaded Intel HD3000...

There's one last trick I can think of. If you're on CrossOver 13.x select the bottle where the game is installed, go to the Advanced tab and try either of the following or both:

1) There's an option to disable Performance Enhanced Graphics - use it and try the game again

2) Disable the Mac Driver, try to run the game again

I really wish Apple stopped putting subpar graphics chips in their products :(

Still nothing :( i just think its a problem with the game itself not crossover since many people have it, thanks for the support though looks like i just have to wait for an update

also i'd like to apologize for the mistake in the title, i can't believe i wrote screnn :(

I tried it on my mac and it's stuck on the launcher. It says my computer doesn't meet the requirements even though it should still work. Is there a way to tell it I'm running on windows just so it will load?

I also get the "minimum requirements error".

iMac 21.5-inch, Late 2012
3,1 GHz Intel Core i7
16 GB 1600 MHz DDR3
NVIDIA GeForce GT 650M 512 MB
OS X 10.9.2 (13C64)

Disabling the Mac Driver doesn´t help.
I will try tomorrow to find a fix.

Have a nice day.

Unfortunately, two launchers get created for this game. One by the installation program and one via the crosstie. The one that you want to use is the one created by the crosstie because it includes a command line parameter which allows bypassing that "error message".

You may want search in finder for the shortcut called Launch Epic Quest for Mighty Loot

Hi there,

i´ve used the CrossTie Installer, but i only have one launcher.
I first get error "Warning 40000006 : Unrecognized command line option... The rest of the command line options will be ignored !" and then the "Minimum Requirements" Error.
I only have "The Mighty Quest For Epic Loot (The Mighty Quest For Epic Loot)" launcher and nothing else in the Crossover Folder and Spotlight does not find any other launcher.

Have a nice evening.

Oh my... I got around today to testing this and you guys are right but I also have a fix. It appears that Ubi changed some things for the open beta and one of them is the launcher and the command arguments for it. So, for people that already have the game installed create a new shortcut, using the Run Command button from the Bottle Manager that points to:
"C:/Program Files/The Mighty Quest For Epic Loot/Launcher/PublicLauncher.exe" -SkipMinimumConfigCheck

-SkipMinimumConfigCheck Is the command line argument that bypasses the annoying, possibly broken, system check. You will still see that error message from time to time when they update the launcher. In that case just restart it from your newly created shortcut.

I'll update the crosstie ASAP and let you know when the "new" version is online.

UPDATE 1: Crosstie has been modified, tested and published. It's currently awaiting ninja approval.
UPDATE 2: The crosstie is now online

With "-SkipMinimumConfigCheck" i can pass the Launcher and Updates but then i get stuck at the loading screen. It loads forever.

Thanks for your big support. :)

Unfortunately I'm unable to test on Mac OS X. If a solution that means a tweak to the crosstie is found, I'll add it.

One thing though. Have you tried quitting the game, making sure that nothing is running in the bottle with the Quit bottle button/Force quit (if needed) and then starting the game again?

I have this same stuck at loading screen issue.

I used the recently updated crosstie for installation. I managed to get this far without disabling PEG or using legacy X. With disabling PEG and using legacy X, I get the same results. If I only disable PEG and don't use legacy X, the client crashes due to an "unexpected error." I tried each of these configurations several times (after closing and reopening the application using the correct launcher).

One things I find weird is that as soon as the loading screen opens, there is a little spinning circle/arrow thing at the bottom right. It spins for a few seconds, and then the "Loading..." text shows up at the bottom. Right after the circle/arrow thing finishes and before the "Loading..." text appears, the game changes resolution slightly. I'm not even completely sure if it's a resolution change or just a weird shift, but it seemed to be something worth noting. This was also the point where the client crashes, right after the circle/arrow thing finishes (when I disabled PEG only).

I was going to do more tests with console open and such, but the client is telling me that there is server maintenance, so I will wait until later.

(Using: OS X 10.8.4, quad i7, GT 650M, 8G DDR3)

Hmm, yes what you describe happens on my Linux machine but I actually get the game running and not a crash. Maybe it does not "like" full screen... Try an emulated desktop, maybe it'll like that better.

If you don't know how to set that up, here's some info:

http://www.codeweavers.com/support/wiki/mac/mactutorial/unsupported_deps

Search that page for: Emulate a Virtual Desktop

How do i reenable PEG because i did something and now the game is crashing.

Nevermind, I got it.

dangit now it's crashing on the loading screen I'm on mac os x by the way

Yeah, I see this is common for Mac OS X users... can't really say what the problem is since I can't test on that OS. Did you try running it in an emulated desktop like I suggested?

Before it was getting stuck at the loading screen but now it's crashing.

Would there be some sort of crash report?

Hmm let's see what the launcher believes that your systems are not "worthy". Please follow these steps:

1) Open CrossOver and the Bottle Manager and select the bottle where the game is installed
2) Click on the Open C: Drive button
3) Browse to C:/Program Files/The Mighty Quest For Epic Loot/Log
4) If there is a file called PublicLauncherLog0001.txt rename it to PublicLauncherLog0001.txt-old
5) In the Bottle Manager click on the Run Command button and browse to C:/Program Files/The Mighty Quest For Epic Loot/Launcher, select the file called PublicLauncher.exe and click on the Open button
6) Click on the Run button

This will run the launcher and it will fail while checking system requirements. Good, we want to see what test fails.

Now, in C:/Program Files/The Mighty Quest For Epic Loot/Log there should be a new file called PublicLauncherLog0001.txt. Open it and post the contents of the file here.

Example:


[03.07.14 13:35:00.798][Verbose]Launcher Start
[03.07.14 13:35:00.798][Verbose]Connected to Steam: FALSE
[03.07.14 13:35:00.798][Verbose]Loading Installed Game Packages Info
[03.07.14 13:35:00.798][Verbose]Loaded Installed Game Packages Info
[03.07.14 13:35:00.829][Verbose]TaskInitWeb::entered
[03.07.14 13:35:00.939][Verbose]Loading page file:///C:/Program%20Files/The%20Mighty%20Quest%20For%20Epic%20Loot/Launcher/LocalLauncher/launcher.html
[03.07.14 13:35:01.123][Verbose][Javascript]init
[03.07.14 13:35:01.168][Verbose]Page load finished!
[03.07.14 13:35:01.168][Verbose]TaskInitWeb::exited
[03.07.14 13:35:01.168][Verbose]TaskConfigureNetwork::entered
[03.07.14 13:35:01.215][Verbose][Javascript]showProgressBar
[03.07.14 13:35:01.301][Verbose]TaskConfigureNetwork::exited
[03.07.14 13:35:01.301][Verbose]TaskCheckPCMinRequirements::entered
[03.07.14 13:35:01.301][Verbose]Loading requirement flags from disk
[03.07.14 13:35:01.557][Verbose]Adapter 0 test start
[03.07.14 13:35:01.557][Verbose]Texture format ATI1 not supported
[03.07.14 13:35:01.557][Verbose]Adapter 0 doesn't meet the minimum requirement
[03.07.14 13:35:01.581][Verbose][Javascript]showMessageBox
[03.07.14 13:35:02.810][Verbose]TaskCheckPCMinRequirements::exited
[03.07.14 13:35:02.810][Verbose]TaskExit::entered
[03.07.14 13:35:02.818][Verbose]TaskExit::run

The relevant bit:


[03.07.14 13:35:01.557][Verbose]Adapter 0 test start
[03.07.14 13:35:01.557][Verbose]Texture format ATI1 not supported
[03.07.14 13:35:01.557][Verbose]Adapter 0 doesn't meet the minimum requirement

The above is enclosed between [code][/code] tags.

Bam!
[02.07.14 21:36:13.011][Verbose]Launcher Start
[02.07.14 21:36:13.012][Verbose]Connected to Steam: FALSE
[02.07.14 21:36:13.012][Verbose]Loading Installed Game Packages Info
[02.07.14 21:36:13.013][Verbose]Loaded Installed Game Packages Info
[02.07.14 21:36:13.055][Verbose]TaskInitWeb::entered
[02.07.14 21:36:13.384][Verbose]Loading page file:///C:/Program%20Files/The%20Mighty%20Quest%20For%20Epic%20Loot/Launcher/LocalLauncher/launcher.html
[02.07.14 21:36:13.589][Verbose][Javascript]init
[02.07.14 21:36:13.658][Verbose]Page load finished!
[02.07.14 21:36:13.658][Verbose]TaskInitWeb::exited
[02.07.14 21:36:13.658][Verbose]TaskConfigureNetwork::entered
[02.07.14 21:36:13.762][Verbose][Javascript]showProgressBar
[02.07.14 21:36:18.879][Verbose]TaskConfigureNetwork::exited
[02.07.14 21:36:18.879][Verbose]TaskCheckPCMinRequirements::entered
[02.07.14 21:36:18.879][Verbose]Loading requirement flags from disk
[02.07.14 21:36:19.886][Verbose]Adapter 0 test start
[02.07.14 21:36:19.886][Verbose]Texture format ATI1 not supported
[02.07.14 21:36:19.886][Verbose]Adapter 0 doesn't meet the minimum requirement
[02.07.14 21:36:19.938][Verbose][Javascript]showMessageBox
[02.07.14 21:36:22.329][Verbose]TaskCheckPCMinRequirements::exited
[02.07.14 21:36:22.329][Verbose]TaskExit::entered
[02.07.14 21:36:22.338][Verbose]TaskExit::run

So it fails in the same place it failed on my system... trouble is that the sys req checking routine exits as soon as a test fails.

I went to the forums and managed to get the attention of a developer. It turns out that the check should not fail on ATI1 compression support, the game's checks and the launcher's were out of sync. So they are going to take that out. This is the good news.

I've also bounced the idea that the sys requirement check should not exit on the first fail because it would be useful to see what tests succeed and which ones failed. The dev seemed to agree and we may see that at some point. Actually he suggested that a stand-alone utility that ran those checks bits would be even better. So we might see that at some point. No ETA.

Relevant forum thread: System requirement check a bit too rigid

Could you provide another log please? This time, you follow the same steps as above but instead of messing with the launcher log files you leav them alone. Once you have the command line to the launcher in the "Run Command window add -SkipMinimumConfigCheck < - this is a space followed by -SkipMinimumConfigCheck. In the same window there is a Debug option. Click on it check the "create log file" checkbox. No need to check anything else. Click on Run and you'll be prompted to choose where to save your log file. Try to run the game. When it fails collect the file, upload it to your dropbox, google drive, etc and link it here so I can take a look at it.

Salut.

I tried the above.
Ran the following command:

"/Users/rci/Library/Application Support/CrossOver/Bottles/The Mighty Quest for Epic Loot-2/drive_c/Program Files/The Mighty Quest For Epic Loot/Launcher/PublicLauncher.exe" -SkipMinimumConfigCheck

I left the space after "-SkipMinimumConfigCheck"
Here is a screenshot of the error I get, and a screenshot of what I chose.

http://imgur.com/xQyDjj8
http://imgur.com/PiIcyYf

And here is the log generated by Crossover.
http://pastebin.com/eFBUx4Er

Does this happen with crossover 13.1? Was the game installed using the crosstie? In your case the application seems to just crash, not show a black screen

Yes, 13.1.
Yes, the game was installed twice in two new separate bottles using crosstie.
Yes, my behaviour seems to be unique amongst reports.
10.9.2 install.
I will try another local user account, and report back.

Another user works fine. I tried the Guest user. I will troubleshoot the problem further on my own user account.
Thanks for the help!

Folks, as a follow-up to this discussion, there is an experimental version of the launcher.

Discussion thread is located here:
Can't play the game because of the minimum requirement check?

Direct link to the launcher:
http://static7.ubi.com.s3.amazonaws.com/mqel/mightyquest/PublicLauncher/PublicLauncher_231911_SkipMinCheck.zip

Instructions:

1) Back up the Launcher folder.
2) Extract the zip into the original Launcher folder, making sure
PublicLauncher.exe is overwritten, as well as the .js files in
LocalLauncher\javascripts\translations.
3) Play!

This new version of the launcher should be more verbose and tell you what tests fail but it should also allow you to press a button and attempt to run the game anyway. Try it out, give feedback.

The new version of the launcher went live along with the 22nd update pack. You'll be able to run the game even if the sys req check fails. Chances are that your game will crash. I'm interested in debugging logs generated by both CrossOver and the launcher. See the post I made above on how get them.

The crosstie has been updated to reflect this change but it'll got live as soon as a ninja approves it. Basically the install should now go the windows way: start installer, next,..,next, finish :)

Hello,

THis is a game that really looks awesome. I have followed what you said, and this is my results:

  1. Installed game through crosstie
  2. Changed bottle to Win 7 (on XP install, game did not install, through an error which I didnt write down, but can try again if you want?)
  3. Changed the launcher and js files with the one you mentioned.
  4. Loaded fine (no extra command line commands). Checked system requirements, pass, etc ,etc.
  5. Everything was fine, no problem. I click Play Game
  6. ERROR with AudioDevice. On PC this means there is no usable or installed audio device. On Windows 7, this could happen with certain onboard sound devices if no speakers or headphones are plugged in.
  7. I click OK, and re-open the loading screen. First time continued to show loading circle icon. Second time, the launcher game me a message: Game Exception. Failed unexpectedly.

Link to LOG File created: https://dl.dropboxusercontent.com/u/3431184/Documents/newlog.cxlog

Log from launcher:

[08.22.14 11:05:35.158][Verbose]computing CRC for ..\GameData\Bin\version.Game.txt
[08.22.14 11:05:35.173][Verbose]computing CRC for ..\GameData\Bin\MightyQuest.exe
[08.22.14 11:05:35.340][Verbose]TaskRepairGameVersion::exited
[08.22.14 11:05:35.340][Verbose]TaskRepairEnd::entered
[08.22.14 11:05:35.340][Verbose]TaskRepairEnd::run
[08.22.14 11:05:35.384][Verbose]TaskRepairEnd::exited
[08.22.14 11:05:35.384][Verbose]TaskRepair::exited
[08.22.14 11:05:35.384][Verbose]TaskWaitForLaunch::entered
[08.22.14 11:05:37.549][Verbose][Javascript]hideProgressBar
[08.22.14 11:05:37.549][Verbose][Javascript]showLaunchButton
[08.22.14 11:05:56.680][Verbose][Javascript]_onLaunchButtonClicked
[08.22.14 11:05:56.681][Verbose]TaskWaitForLaunch::exited
[08.22.14 11:05:56.681][Verbose]TaskBeforeLaunchGame::entered
[08.22.14 11:05:56.681][Verbose]TaskBeforeLaunchGame::run
[08.22.14 11:05:56.720][Verbose]TaskBeforeLaunchGame::exited
[08.22.14 11:05:56.720][Verbose]TaskLaunchGame::entered
[08.22.14 11:05:56.720][Verbose]TaskLaunchProcess::entered
[08.22.14 11:05:56.720][Verbose]Force send server heartbeat and wait ...
[08.22.14 11:05:56.721][Verbose]Stop server heart beat.
[08.22.14 11:05:56.873][Verbose]TaskLaunchGame::run
[08.22.14 11:05:56.873][Verbose]TaskLaunchProcess::run
[08.22.14 11:05:56.902][Verbose][Javascript]hideLaunchButton
[08.22.14 11:09:44.656][Error]TaskLaunchProcess::run Game crashed!
[08.22.14 11:09:44.829][Verbose][Javascript]showMessageBox
[08.22.14 11:09:48.296][Verbose]TaskLaunchProcess::exited
[08.22.14 11:09:48.297][Verbose]TaskCheckCrashLogs::entered
[08.22.14 11:09:48.298][Verbose]TaskCheckCrashLogs::Crash log found, or the Bloomberg folder is not empty
[08.22.14 11:09:48.308][Verbose]TaskCheckCrashLogs::exited
[08.22.14 11:09:48.308][Verbose]TaskSendCrashLogs::entered
[08.22.14 11:09:48.330][Verbose][Javascript]showMessageBox
[08.22.14 11:09:49.858][Verbose]TaskSendCrashLogs::exited
[08.22.14 11:09:49.859][Verbose]TaskExit::entered
[08.22.14 11:09:49.869][Verbose]TaskExit::run
[08.22.14 11:09:49.871][Verbose][Javascript]hideProgressBar
[08.22.14 11:09:49.933][Verbose][Javascript]hideProgressBar
[08.22.14 11:09:49.933][Verbose][Javascript]showProgressBar

I am using a Mac Mini 2006.
OS X 10.9.4
2 GHz Intel Core 2 Duo
4 GB 1333 Mhz DDR3
NVIDIA Geforce 9400 256MB (onboard)
Audio:
Built-in Output:

Default Output Device: Yes
Default System Output Device: Yes
Manufacturer: Apple Inc.
Output Channels: 2
Current SampleRate: 44100
Transport: Built-in

Any suggestions? Please help! You have done amazingly so far!

Kind regards
Josh

I forgot to mention... The sound in the loading ubisoft video works fine...?

1 to 34 of 34

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi02LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzMxNDM1MjAzLCJjc3JmX3Rva2VuIjoiVVlBUlJKYno5TXZadmRiZiIsImdkcHIiOjB9