it is the decision of the Publishers. I would self not use any SF. But the problem is funny. Why works the B3d exe file not with SF copy protection?
The Publisher used the SF Protection Studio, select the exe file and generate a CD-Key. These do everything correctly.
After starting the Protected EXE File crashed it with "“Unhandled Exception Interrupt”.
The Publisher used the SF Protection Studio, select the exe file and generate a CD-Key. These do everything correctly.
After starting the Protected EXE File crashed it with "“Unhandled Exception Interrupt”.
You're still providing almost no information and expecting an answer. I know you probably don't *have* any information, but without knowing what Starforce does, the best we can do is guess.
Evidently StarForce works by tapping into the EXE and intercepting certain calls to ensure various things ( that a debugger isn't being used, for example ) and evidently B3D exe's don't like it. Some of the stronger protection options in Armadillo cause B3D games to crash too.
My best guess ( because that's all I can possibly offer ) is that your publisher either needs to experiment with disabling advanced protection options or if that's not possible, it may be that Starforce just won't work with a B3D game.
For one thing, it might be that Blitz3D statically links FMod and it's own runtime libraries into a B3D exe whereas most game will dynamically link to those libraries. That alone could cause problems with advanced copy protection systems. B3D tries to call an FMod function in the statically linked code and Starforce is futzing around with it? Kaboom! Dunno. Like I said, just guessing.