Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
0 
Report this post
...crashes on my Mac Book Pro with Mac OS 10.13.2 (2.8 GHz Intel Core i7, Intel HD Graphics 3000 512 MB).
... it runs on my Mac Book Pro with Mac OS 10.11.6 (2.26 GHz Intel Core 2 Duo, Nvidia GeForce 9400M 256 MB).
MacBook (13-inch, Early 2011)
OS X El Capitan
Version 10.11.6 (15G1217)
Processor 2.7 GHz Intel Core i7
Memory 4 GB 1333 MHz DDR3
Graphics Intel HD Graphics 3000 384 MB
Description of crash: When starting the game, the game just loads into a black screen and a half screen load bar. It used to work until the game updated near new years/christmas. Thanks for your help.
Mac OS 10.13.2 = High Sierra
Mac OS 10.11.6 = El Capitan
Hmmm... could it be an Intel HD Graphics 3000 issue?
My issue is that it just won't launch, and when i try to launch, it completely freezes my macbook and I have to do a hard reboot. Here are my specs:
MacBook Pro (13-inch, Early 2011)
Processor: 2.3 GHz Intel Core i5
Memory: 16 GB 1333 MHz DDR3
Graphics: Intel HD Graphics 3000 512 MB
OS Sierra: 10.12.6
I hope this helps!
MacBook Pro (Retina, 15-inch, Mid 2015)
Processor: 2.5 GHz Intel Core i7
Memory: 16 GB 1600 MHz DDR3
Graphics: Intel Iris Pro 1536 MB
OS: High Sierra 10.13.2
MacBook Air (13-inch, Mid 2011)
macOS High Sierra
Version 10.13.2
Processor 1.7 GHz Intel Core i5
Memory 4 GB 1333 MHz DDR3
Graphics Intel HD Graphics 3000 384 MB
Everything worked just fine until the Christmas update. When starting the game I can only see a black screen and a half full loading bar. Hope you will fix it. Thanks!
Bugs:
- One worker on each side stands outside of my outer wall and starts to run in when the greed come.
- Deer seem to ignore my presence until I am 3-5 feet away from them instead of when my torch's light hits them. The problem here is that they run towards me when I move towards them (even if I move slowly towards them). It is not the same as when they run towards me because I am galloping towards them at full speed. The deer successfully run away when I walk really slow or move left and right rapidly when my light reaches them.
- Pressing backspace while editing the text in "Set Blazon" seems to close the settings window while also deleting one letter from the text field. One walk around I have done is using the delete key instead to delete the text ("…").
- I am not sure if this one is a bug or not, but my friend has the GOG version and his game shows v1.2.10. As a side note, he does not have the current issues I have been facing. The bug here is that in his game there are available mounts in island 1 & 2 while for me I have no mounts available for purchase (3 coins) at a stable. I am not sure if this is because of the version of our games because both of us have tested this with new save files.
- When assigning workers to build outside of the kingdom's walls, one worker seems to run incredibly slow out of the group. For example, when three workers were building the ship and finished, one worker would run as if he were walking while the other two workers were sprinting back to the castle. This happened both during the day and during the night.
- A worker chopped down a tree, picked up the coin after it fell, and did not want to give it to me when we were both stopped.
- This happens 2/5 times: When an archer shoots a rabbit, I am unable to pick up the coin. The coin looks as if it is in the background behind the bushes. No matter how far I walk away from it, I am unable to pick it up myself. The NPCs are the only ones who can pick it up.
I would also like to list two things I have noticed which I am not sure if they are part of the game's engine or considered bugs.
Possible Bugs?:
- When upgrading a peasant into a knight, three or four archers change clothing which I would assume is an upgraded archer as well. The only problem I face with this is that I lose 3-6 archers on each side that can hunt animals. Does upgrading an archer make them lose the ability to shoot an animal that they are standing next to? It matters when I only have 6-12 archers in total. I understand they stick with the knight, so they do not want to leave their side, but if a rabbit is right next to them I don't see why they cannot shoot it. I am not sure if this is done on purpose or if I am facing a bug.
- The number of archers on each side is drastically uneven at times. I do try to recruit vagrants on each side of the castle evenly, but sometimes I still end up with 6-7 archers on the left side and 2-3 archers on the right side. This happens to me after island 1 as well.
Below are the specs of the Mac I have been facing these issues listed earlier on. Hopefully this will help the developer (if they end up reading all of this) in determining the possible solutions to the so-called bugs I may be running into.
Specs:
iMac 5K (Late 2015)
MacOS: OS X El Capitan [v10.11.6]
Processor: 3.3 GHz Intel Core i5
Memory: 32GB 1867 MHz DDR3
Graphics: AMD Radeon R9 M395 2GB VRAM
Feel free to contact me if there is anything else I can provide to help! (:
Not a dev, but a longtime player, so I can address some of these. However, I would suggest that you make general bug reports in a separate thread; a lot of these have nothing to do with playing the game on a Mac specifically, so this thread isn't really the right place for these issues.
1) I assume you're referring to builders. Sometimes the builders hang out by the walls, on hand to repair the walls if the Greed damage them. Yes, sometimes this means they hang out outside the walls until they're in active danger. This isn't great AI, but it's not a 'bug' per se.
2) Deer movement is kind of random and unpredictable. That's how it's always been. Again, not fantastic AI, but not a bug.
3) That's a legit issue for the devs. Sadly, I can't help with it.
4) I don't know if the GOG version numbers are different from the Steam version numbers, but v1.2.10 isn't even out yet, as far as I know; v1.2.8 is the current version, and nothing later than that is listed anywhere. Are you sure you have the right version number for your friend's copy? Either way, the lack of mounts on islands 1 and 2 isn't a bug; what features each island has are mostly randomized. Sometimes mounts will appear, and sometimes they won't. This isn't a bug. (Also, certain features have to be unlocked before they'll appear, by paying for the requisite parchment at signposts. If you haven't unlocked any mounts, they're not going to appear for you ever until you do.)
5) Builders are only guaranteed to run when there are Greed near them, or when they're on their way to an active project. Otherwise, they move at whatever pace suits them. This is an effect of their AI, not a bug.
6) The NPCs don't keep coins. Either you actually picked it up, or the worker gave it to you and you didn't see it. Or, possibly, you needed to walk away from him and walk back to proc the drop. Either way, I've logged far too many hours in this game and I've never seen any NPC refuse to give up coins.
7) This one is a rarely occurring bug, but I've definitely seen it myself. Definitely annoying, and I'm unsure what causes it, but hopefully the devs address it at some point.
8) When a peasant becomes a knight, they gain a retinue of several archers that accompany them. They will claim this retinue - no more than four archers - out of your currently existing archers, who will change clothes to signify their new status as squires. Squires stay with the knight, and do NOT hunt, so if you make knights too soon, this can definitely cut into the money you get from your archers hunting rabbits and deer for you. However, this is not a bug, but a feature - squires not hunting is the tradeoff for being able to send a knight and his retinue out to destroy Greed portals.
The other benefit to knights and their retinues is that they're smarter (or more cowardly) than regular archers; when a wall a knight is defending takes too much damage, the knight will take his squires and fall back to the next closest wall. This also has its tradeoffs and drawbacks; if your defense is mostly knights and squires, and a wall takes too much damage, they'll run away and the wall will probably get knocked down because 80% of your fighting force ran away while it was still standing. But at the same time, regular archers don't retreat until they're practically being hit, so you're a lot less likely to lose knights and squires in an attack than you are regular archers.
Long story short - squires are a feature, not a bug. But you have to carefully consider when you want to create knights, and ideally build up a big army of archers before you do so that you have some archers and squires. Remember that, if you're not ready to be destroying Greed portals yet, knights aren't a very worthwhile investment. Wait until you need them, if possible.
9) The game seems to assign archers to each side pretty much at random, no matter which side you recruit peasants from. Sometimes those assignments suck. However, archers do run back and forth between each side regularly...although that can cause problems too, especially on larger islands if you've expanded outwards a long way in either direction. Your archers will spend 90% of their time running back and forth, and maybe 10% of their time actually being useful. Not exactly a bug, but poor AI that I'd love to see the devs improve. (Not sure if they will, though...especially when they've got a lot of things to fix right now, post-Skull Island updte, that actually are bugs.)
Honestly, I really don't know if any of these are Mac-specific issues, and most of them aren't even bugs. I'd suggest you take the ones that are bugs, or sub-optimal game performance, and put them in a new thread in a more appropriate place. I hope I've at least clarified some things for you, though.
macbook air 13" mid 2011
1.8GHz Intel Core i7
4GB 1333MHz DDR3 ram
Intel HD Graphics 3000 384 MB
it seems like integrated graphics 3000 is a common factor?
I played Kingdom classic before and it worked with no problems.
Macbook Pro 13'' (late 2011)
macOS Sierra
2,4Gz Intel Core i5
4 GB 1333 MHz DDR3
Intel HD Graphics 3000 384 MB
Weird thing is the game ran fine once, then second (third?) time I booted it, game freezes on boot.
High Sierra 10.13.4
MacBook Pro 13" (Early 2015)
3.1 GHz Intel Core i7
16GB 1867 MHz DDR3
Intel Iris 6100