CS GO is not launching since I updated my software to High Sierra (SOLVED)

[77CM ♔ pΛshΛ o7]

First of all, I contacted with Steam Support, searched every possible solutions in Google for like 7-8 hours, did read all the topics in Steam Discussions, nothing helped, so I decided to open my own post.

I had Mountain Lion in on my Mac, a few days ago I bought a SSD and removed my HDD, I installed clean High Sierra, Steam and CS GO. Now it says the game is running, my friends says I am in the game but I can't see it in task manager. When I check it from Activity Monitor, I can see it.
I tried to launch another game ''This War of Mine'' it worked properly.
I contacted with Steam Support, they told me to put ''-config -safe -autovid'' to CS GO options, didn't work. Eventually they said, they can't help me anyhow?!

The weird part is I can see the Steam in -----> MACOS/Applications

But CS GO is at -------> MACOS/Users/fatihsmbp/Applications

I am not sure if it was like this before. (in mountain lion)


I verified integrity of game files 5 times, re-installed to Steam and CS GO 3 times.

I decided to launch it from ----> MACOS /Users/fatihsmbp/Library/Application Support/Steam/steamapps/common/Counter-Strike Global Offensive/csgo_osx64, in terminal it says

Fatihs-MacBook-Pro:~ fatihsmbp$ /Users/fatihsmbp/Library/Application\ Support/Steam/steamapps/common/Counter-Strike\ Global\ Offensive/csgo_osx64 ; exit;
Failed to load the launcher (dlopen(bin/osx64/launcher.dylib, 2): image not found)


I have the launcher.dylib in
---> . /Users/fatihsmbp/Library/Application Support/Steam/steamapps/common/Counter-Strike Global Offensive/bin

but I don't have it in
---> . /Users/fatihsmbp/Library/Application Support/Steam/steamapps/common/Counter-Strike Global Offensive/csgo/bin/osx64

does it makes any difference? or is it supposed to be like this?
I tried to copy launcher.dylib to there but it makes no difference.

If you guys know anything please help me. I really missed to play this game. We can make Skype call or something if you like to.

[77CM ♔ pΛshΛ o7]

引用自 Kachowski：

Man, i'm really upset with this same issue. I already tried every possibles ways to fix this problem but it seems like a problem without solution...
I hope Steam look for our, poor guys suffering with this. this not lookin like a PC or files issue, but looks like a compatibilitie one. Waiting for a update that will correct this,

'cause I saw so many people with the same issue in every part of internet and none has the solution. I bought a MacBook but i'm thinking in come back to windows, there I never had this problem.

Salutes from Brazil.


PS: STEAM/VALVE: FIX THIS PLEASEEEE WE JUST WANT TO PLAY CS:GO

Well, we should admit it's not a game computer but I like to use it and I am sure you will love the daily usage of Macbook as well, so you won't really mind the performance in gaming :D
Cause I play only 1 game, which is Cs Go, and my Mac can handle it (at least it was use to before I broke it lol) so don't give up brah! Salutes!!

[Black]

引用自 Sep102：

Do you know if you have the same case-sensitive filesystem issue here or is the problem that you upgraded to High Sierra and now things aren’t working properly in Steam and games?

If you need to check you can use the Disk Utility program to find out. Select your install drive (probably named Macintosh HD) and go to the File menu and Get Info. There should be a field in the window that opens that reads like “Is Case-Sensitive”.

I made the steps you wrote and find out that I have the same case-sensitive filesystem, it's cleary saying it on get info. PS: I didn't played any game before in Steam using macOS, it means that I don't know if my problem would exist in lower mac systems.


Sorry for my english. Waiting for a asnwer

[Black]

引用自 J4mes M0riarty P4sha：

引用自 Kachowski：

Man, i'm really upset with this same issue. I already tried every possibles ways to fix this problem but it seems like a problem without solution...
I hope Steam look for our, poor guys suffering with this. this not lookin like a PC or files issue, but looks like a compatibilitie one. Waiting for a update that will correct this,

'cause I saw so many people with the same issue in every part of internet and none has the solution. I bought a MacBook but i'm thinking in come back to windows, there I never had this problem.

Salutes from Brazil.


PS: STEAM/VALVE: FIX THIS PLEASEEEE WE JUST WANT TO PLAY CS:GO

