Raycaster Object Editor Crashes

Quote

C:\Users\Ben\ApData\Local\Temp\mrt136.tmp\animPicture.mfx

animPicture.mfx refers to the Animated Picture object, which might be the culprit of the crash. I also know this extension is incompatible (has issues) with HWA too, if that helps.

Sorry for the bump on this but sounds like people here have made a bit of progress with getting this to work? I'm having the same issues with the editor crashing upon opening on win 8.1. Does open for me under compatibility modes for win 95/98 but instantly closes as soon as I try to load textures. Is there any definitive fix for this that people have found yet? I basically picked up a copy of fusion just for this raycasting extension and it's a real shame I can't do much with it!

Also, I don't know if I'm missing something but is there any way to resize the editor viewport? It seems fixed at the default size and for any maps bigger than 8x8 there's a lot of scrolling involved! X)

Cheers all!

I'm running into the same issue. I was able to get it to run by switching to compatibility for Win98, but it closes when I try to open a file.

I ran Dependency Walker and it showed me three files missing:
* API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
* API-MS-WIN-CORE-PRIVATEPROFILE-L1-1-1.DLL
* API-MS-WIN-CORE-KERNEL32-PRIVATE-L1-1-1.DLL

Does this mean I need to track down these files to make it work?

Quote from JDWB

Does this mean I need to track down these files to make it work?

I came across Please login to see this link. that states the Dependency Walker shouldn't be entirely relied upon.

Quote

Dependency Walker's static analysis is not to be relied upon. The fact that Dependency Walker reports issues with those DLLs based on its static analysis does not mean that this is indeed your problem. It is normal for perfectly fine executables to report problems as you describe under static analysis, and yet execute perfectly well.

Right now I'm looking at Dependency Walker's assessment of my application and I see the exact same list of supposedly problematic files as you do. But the application runs perfectly well. Simply put, you are looking at a false positive.

It's definitely something that will continue to get worse as this extension is very old (from the MMF1-era). Newer versions of Windows will only break compatibility when new technologies replace it.

You could try installing DirectX 8 and DirectX 9 from re-distributable packages. Installing older versions of DirectX won't override newer versions, but instead includes the older files should they be called upon. That said, I don't know if DirectX is the cause of the problem here.

Ok I might have to give that a go with installing previous direct x versions then. If not I'm going to have to use the map editor solely on my win7 desktop and any other work on my win8 lappie. Bit worried that when win10 comes out it's going to make things even worse, and I was really hoping to update my win7 machine to win10.

Don't suppose there's any chance of the extension dev updating this, or is there a similar extension that could be used instead? I know this one's a bit old now and probably not likely still worked on.

Thanks for the replies!

cardo, any luck with the Direct X?

I haven't tried it yet JDWB. Think I'll likely wait to update this machine to win10 and see what the damage is like then!

Works 100% for me on my Windows 7 machine, will try an Windows 8 machine tonight.

Kisguri, how did you get on with it running on your win8 machine? Any joy? Looking forward to trying it out on win10 at the end of the month.

Maybe this issue is related somehow: Please login to see this link.