ติดตั้ง Steam
เข้าสู่ระบบ
|
ภาษา
简体中文 (จีนตัวย่อ)
繁體中文 (จีนตัวเต็ม)
日本語 (ญี่ปุ่น)
한국어 (เกาหลี)
български (บัลแกเรีย)
Čeština (เช็ก)
Dansk (เดนมาร์ก)
Deutsch (เยอรมัน)
English (อังกฤษ)
Español - España (สเปน)
Español - Latinoamérica (สเปน - ลาตินอเมริกา)
Ελληνικά (กรีก)
Français (ฝรั่งเศส)
Italiano (อิตาลี)
Bahasa Indonesia (อินโดนีเซีย)
Magyar (ฮังการี)
Nederlands (ดัตช์)
Norsk (นอร์เวย์)
Polski (โปแลนด์)
Português (โปรตุเกส - โปรตุเกส)
Português - Brasil (โปรตุเกส - บราซิล)
Română (โรมาเนีย)
Русский (รัสเซีย)
Suomi (ฟินแลนด์)
Svenska (สวีเดน)
Türkçe (ตุรกี)
Tiếng Việt (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
กฎและแนวทางปฏิบัติในกระดานสนทนา
รายงานโพสต์นี้
Have you run that, Copied it and sent it off to support? That would be very helpful to solve your issue.
Send them that, and the error log, It's kinda hard to fix a bug that they have no idea what is happening in your particular case. It's obviously not a wide spread issue, so you need to do your part.
I'm not surprised the settings crash is still around though, Battle for the Bosporous has had the same cadre of bugs since launch and they have shown no interest in investigating it.
It's honestly a tragedy how frequent bugs of any kind have gotten. Used to be able to reliably know that the only kind of issues a player would encounter, say in EU4, were bugs you had to actually cause and which could be used to do cursed things like Ryukyu world conquest.
I've probably spent 9 hours so far doing every single thing you can think of trying to find out what it is specifically, then it would be replicable, and that would take the legwork out of a hotfix, but nothing, the error logs, anything have given me anything I can make sense of, and I haven't heard back from the devs.
800 hours on CK3 and it was only from Royal Court on that I experienced any crashes whatsoever, 3000 in CK2 and I have never had it crash, not even once. No idea if they just slackened the standards or if it's some bizzarely niche thing that is based on a fault in my OS (Windows 10), I mean I really am at a loss. Most of the reports I've combed through just say what they were doing, and that it crashed.
I thought maybe I'd found something when I saw someone post a log that specifically mentioned another application crashing at the same time, but it was OneDrive, and they had the game downloaded on OneDrive, which I don't, so I don't know if that's a different issue/crash, or if the crash is itself so volatile that it nukes other things. Usually my crashes are just crashes of the normal variety, but a few have crashed Steam as well. Additionally they seem wholly independent of anything you'd think.
My rig is old, not like, fossilized, but not new. In spite of that, it is a gaming rig, it runs major AAA system-hogs without issue.
One that I can reliably reproduce is a crash that involves changing the graphics preset. That causes a kind of pop-in that I recognize from earlier Royal Court loading crashes, and the new crashes with the barbershop. The models and graphics stutter, get really fuzzy, then a CTD. I've spent a few hours running clean installs just to see if I can make some sense of some of this, but after a few crashes the game stops being able to even launch and crashes while it's launching, forcing me to do another purge, which is terribly time-consuming.
I really want to figure out what it is specifically, or at least a way to avoid it until people more capable than me can fix it.
I've tried installing to different drives, I have three, but that doesn't seem to really do anything. I don't use mods, of any kind, for CK3. I had thought maybe that just the act of having the Game of Thrones mod installed, if not active, might be the issue, purged it, then purged the files and reinstalled it, same issue.
My next idea that I have is just dropping every setting to an absolute minimum to see if that effects the popin and whatnot.
It feels like the crash is rooted in too much happening graphically for some reason, because even dropping texture quality causes a popin and freeze, though it does not, interestingly enough, cause it to crash /most/ of the time (it has a few times, but it is not reliable, so maybe it's an optimization bug?)
Unsure.
Only suggesting i can make,
Run all windows updates and graphics/sound drivers, Reinstall your chip set, Chipset is super easy to check and often one that gets over looked the most. You need to know exactly what mother board you have and goto their manufacture page, You can also read up on all the other updates/fixes for your board.
Run userbenchmark.com and see if anything gets flagged, For example, memory can often be set wrong especially if it was just used on default, simple things like XMP was never turned on, but it can flag lots of issues.
Grab CCleaner, and check the driver update tool, Manually update things that are not done with normal windows updates, Sometimes intel and random things will have updates that don't update under normal windows updates. a computer is only as good as it's weakest driver so to speak.
Turn off everything else, including your virus scanner, and just run the game and your basic Graphics/sound suites, turn off everything else on on start up, just run your basic windows, start steam and then the game. There can always be a conflict causing an issue. This is the only way to rule that out.
Run Scan disk from system tools, Run Defrag if the game is on an HDD, Don't run defrag on an SSD. Perhaps run a Ram test as well.
(Big disclaimer anyone that doesn't know what i'm talking about next should really Watch some videos and read the motherboards owner manual before even thinking about attempting this. You can even also call the manufacturer if needed as they can walk you through it step by step. Screwing this up can mess up your comp permanently, but with a bootstick, EZ flash and resources people should be able to tell if they can do this type of update or not. Don't if you are not 100% certain of your abilities. It's not risky like over clocking, but it needs to be done exactly as they say or your may find yourself in need of a new mother board, You are warned.)
Check your mother board manufacturer and see if your bios is up to date. If its not i'd do that as well. Often stability is one of the biggest fixes outside of added support that gets done post release and more often than not even direct from a seller or factory the bios isn't updated. I've seen plenty of pre-made systems that never had it updated as well, so unless you've done it, it often is not done. Again, Don't attempt this unless you are sure of your ability, i can't stress this enough, If anyone needs more advice on this, you can message me or go watch one of the 100's of youtube vids on your exact board.
This stuff is just typical normal proper set up stuff, You'd be surprised how often these steps fix issues.
I will just add, I wish they would use the BETA opt in more, so the current play that the masses are on is a bit more bug free, verse having to roll back to more stable patches. I personally can't wait for a nice stable version of this build before i really start putting any sort of time into the game. I play on slow, so putting 20-30 hours into something to have it bug out that an average player would of found in a single night while might be maddening for them, imagine spending an entire month on your play and having it happen. Robe was pretty solid, these last few months not so much.
Good luck.
I did a near-total purge of a third of my drivers and reinstalled them, which has seemingly improved stability, maybe even fixed the issue, though I'm not sure yet.
Okay, so, 1.9 and 1.9.1 introduced a fairly large number of new shaders and graphical updates to the game, which are currently throttling it and causing conflicts with even mildly out of date drivers, and in my case, drivers that were current (first thing I tried was driver updates, weirdly enough.)
Updating drivers will fix the crashing for some people, reinstalling them will cover another group of affected people, but there's some funky optimization issues currently that might just be unfixable for others. Clean reinstalls that purge both CK3 folders, and update your graphics drivers, and it will most likely let you in for the time being.
I anticipate future patches will unbork the issue on a broader scale, but it is currently incumbent on us to ducttape it together so we can play the game in the meantime.
Did you play Mount & Blade 2: Bannerlord during Early Access, there was an Patch, who only the half of all Players, where able to play the Game, the other half, where not able to play the Game at all.
So do not say, it would be for all Players, it depends on the Devs.
And the Devs of CK3 did something wrong with this Patch for sure.
Did you post a report without even "mildly" updating your drivers? lol
What a way to waste everyone's time, mate. I run this thing on a potato using Win 8 with no crashes so it's 100% a hardware issue.
Lots of potato talk as your suggested fix.
Ive had a handful of full hard crashes. But just that, only a handful in over 3500 hours
I'd get this line of inquiry if I didn't have 800 hours on the game and hadn't only experienced such a drastic alteration to the game after I updated the game.
Pack it up fellas, we wasted Koro's time. He's got a bad PC and his game doesn't crash. Pack it up, it doesn't happen.
What is the goal with this my guy. What is the goal with this kind of post. All it did for me was make me feel kind of... confused.
Mostly with the "mildly," what was even... why did you write the word mildly in quotes like it was referencing something in what you responded to.
Curb the weird arrogant talking-down to random people dude, it isn't a flex when you say you don't have an issue and have 3500 hours. That isn't a flex. Your lack of an issue is not indicative of nobody else having it. If it was then development teams for games wouldn't need several PCs of wildly different makeups, they would just chain one guy up in a basement with a PC running Windows Vista and that would work. Someone has a bug? Grab the beating stick and go see what Bert says, if the Vistinator has it, beat Bert for his failures, if it doesn't, beat him anyways but praise his diligence.
And bizarrely enough, despite it apparently being a hardware issue, it only cropped up simultaneously on multiple systems after a patch. It has not manifested on any other games, even those running on the same engine. It goes away when rolling back to pre-Tourneys patches. Nothing else anywhere else is affected. Just this one game.
That's a pretty weird hardware issue, barring like, a vengeful spirit that just really hates CK3 infecting a few hundred/thousand (I have no idea how many people it affects, enough that people have been complaining and asking since around May 15th.) people, it doesn't really make sense to me that it's related to my hardware, which is a 4K rig and runs literally everything else fine.
I was off by like 4 days, it was May 11th when people started posting about it, which yeah that was the launch date, my bad.
I have no idea why Paradox Steam forums of any game are so infested with people that act like this.
Someone literally finds something that might help alleviate a bug that people have been reporting for nearly 30 days? Waste of time, better be toxic and self-centered, because if I don't have issues, it's a hardware issue. (No it's not :)
Typically when people have hardware issues, they come about in the form of like, when they're first trying to play a game, or if their PC is in the process of dying. My PC seems fine, and I only started getting these crashes after 800 hours. I have literally been playing CK3 on max settings since it launched, as in I have played it since day one, and didn't have a single crash until after Royal Court. It didn't get this bad until 1.9, and people have been reporting the same thing since the launch of the patch.
I got lucky, and happened to find something that seemed to have a positive result. Other people have not had that same luck, Hell, there are people who did clean reinstalls of the game and that fixed the issue.
That's just how it is with game bugs. They are just like that. I feel like you need a hug or something man.
If the weird "mildly," bit is a reference to if I ran dxdiag or not /before/ I reinstalled a few drivers, yes. I did. Nothing was out of the ordinary, and much to my frustration, for a hot minute the game wasn't even crashing in a way that produced error logs. But, mercifully, I was able to get one after awhile. Again, much to my frustration, it was just... nothing. I scoured that thing for an hour, and everything was totally generic, nothing that was diagnostically useful.
Considering that the update changed how textures are loaded, tbh, I'd say the fact that the issue is so comparatively light in contrast to what Leviathan was shows that it's at least well-made and was probably pretty rigorously bugtested.
Oh I forgot that I had the audacity to say that I anticipated that out of date drivers, no matter how mild, I.E. that if my current, not out of date even by one update weren't immune, mildly out of date ones were probably going to be even worse off.
No idea what about calling drivers that aren't covered in dust, and which are only an update or two off "mildly out of date" seemed like it was ripe for smarmy toxicity, but I mean, that's what was picked.
Doesn't the very fact that self-described potato systems *can* run CK3 just fine... kind of itself show that the issue is much more likely to be patch-based? If a bad system can run a game without issue, but a 4K rig cannot, and there were suddenly a large number of people all reporting the same issue ONLY after a patch, doesn't seem like obvious, textbook bug behaviour?
If a system can do everything else, except this one thing which only became problematic after a patch to it, usually the issue isn't that the hardware has a grudge. It's that there is something that just doesn't work within a patch. And patches are very complex, they have dedicated PCs that range in specs and the like that try to replicate bugs. In spite of this, I know of dev teams that could not, in-house, replicate them. There are bugs so niche that only a handful of people will ever find them.
This just isn't one. It's not one I would say even 40% of the playerbase has, it is part of a generally stable patch that most people aren't having issues with.
But it isn't just a handful of folks that got this going on, and again, it only began with 1.9. It happens on any graphical settings, and can crash the game in many ways.
The error log was wholly generic, I combed everything I could and it was all nonspecific, no mentions of OneDrive like the other guy, nothing I could use. I tried something, and it worked well enough.
It will help some people the same way clean reinstalls did for some and not me.
You didn't have an issue, yet you came here anyways, and wrote a passive-aggressive snide comment about how it wasted your time.
??????????
You came to a thread about an issue you hadn't experienced and expected to somehow fix an issue you didn't have?
Kind of a goofy thing to do, tbh.
stop.