Well, we should admit it's not a game computer but I like to use it and I am sure you will love the daily usage of Macbook as well, so you won't really mind the performance in gaming :D
Cause I play only 1 game, which is Cs Go, and my Mac can handle it (at least it was use to before I broke it lol) so don't give up brah! Salutes!!

Oh man, I really loved how macOS systems work. I just play one game too, wich is Cs:go, and I was pretty good when played in my old Windows and I want to go back to my old gold days hahahah. I hope find a solution for this big problem. Hope u come back to the game too. Salutes!

[77CM ♔ pΛshΛ o7]

引用自 Kachowski：

引用自 J4mes M0riarty P4sha：

Well, we should admit it's not a game computer but I like to use it and I am sure you will love the daily usage of Macbook as well, so you won't really mind the performance in gaming :D
Cause I play only 1 game, which is Cs Go, and my Mac can handle it (at least it was use to before I broke it lol) so don't give up brah! Salutes!!

Oh man, I really loved how macOS systems work. I just play one game too, wich is Cs:go, and I was pretty good when played in my old Windows and I want to go back to my old gold days hahahah. I hope find a solution for this big problem. Hope u come back to the game too. Salutes!

The touchbar, system and battery health is more than enough. It's been 3 years and still it can stand 5-6 hours with full charge. Amazing.
To be honest, you probably will not get the same efficiency you use to get in your Windows, but you will be fine anyway. Since you closed everything behind the CSGO, you can easily play around 70-80 fps and I think it's acceptable.

Let's fix this damn error and destroy to Dust 2 together!

[Black]

引用自 J4mes M0riarty P4sha：

引用自 Kachowski：

Oh man, I really loved how macOS systems work. I just play one game too, wich is Cs:go, and I was pretty good when played in my old Windows and I want to go back to my old gold days hahahah. I hope find a solution for this big problem. Hope u come back to the game too. Salutes!

The touchbar, system and battery health is more than enough. It's been 3 years and still it can stand 5-6 hours with full charge. Amazing.
To be honest, you probably will not get the same efficiency you use to get in your Windows, but you will be fine anyway. Since you closed everything behind the CSGO, you can easily play around 70-80 fps and I think it's acceptable.

Let's fix this damn error and destroy to Dust 2 together!

It's more than sufficiente! hahah. Sure we will destroy in the maps after I fix it. Just wait a little time and u will receive a message to play. HOPE

[Sep102]

引用自 J4mes M0riarty P4sha：

https://ibb.co/kaimRS
https://ibb.co/bL7rt7
https://ibb.co/ircPD7
https://ibb.co/mpsrt7

I wasn't able to unite them so I am sending these separated. This is my disk utility,

I did something wrong, now I can't save even an image to desktop.

1) Do you think it will be okay if I make option-cmd-R movement and install older system?

2) I have my old hdd, which has ''high Sierra installer'' inside. I will buy the connector tomorrow.
So maybe I can connect the HDD to my Mac, then I can choose it as start-up disk, so I will be able to delete everything inside the SSD, cause now I can't delete any thing. Eventually, I will create the new system.

Which one is a better idea? 1st or the 2nd?

By the way, I admire your patience dear Sep102, you're a lifesaver!

The second is definitely the easier of the two methods, once you have a separate drive to boot from you won't have any issues properly erasing this one.

How are you currently booting into macOS for those images? Are you booted into macOS off of the volume in "Container disk2"? If so have you been trying to reinstall macOS to that container or to "Container disk1", and if so were you trying to delete "Container disk1" as part of the reinstall process?

I haven't run into the same pre-boot creation failure that you have so I'm not sure what the steps are that you went through that resulted in it, but this is what I would try in your situation (you can let me know if this is what you did in the first place):

1) Select "Container disk1", right-click and select "Add APFS Volume..."
2) Give it a name and select APFS or "APFS (Encrypted)" as the format
3) Start the High Sierra installer (the "Install macOS High Sierra" from the App Store)
4) Select the new volume I created in steps 1&2

[77CM ♔ pΛshΛ o7]

引用自 Sep102：

引用自 J4mes M0riarty P4sha：

https://ibb.co/kaimRS
https://ibb.co/bL7rt7
https://ibb.co/ircPD7
https://ibb.co/mpsrt7

