Black Screen at Beginning of Game

[Finchfish]

I tried to start a new game yesterday and after the intro ended (the part after it says "you take it" referring to the summer job) the game freezes on a black screen. The music still plays but I can't do anything and it says the application isn't responding.

I'm on a MacBook Pro 2015 and running on OS Sierra. I'm not sure if it's the update or what but I've never had problems with the game freezing before. I tried reinstalling the game and putting the command on Campo Santo website through the Terminal, still nothing. Anybody have any fixes?

[aniva26]

So, I got a reply from the game company:

"
We're so sorry you're experiencing this issue!
We've had a small handful of players write in about this and all of them reported attempting to play the game on the Intel Iris integrated GPU. Generally, it's not uncommon to have the game crash or freeze after running smoothly for a small while when running on integrated GPUs. While we're still investigating this specific issue and attempting to reproduce it on our end, we believe it's related to your unsupported graphics card.
If you have another machine that meets our minimum requirements, we recommend finishing the game there. Alternatively, if your Mac happens to have a dedicated GPU, you can force Firewatch to run off of that by following the steps in this article:
http://www.howtogeek.com/175281/how-to-force-graphics-options-in-pc-games-with-nvidia-amd-or-intel-graphics/
If neither of those are options for you, we understand if you would choose to pursue a refund. In which case, you would need to work directly with Steam to initiate that process: http://store.steampowered.com/steam_refunds/
"

It does seem to be a new issue with the update so I wouldn't think that it's an issue with the graphics card...?

[Nick Nolte Circa 1979]

Support got back to me, said exact same thing. Unsupported graphics card oesn't make sense to me, though, since the graphics are perfect up until the game freezes between sections...

[Finchfish]

aniva26 の投稿を引用：

So, I got a reply from the game company:

"
We're so sorry you're experiencing this issue!
We've had a small handful of players write in about this and all of them reported attempting to play the game on the Intel Iris integrated GPU. Generally, it's not uncommon to have the game crash or freeze after running smoothly for a small while when running on integrated GPUs. While we're still investigating this specific issue and attempting to reproduce it on our end, we believe it's related to your unsupported graphics card.
If you have another machine that meets our minimum requirements, we recommend finishing the game there. Alternatively, if your Mac happens to have a dedicated GPU, you can force Firewatch to run off of that by following the steps in this article:
http://www.howtogeek.com/175281/how-to-force-graphics-options-in-pc-games-with-nvidia-amd-or-intel-graphics/
If neither of those are options for you, we understand if you would choose to pursue a refund. In which case, you would need to work directly with Steam to initiate that process: http://store.steampowered.com/steam_refunds/
"

It does seem to be a new issue with the update so I wouldn't think that it's an issue with the graphics card...?

Hmm yeah that doesn't seem right, especially since I've played the game fine all the way through when it first came out on the same computer. Not sure it's a graphics card issue either. I'll try to keep looking around and see if I can find something that will work. If nothing comes up, hopefully it will be fixed in the next update? Idk. :\ Thanks again for helping out!

[tyler.durand]

add me to the list. black screens. very laggy. freezes alot. just purchased from my wishlist after waiting for a sale for such a long time. sad to have issues right away...

[Tarto Green]

