-
Notifications
You must be signed in to change notification settings - Fork 64
CQUI stuck on loading screen in Linux #575
Comments
I too am seeing "Please Wait..." immediately after starting a new game with CQUI under Steam/Civ6/linux. No actual lua log ever generates. I literally reinstalled the game clean, removed all the steam subdirectories to get a completely clean install. The issue persists. If I disable CQUI, and begin a new game, no issue. I'll happy provide whatever I logs I have but since I literally cannot make the first move in the new game, there don't appear to be any relevant logs generated (moddling.log exists, but lua.log does not.) Please let me know what other logs I might provide if these can help. Thanks! |
Issue was caused by a case sensitivity issue. Aspyr really did a hatchet job with the port in terms of mods. The files are case sensitive on Linux, BUT they don't use the same case pattern as any other release. Why? Dunno, but it can cause issues like these sometimes. A fix should go live later today |
Thank you!!! Much appreciate your help!
…On Sat, Jul 8, 2017, 12:51 PM Chris ***@***.***> wrote:
Issue was caused by a case sensitivity issue. Aspyr really did a hatchet
job with the port in terms of mods. The files *are* case sensitive on
Linux, BUT they don't use the same case pattern as any other release. Why?
Dunno, but it can cause issues like these sometimes. A fix should go live
later today
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#575 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHu9x8TEcec_9TgpHS52_bBGp6cKhY3iks5sL7OIgaJpZM4OP6-V>
.
|
Hi Chaorace this is still occurring even after subscribing and unsubscribing under Linux. Does the GitHub fix push to the Steam Workshop? I've tried this again with the completely new game. |
@corq The workshop updates weekly. Fix is live to Steam as of 30 minutes ago |
Thanks! Played several hours overnight, appears to be working great! |
Yeh can confirm under Ubuntu and most recent update this behavior is definitely back. |
Active development is over here now: https://github.com/Azurency/CQUI_Community-Edition |
Thanks - I think I saw that the cqui bug I filed had been moved over there
already.
…On Sat, Nov 18, 2017 at 12:00 AM, ProustIdee ***@***.***> wrote:
Active development is over here now: https://github.com/Azurency/
CQUI_Community-Edition
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#575 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHu9x7sXZuko6LMdzfRKr2gNPPnjSi2gks5s3mR5gaJpZM4OP6-V>
.
--
__________________________________________________________________________________________
QTH KORL Winter Park, Florida | Icom R75 | RFSpace SDR-IQ::Pixel Loop RF-1B
| Uniden HP2
SDR Captures/loggings posted to: https://corq.co when audio quality allows.
__________________________________________________________________________________________
|
It took some troubleshooting but after some painful research (including a complete deletion and re-installation of Civ 6 on steam) I've determined that, alas, the problem is with this, my all-time favorite, seemingly must-have Civilization 6 mod.
Here's what happens when it's enabled. I start the game - fine so far. But then I either load a game or create a new one, and i get a hang state. For new games, it just sits on 'please wait' forever until I have to kill the process. On loaded games, I can't access orders for any units at all, so same sad conclusion.
I have no idea what's causing it BUT I have determined that there's some sort of error with map generation when CQUI is in use. I could possibly recreate the problem and send copies of my console yelling about it but I kind of hope to avoid that. Would really love to see this issue resolved because it makes the game so much more playable when it works. Heck, I love it enough that I created a github account to mention the problem!
The text was updated successfully, but these errors were encountered: