Others Forest of the Blue Skin [Oct 2025] [Zell23]
- Thread starter Muff Diver
- Start date
bwardyunbip
Active Member
- Dec 15, 2019
- 633
- 270
- 196
Baltidouble
Member
- Apr 21, 2020
- 146
- 90
- 172
BuPa
Newbie
- Aug 21, 2017
- 37
- 55
- 148
I had the d3dx9_39.dll and (0xc000007b) issues, and it's taken me a good three hours of steadily growing insanity and bullheadedness, but I think I've managed to finally grasp and (so far, at least) solve them!
The answers in this thread and on google were almost no help. Downloading the dll in question and putting it in either the game folder or my SysWOW64 folder got rid of the d3dx9_39.dll error, but it was then replaced by the (0xc000007b) error. Installing the latest .NET frameworks did nothing, changing DPI settings in the compatibility section of the exe's Properties did nothing, installing and attempting to use Locale Emulator did nothing, and a number of other suggestions (mostly from googling, but a few here as well) of what to try seemed too off the mark for me to attempt them given how high-effort or even potentially damaging they sounded.
So, the problem – as I understand it from further research, anyway – is that FOBS is looking, very specifically, for a d3dx9_39 dll, which belongs to a specific version of DX9. I have DX12, but going into my SysWOW64 folder, it's apparent that my installation also came with DX9, 10, and 11. But my relevant dll there for the DX9 installation is 'D3DX9_43.dll', from some later version of DX9 than what FOBS was expecting to find. I assume that just pasting in the _39 dll I downloaded fixed FOBS's "find the expected file" problem, but that the _39 dll was somehow incompatible with my actual, more up-to-date _43 installation.
Thus, my solution: go to your SysWOW64 folder, find your particular d3dx9_## dll, place a copy of it into your FOBS game folder, and then rename that copy to the expected 'd3dx9_39.dll'.
Doing this has at least gotten me to the title screen, so it's more progress than anything else has managed to give me. Hope this helps anyone still struggling with either of those issues.
The answers in this thread and on google were almost no help. Downloading the dll in question and putting it in either the game folder or my SysWOW64 folder got rid of the d3dx9_39.dll error, but it was then replaced by the (0xc000007b) error. Installing the latest .NET frameworks did nothing, changing DPI settings in the compatibility section of the exe's Properties did nothing, installing and attempting to use Locale Emulator did nothing, and a number of other suggestions (mostly from googling, but a few here as well) of what to try seemed too off the mark for me to attempt them given how high-effort or even potentially damaging they sounded.
So, the problem – as I understand it from further research, anyway – is that FOBS is looking, very specifically, for a d3dx9_39 dll, which belongs to a specific version of DX9. I have DX12, but going into my SysWOW64 folder, it's apparent that my installation also came with DX9, 10, and 11. But my relevant dll there for the DX9 installation is 'D3DX9_43.dll', from some later version of DX9 than what FOBS was expecting to find. I assume that just pasting in the _39 dll I downloaded fixed FOBS's "find the expected file" problem, but that the _39 dll was somehow incompatible with my actual, more up-to-date _43 installation.
Thus, my solution: go to your SysWOW64 folder, find your particular d3dx9_## dll, place a copy of it into your FOBS game folder, and then rename that copy to the expected 'd3dx9_39.dll'.
Doing this has at least gotten me to the title screen, so it's more progress than anything else has managed to give me. Hope this helps anyone still struggling with either of those issues.
Last edited:
bwardyunbip
Active Member
- Dec 15, 2019
- 633
- 270
- 196
BuPa
Newbie
- Aug 21, 2017
- 37
- 55
- 148
Ah, I had only been talking about my issues with FOBS specifically, sorry. I just downloaded and opened SnY to see if I had any similar problems there, but no, those two demos seem to work fine for me out of the box. What are the issues people are having with opening those?
Ov3rlord24
Newbie
- Aug 5, 2018
- 94
- 39
- 161
Ov3rlord24
Newbie
- Aug 5, 2018
- 94
- 39
- 161
xZecretX
Well-Known Member
- Jun 6, 2017
- 1,270
- 1,053
- 407
You linked to a post that contains said save.
In case that the attachment does not open a open/save file prompt (for me on Firefox, for example, it opens in another tab with unreadable symbols), you need to right-click on the attachment to open the context menu and select "Save Link As...".
Make sure to change the file type (for example for me by default "Text Document (*.save)" is selected, you need "All Files (*.*)" here) and change the file name if necessary (attachments always add some numbers to the beginning which usually need to be removed to work and in this case the correct file extension is ".actsave" and not ".save").
StapleComm
Well-Known Member
- Apr 24, 2020
- 1,078
- 1,057
- 338
bwardyunbip
Active Member
- Dec 15, 2019
- 633
- 270
- 196
Succubus Hunter
Devoted Member
- May 19, 2020
- 9,355
- 18,329
- 863
StapleComm
Well-Known Member
- Apr 24, 2020
- 1,078
- 1,057
- 338
...very helpful, thanks guys. Seriously tho, I walk into different locations, and have no clue what am I supposed to do in them. Maybe I'm blind, but it looks like they only have monsters in them and that's it
Lazyrick
Active Member
- Jan 10, 2018
- 688
- 790
- 297
To be fair, that's really all you can do in it right now. Zell made a
You must be registered to see the links
in October saying that they wouldn't be releasing anymore demos of SnY until it was done. whatever copy you have is just an early demo that showcases a couple of monsters.
StapleComm
Well-Known Member
- Apr 24, 2020
- 1,078
- 1,057
- 338
Succubus Hunter
Devoted Member
- May 19, 2020
- 9,355
- 18,329
- 863