I also experienced same problem. Please help :(

[aniva26]

I sent a reply back to explain that this was most likely an issue with the update and that many mac users all of a sudden had an issue at the same point in the game with this and got this reply:

"
Yes, we're actively investigating this issue, as it's very strange that this occurs consistently at the same point in the game, and only recently appeared after the latest patch. We want to quickly note that we can't guarantee that if we patch this issue, the game will run smoothly until completion. It's totally possible we fix this and then you run into another issue due to the integrated GPU that we cannot fix.

Regardless, we're going to do our best to address this! We just (as in late last night) got a Mac in the office with Intel Iris to test on. Our lead programmer is out for the week but we're hopeful we'll know a bit more about what's going on by mid next week.

Thanks so much for your patience!
"

So i don't know if I should keep it and hope that they fix it asap or return it within the two weeks but risk not having another discount on this for a while....

[neitiv]

I'm having the same issue with MacBook Pro 13-inch, Early 2015 with Intel Iris 6100 integrated graphics. It is very early stage on game when Henry sees a deer and there's a dialog about job offer that Henry takes. After that screen blacks out, music plays on the background and game stops responding.

This game has been on my wishlist quite a time and I'm so frustrated that now when it was on sale and I was finally able buy it, that I'm not able to play it. I'm thinking about refunding the game if there will be no fix for this. At least it should be mentioned on system requirements that the game is not supported on computers with Intel Iris graphics, so that other people with same type of graphics card won't do the same mistake and end up buying a game that is not supported on their computer.

Edit: It seems that someone was able to get the game work with boot camp and Windows 10 on the same Mac.

I removed the game from my Mac and downloaded it again, also tried to remove the file via Terminal but neither were helping. Although, now the game really crashes and I'm able to get the crash report. It says:

Process: Firewatch [17949]
Path: /Users/USER/Library/Application Support/Steam/*/Firewatch.app/Contents/MacOS/Firewatch
Identifier: unity.CampoSanto.Firewatch
Version: Unity Player version 5.4.1p4 (5.4.1p4)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Firewatch [17949]
User ID: 501

Date/Time: 2016-11-03 22:20:41.935 +0200
OS Version: Mac OS X 10.12 (16A323)
Report Version: 12
Anonymous UUID: F3851B9E-BD9F-5A77-CF04-198E1E0A64B8

Sleep/Wake UUID: B875E9C3-47D9-496F-A57B-C1597C9F3241

Time Awake Since Boot: 260000 seconds
Time Since Wake: 8100 seconds

System Integrity Protection: enabled

Crashed Thread: 8 UnityGfxDeviceWorker

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [0]

Thread 8 Crashed:: UnityGfxDeviceWorker
0 com.apple.CoreFoundation 0x00007fffa28fb339 getAtomTarget + 105
1 com.apple.CoreFoundation 0x00007fffa27eba81 ___forwarding___ + 689
2 com.apple.CoreFoundation 0x00007fffa27eb748 _CF_forwarding_prep_0 + 120
3 com.apple.driver.AppleIntelBDWGraphicsMTLDriver 0x000000010a5311d4 SamplerStage::bindSamplerToTexture(unsigned char, unsigned char) + 110
4 com.apple.driver.AppleIntelBDWGraphicsMTLDriver 0x000000010a530f22 SamplerStage::writeSamplerState() + 542
5 com.apple.driver.AppleIntelBDWGraphicsMTLDriver 0x000000010a525176 IGRenderStateSamplers::writeIf() + 86
6 com.apple.driver.AppleIntelBDWGraphicsMTLDriver 0x000000010a51e400 IGAccelRenderCommandEncoder::programPipeline(sPrimitiveData const&) + 3780
7 com.apple.driver.AppleIntelBDWGraphicsMTLDriver 0x000000010a51ff40 IGAccelRenderCommandEncoder::drawIndexedPrimitives(MTLPrimitiveType, unsigned int, MTLIndexType, MTLIGAccelBuffer*, unsigned int, unsigned int, unsigned int, unsigned int) + 586
8 com.apple.driver.AppleIntelBDWGraphicsMTLDriver 0x000000010a50ca7a -[MTLIGAccelRenderCommandEncoder drawIndexedPrimitives:indexCount:indexType:indexBuffer:indexBufferOffset:] + 192
9 unity.CampoSanto.Firewatch 0x0000000100c7b12c GfxDeviceMetal::DrawBuffers(GfxBuffer*, VertexStreamSource const*, int, DrawBuffersRange const*, int, VertexDeclaration*, ChannelAssigns const&) + 2172
10 unity.CampoSanto.Firewatch 0x00000001011ec112 GfxDeviceWorker::RunCommand(ThreadedStreamBuffer&) + 16210
11 unity.CampoSanto.Firewatch 0x0000000100c7dffc GfxDeviceWorkerAutoreleasePoolProxy + 60
12 unity.CampoSanto.Firewatch 0x00000001011ef9a4 GfxDeviceWorker::Run() + 52
13 unity.CampoSanto.Firewatch 0x00000001011e80bc GfxDeviceWorker::RunGfxDeviceWorker(void*) + 60
14 unity.CampoSanto.Firewatch 0x0000000100c3159c Thread::RunThreadWrapper(void*) + 60
15 libsystem_pthread.dylib 0x00007fffb7a45abb _pthread_body + 180
16 libsystem_pthread.dylib 0x00007fffb7a45a07 _pthread_start + 286
17 libsystem_pthread.dylib 0x00007fffb7a45231 thread_start + 13

Logical CPU: 2
Error Code: 0x00000000
Trap Number: 3

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 151418
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=331.4M resident=0K(0%) swapped_out_or_unallocated=331.4M(100%)
Writable regions: Total=784.1M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=784.1M(100%)

VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate framework 128K 2
Activity Tracing 256K 2
CG backing stores 880K 3
CG image 68K 6
CoreAnimation 68K 8
CoreUI image data 1364K 8
CoreUI image file 304K 5
Foundation 4K 2
IOKit 7940K 2
Kernel Alloc Once 8K 2
MALLOC 705.3M 167
MALLOC guard page 48K 10
MALLOC_LARGE (reserved) 256K 2 reserved VM address space (unallocated)
Memory Tag 242 12K 2
STACK GUARD 56.2M 44
Stack 29.6M 44
VM_ALLOCATE 28.6M 54
VM_ALLOCATE (reserved) 40K 3 reserved VM address space (unallocated)
__DATA 25.2M 261
__GLSLBUILTINS 2588K 2
__IMAGE 528K 2
__LINKEDIT 134.5M 23
__TEXT 197.0M 252
__UNICODE 556K 2
mapped file 60.5M 16
shared memory 16.4M 14
=========== ======= =======
TOTAL 1.2G 912
TOTAL, minus reserved VM space 1.2G 912

Model: MacBookPro12,1, BootROM MBP121.0167.B17, 2 processors, Intel Core i5, 2,7 GHz, 8 GB, SMC 2.28f7
Graphics: Intel Iris Graphics 6100, Intel Iris Graphics 6100, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54424C41522D4E5544
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54424C41522D4E5544
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x133), Broadcom BCM43xx 1.0 (7.21.171.10.1a16)
Bluetooth: Version 5.0.0f18, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0512F, 500,28 GB
USB Device: USB 3.0 Bus
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1

[jenstein04]

Exact same issue as above, right after the deer and the job offer, MacBook Pro 13-inch, Early 2015 with Intel Iris 6100 integrated graphics.

[DeWitt]

Just bought the game and have met exactly the same problem. I took the job and they took my game Kappa. Intel HD Graphics 6000.

I'm not sure if I should ask for refund... I mean, I did read that Intel Based Card is not supported but people here are saying the game was fine even on the Intel Based one before the last update, right?

[Nick Nolte Circa 1979]

Just received a message from tech support saying they figured out what was causing the problem and are working on a patch, which should be up within in a week. Don't go running to refund just yet!

[hermit]

Hopping onto this because I face the same issue as well!

[夏花绚烂开。]

so it can't fix ? can i get my money back because this problem？
我也卡那里了，尼玛退钱！！！

[goobie]

We believe this issue has been resolved as of the latest patch on Nov 7th.

One of our ongoing goals with Firewatch support has been to continue to improve stablity and performance. To that end we upgraded to a version of Unity which gave us access to multithreaded OpenGL for Mac OS. I'll spare you technical details, but this is a big performance improvement!

Unfortunately something in our renderer was causing the crash like behavior described above on Mac integrated GPUs (so all 13 inch MBPs). We have passed call stacks on to Untiy, but this issue has been resolved by re-building Firewatch using a different version of the engine.

If you still experience this issue, please try verifying the integrity of your game cache.

If the issue persists after that, please contact us via email at [e-mail], that is the fastest way for us to get eyes on an issue, and this is one we would like to regress if needed!

[faytaren]

It's working!

Thank you for fixing this - you guys are awesome.

[hermit]

thanks for getting it sorted out so quick!