I wasn't able to unite them so I am sending these separated. This is my disk utility,

I did something wrong, now I can't save even an image to desktop.

1) Do you think it will be okay if I make option-cmd-R movement and install older system?

2) I have my old hdd, which has ''high Sierra installer'' inside. I will buy the connector tomorrow.
So maybe I can connect the HDD to my Mac, then I can choose it as start-up disk, so I will be able to delete everything inside the SSD, cause now I can't delete any thing. Eventually, I will create the new system.

Which one is a better idea? 1st or the 2nd?

By the way, I admire your patience dear Sep102, you're a lifesaver!

The second is definitely the easier of the two methods, once you have a separate drive to boot from you won't have any issues properly erasing this one.

How are you currently booting into macOS for those images? Are you booted into macOS off of the volume in "Container disk2"? If so have you been trying to reinstall macOS to that container or to "Container disk1", and if so were you trying to delete "Container disk1" as part of the reinstall process?

I haven't run into the same pre-boot creation failure that you have so I'm not sure what the steps are that you went through that resulted in it, but this is what I would try in your situation (you can let me know if this is what you did in the first place):

1) Select "Container disk1", right-click and select "Add APFS Volume..."
2) Give it a name and select APFS or "APFS (Encrypted)" as the format
3) Start the High Sierra installer (the "Install macOS High Sierra" from the App Store)
4) Select the new volume I created in steps 1&2 [/quote
yup I exactly did the same thing. I installed the High Sierra to Volume 2 but I didn't choose it as encrypted. But it happened so this is where I've failured. I will try the 2nd way tomorrow. If I am not going to failure with the erasing the current connected SSD, I think I will be fine. I will chose my seperated HDD drive as current start-up disc.

[77CM ♔ pΛshΛ o7]

引用自 Sep102：

引用自 J4mes M0riarty P4sha：

https://ibb.co/kaimRS
https://ibb.co/bL7rt7
https://ibb.co/ircPD7
https://ibb.co/mpsrt7

I wasn't able to unite them so I am sending these separated. This is my disk utility,

I did something wrong, now I can't save even an image to desktop.

1) Do you think it will be okay if I make option-cmd-R movement and install older system?

2) I have my old hdd, which has ''high Sierra installer'' inside. I will buy the connector tomorrow.
So maybe I can connect the HDD to my Mac, then I can choose it as start-up disk, so I will be able to delete everything inside the SSD, cause now I can't delete any thing. Eventually, I will create the new system.

Which one is a better idea? 1st or the 2nd?

By the way, I admire your patience dear Sep102, you're a lifesaver!

The second is definitely the easier of the two methods, once you have a separate drive to boot from you won't have any issues properly erasing this one.

How are you currently booting into macOS for those images? Are you booted into macOS off of the volume in "Container disk2"? If so have you been trying to reinstall macOS to that container or to "Container disk1", and if so were you trying to delete "Container disk1" as part of the reinstall process?

I haven't run into the same pre-boot creation failure that you have so I'm not sure what the steps are that you went through that resulted in it, but this is what I would try in your situation (you can let me know if this is what you did in the first place):

1) Select "Container disk1", right-click and select "Add APFS Volume..."
2) Give it a name and select APFS or "APFS (Encrypted)" as the format
3) Start the High Sierra installer (the "Install macOS High Sierra" from the App Store)
4) Select the new volume I created in steps 1&2

Show time!
I choose the 2nd way, I choose the external HDD as start-up disc, in that time I was able to erase everything inside the SSD, then I tried to install to Sierra to my internal SSD, after it laptop is frozen, so I closed it, I did the install via cmd+R,

Currently, I have Yosemite X in my SSD, but the thing is, now I can't connect but HDD to laptop, it's just doesn't show up(?) I can see the light on the SATA to USB devide but I can't see the HDD in anywhere disc utilities etc.

I didn't really like Yosemite and I am not able to upgrade to El Capitan, so what do you suggest guys?
Old Yosemite, or High Sierra?

[Sep102]

Could you clarify, can you not boot into the macOS install on your external drive anymore, even by holding down option at startup and waiting for it to show up? Or does it just not show the drive in disk utility when you’re booted into Yosemite?

