UE5 and VSC issues with Mac OS really needs to be addressed pls

Unreal Courses Ask
,
#1

I can’t get Xcode or VSC working on MacOS with UE5. Project seems to set up ok in VSC, but the moment I add a C++ Actor from UE, include issues abound. Some helpful person in the UE Slackers Discord sent me to:

https://pdl39.medium.com/how-to-fix-vs-code-intellisense-error-squiggles-for-unreal-engine-projects-5fd9d4aacb7e

Unfortunately this is above my level as a newbie to follow despite much mucking about. Clearly there is a well understood problem here. Seems like a “clang” install is necessary - also adjustments need to be made to JSON files (such as version number missing in cpp_properties and compiler file path)? Please advise. This course is essentially useless to a MacOS user as it stands. Very frustrating and need to get this working please. Thank you!

just some other notes:
rolled back Xcode to 13.2.1 because apparently there are known issues with the latest version - roll back didn’t help.

Mac OS 12.3.1 running on M1 Max 32 core GPU, 32GB unified RAM
Visual Studio Code version 1.67.1
Visual Studio 8.10.23.7

#2

What trouble do you have installing that extension? The instructions are rather clear IMO

direct link to the instructions:
vsc-ext-ue4-int-fixes.md · GitHub

#3

I followed the instructions, but it still didn’t work so I have no idea what’s going on. I suspect that I’m misunderstanding the instructions but I have no way of knowing. Given that this is obviously not just me, it would be helpful to have a video on specifically how these steps are implemented. I’m quite frustrated tbh primarily because I don’t know what I’m doing wrong or if it’s even me. Clearly the Unreal team has prioritized Windows first and I do have a windows machine but it’s a desktop and I’m limited by how much time I can spend in front of it. Obviously this is going to be an issue for anyone else trying to take this course on MacOS so it seems critical to have a walk through.

Thank you

#4

Could you show the output of the extension? From the output window use the drop down menu on the right to select it

output
output1512×172 9.1 KB

Also I think the extension isn’t currently working with M1 macs, there’s an issue about it and the author is trying to fix it.

Edit: here’s the issue https://github.com/boocs/ue4-intellisense-fixes/issues/10

#5

Thank you Dan. I’ll look at this later today. I really appreciate the support. :wink:

#6

here’s the output log. Thank you Dan! Btw, as I am browsing the above link, I see there is a stipulation about C++ 17. I have tried both C++ 17 and 14. Neither work.

Screen Shot 2022-05-17 at 10.11.13 AM
Screen Shot 2022-05-17 at 10.11.13 AM3228×1884 739 KB

#7

ok, having read through the GitHub link, it appears that this remains unresolved (as you suggest the extension isn’t currently working).

So I have two dumb questions (forgive me because I’m just unfamiliar with the context of coding expectations in a general sense):

  1. I realize this isn’t GameDev’s issue specifically, but in a general sense, how long do such bugs often take to clear up? I assume that Epic’s Unreal team will ultimately resolve this problem (pretty amazing to me that they shipped UE5 to MacOS with this not fixed although I suppose that’s neither here nor there).
  2. I suppose I could just try on my own, but in the interest of not going down a path of more frustration, does this Intellisense issue cause inoperable problems for the functioning of UE5 and VSC? In other words, will this Intellisense malfunction actually cause compile problems for UE5? Can I just ignore the errors? (obviously this is going to make troubleshooting more difficult but just wondering if the code will work with UE5 assuming that I haven’t actually made the errors in my code).

Thanks Dan!

#8

  1. Really hard to say because Windows support is where the main focus is, really. macOS and especially Linux take the backseat. M1 mac support is probably on the same level as Linux. On top of that VS Code support has been quite a mess starting around 4.25 which is only shortly after it was supported. It’s the main reason why that extension was made.

    You might have a better experience with Xcode as that might have better integration with Unreal but It’s not as popular as VS Code for C++ development (when IntelliSense works, that is).

  2. It shouldn’t effect compiling at all, no. You should also be able to disable the error squiggles without any complications.

#9

Ok, great. That’s extremely helpful Dan.

Thanks for your help!

#10

UE 5.0.2 seems to have fixed UE5 and VSC on MacOS with regard to c_cpp_properties.json

see attached, Line 26 had to be added. this fixes version errors but not include errors.

However, the include for the header file still is an issue. trying to chase down.

