Missing sound #35 used in ambient sound generator #4
Missing sound #18 used in ambient sound generator #5
Missing sound #35 used in ambient sound generator #6
Missing sound #17 used in ambient sound generator #40
Missing sound #35 used in ambient sound generator #41
Missing sound #8 used in ambient sound generator #56
Missing sound #4 used in ambient sound generator #177
Missing sound #4 used in ambient sound generator #178
I've tried isolating the issue but can't make heads or tails of it. I believe the issue is occurring whenever soundEngine->FindSoundByResID() and is not just limited to the calls that write the above error output.
No idea. I had no sound issues in Blood and AFAIK the two main files, blood.rff and sounds.rff are the same as in the Plasma Pak version.
I'm afraid you'll have to debug this yourself. Can you at least post the startup log?
Graf Zahl wrote:No idea. I had no sound issues in Blood and AFAIK the two main files, blood.rff and sounds.rff are the same as in the Plasma Pak version.
I'm afraid you'll have to debug this yourself. Can you at least post the startup log?
I think this was posted in the wrong forum tho.
At any rate, we could send you the required files if you think that will help sorting out what went wrong in FS. I myself have not tried the remaster's file yet because, to my knowledge, upstream's support for it wasn't finalized anyway.
Graf Zahl wrote:My guess is that sounds.rff wasn't loaded. That's why I asked for the startup log.
Sorry, Graf. I browsed to the file but forgot to click the add button thereafter.
Indeed sounds.rff wasn't loading and I've now isolated the issue being due to case-sensitivity. When I capitalised the filename as per the log, it started working fine. Interestingly enough, this case-sensitivity only affects sounds.rff and gui.rff. blood.rff always loads no matter the case.
You do not have the required permissions to view the files attached to this post.
Thoughts on closing this one off? It's correct in a POSIX sense that the file is case-sensitive as it's a case-sensitive environment, however it's incorrect in the sense that I don't think a user should have to think about it.
One idea to fix it is to query the entire folder into a string list and then doing a non-case compare with the list, and if a match is found use that entry. There may already be a facility to do this already within Raze's backend (i.e. the way it finds .GRP files). This might be the most robust way to fix it.
There's also the "easy" way, i.e. query Blood.rff, BLOOD.RFF, blood.rff.
The first option would be best I reckon. If you go for the second, you'll have some edge case where it's named bLoOd.RfF or something and it'll get missed.