I’d suggest installing High Sierra if you can. How did you end up with Yosemite on your internal drive exactly? Is that the version of macOS that you had loaded on the external drive?

If you do already have Yosemite on your SSD now I’d try running the High Sierra installer from off the App Store while booted into it and see if upgrading it completes successfully.

[77CM ♔ pΛshΛ o7]

引用自 Sep102：

Could you clarify, can you not boot into the macOS install on your external drive anymore, even by holding down option at startup and waiting for it to show up? Or does it just not show the drive in disk utility when you’re booted into Yosemite?

I’d suggest installing High Sierra if you can. How did you end up with Yosemite on your internal drive exactly? Is that the version of macOS that you had loaded on the external drive?

If you do already have Yosemite on your SSD now I’d try running the High Sierra installer from off the App Store while booted into it and see if upgrading it completes successfully.

I am writing the code to Terminal ''volume'' something, even there I can't see my external drive. Only my current SSD. I can't see it anywhere, maybe the converter is broken but dunno I just bought it.

I can update to High Sierra but for now I will stay in Yosemite until the next weekend, I don't have enough time for it.

This is what happened;
SSD was my internal drive. I connected the HDD to my laptop via ''Sata to USB'' converter, I choose the external drive (HDD) as start-up disk. After it opened, I went to Disc Utilities and FINALLY I was able to delete everything inside my SSD.
I had the Sierra Instellar in my HDD, I launched it, choose the SSD to install, then it's just frozen. I didn't do anything for 40 minutes, then I checked, even the time clock was frozen, so I closed it.
I started up, I went to recovery mode and eventually my Mac choose to install Yosemite.

But I can't see my external drive in Yosemite anyway. I was able to see in when I had the Capitan (HDD) either the High Sierra (SSD). That is just weird.

[Sep102]

Gotcha, I think I have a better idea of what happened. I can’t explain why Yosemite can’t see your external drive anymore but I’m pretty sure the reason you have Yosemite installed is because you booted into the internet recovery mode which installed whichever version of macOS Apple says should be installed for your version of MacBook.

At this point you should be fine upgrading to High Sierra whenever you have time for it, everything should work fine running it locally on the SSD. Just when you do, ensure that you choose plain APFS for your filesystem if it asks you (I believe it asks you during the installer if you want to convert to APFS but I honestly don’t remember for sure).

[77CM ♔ pΛshΛ o7]

引用自 Sep102：

Gotcha, I think I have a better idea of what happened. I can’t explain why Yosemite can’t see your external drive anymore but I’m pretty sure the reason you have Yosemite installed is because you booted into the internet recovery mode which installed whichever version of macOS Apple says should be installed for your version of MacBook.

At this point you should be fine upgrading to High Sierra whenever you have time for it, everything should work fine running it locally on the SSD. Just when you do, ensure that you choose plain APFS for your filesystem if it asks you (I believe it asks you during the installer if you want to convert to APFS but I honestly don’t remember for sure).

I have the same though as well. By the way, yes it asks to AFPS while installing it, I remember in the first time, I had a computer programmer with me he choose case-sensitve system but we didn't know it will bring that much problem beside :D



edit: can I ask you, which codes in launcher you're using for fps?

[Sep102]

That’s funny and makes a lot of sense, I could very well see myself being guilty of such a thing in the past helping my own friends with their setups. I imagine there’s a good chance he runs Linux at home, everything has been case-sensitive pretty much forever on Linux so that’d make complete sense why he’d recommend it for macOS.

Unfortunately we don’t get the luxury to choose how our setups go without potentially breaking things :P

[Raymoo’s big journey in Glimp]

Thank god my mac is 5 years old and does not run high sierra.

Somehow all my games like gmod and CS:GO work great!

Hope you fixed it!

[Sep102]

引用自 Shagster：

Thank god my mac is 5 years old and does not run high sierra.

Somehow all my games like gmod and CS:GO work great!

Hope you fixed it!

Actually there are plenty of people that don't have High Sierra but have case-sensitive filesystems that cause them issues, there are several threads on this forum to that effect. What High Sierra did was adding another event where people could make the choice (accidentally or intentionally) to convert their filesystem to case-sensitive. Just having High Sierra isn't all that bad, it's been running well for me since the betas even.