I noticed in the other error report there was a suggestion to change the “compilerPath” to “usr/bin/clang”, but as you can see, it is already but the include error for “CoreMinimal” persist.

Screen Shot 2022-05-28 at 6.38.52 PM
Screen Shot 2022-05-28 at 6.38.52 PM3058×1596 517 KB

#11

utterly frustrating. UE seems to be able to create the C++ project in VSC without issue (although it doesn’t build the version into the cpp_properties_json file)
But the moment I add an C++ Actor from UE5, “CoreMinimal” library isn’t found and while I could ignore Intellisense, then I have no clue where builds may be failing (I’m sure the old school coders are chuckling about when they were young).

There is a new version of Visual Code that is M1 compatible (version 17.0.0.8989). This asked Xcode to be updated to 13.4 which I installed (updated from 13.2.1).

I checked the Terminal to ensure that clang is installed and it is:

(base) **➜** **~** clang --version

Apple clang version 13.1.6 (clang-1316.0.21.2.5)

Target: arm64-apple-darwin21.5.0

Thread model: posix

InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

nonetheless, I can’t get it to work. Surely there is a MacOS developer around who can provide a step by step or simply confirm that this doesn’t work? I’m very confused after installing Visual Studio, Visual Studio Code, Xcode, various VSC extensions, having read multiple forums (and even documentation on MSFT’s site seems to not be current). So many places where things can go wrong, it’s just impossible to troubleshoot without some real prior knowledge.

Ive easily spent 40+ hours trying to read through disjointed documentation, random threads and what appears to be not authoritative direction. very frustrating.

#12

With what error? And this is from using the buikl task?

#13

I just simply mean from random typos or syntax. Perhaps there’s a methodology to finding errors efficiently without Intellisense but as it is, how do I trust the Problems list when the Problems being reported, such as “CoreMinimal” and the UProperties, are actually problems? Or maybe they’re not? I’m just completely confused.

I’m considering buying a windows laptop because I simply need to move ahead.

#14

Well Unreal is not a typical C++ project and IntelliSense isn’t the best. I always go by the errors that are issued from compiling.

This is hard when it’s to do with some Unreal macros and can errors can only be generated from Unreal’s tooling. For example the UPROPERTY macro is just consumed by the Unreal Header Tool. The macro itself expands to nothing e.g Demo. Fortunately Unreal has gotten better at diagnosing those issues.

#15

Thanks Dan for putting up with my frustration. I might suggest that GameDev warn potential students that MacOS and UE5 is currently not really happening unless we’re missing something. I’ve ultimately ordered a Windows laptop because I need to travel and I can’t wait on UE to get their act together. As someone who has been part of beta teams in music software, I’m really surprised that UE is shipping in its current condition, especially with that Epic Games money.

Anyway, thank you as always!

#16

Ha! well, perhaps I’m too much of a noob and I’m conflating errors that matter and errors that don’t? Maybe it’s worth GameDevTV doing a short course on figuring out how to diagnose problems with or without Intellisense. Maybe that is just a silly request, but some frame working might be useful simply because there are so many moving parts here (is it UE, is it VSC, is it Intellisense, is it UE 4 Snippets, and on the Mac specifically, is it Xcode, is it Homebrew, is it Clang, is there a risk of installing VSC extensions that conflict). There are so many variables here that the whole process is utterly confusing. And it’s very difficult for an end user, especially someone who is new, to understand how to hold variables (in scientific terminology) constant while changing others. I’m assuming this is challenging for anyone, but particularly for someone who really has little experience between software bugs and user error in coding and multiple platforms coexisting.

I literally spent days trying to problem solve and isolate where I was going wrong. I do need to be able to author for MacOS because my industry, music, is almost exclusively MacOS, but for now, in the interest of moving forward with C++, I’ve given up and just ordered a Windows laptop.

#17

I haven’t read the conversation but one user seems to have it fixed on an M1 mac.

#18

Thanks Dan,
Unfortunately it still doesn’t work here. I don’t have time to deal with what the UE development team should have fixed before they shipped. I need to continue on with the course. To say that I’m lost and frustrated with the MacOS side of things is an understatement. Windows side of things is a bit buggy with UE5 as I’ve noted in other posts but so far I’ve been fine working through those issues and finding solutions. The Mac is just an utter waste of time.

#19

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.

Privacy & Terms