Process of elimination buddy.
Test, add a couple of plugins at a time, re-test until you experience the crash, then you can eliminate 1 by 1 until the crash is confirmed to be with the last plugin you removed.
Re-add that plugin and confirm if the crash is back so to confirm it’s not a fluke incidence.
If I’m remembering correctly here, his original issue was crashing to desktop on single player.
And he later said it happens on HD edition which is already 1.1
But, curiously not happening on Discovery.
" I dug out some files of my own I had backed up last used on windows 10 , it wasn’t an issue I was experiencing then, but it is a newer pc build"
So 2 potential problems here:
"I can remember when you made matchplayer I said it doesn’t work, and you said are you using 1.0, which I was, so you changed it to work with 1.0, being the saint that you are! "
He’s using a plugin that works for 1.0, unless I’m missunderstanding things. But, would that even matter on singleplayer? Was Vanilla having CTDs every half hour or so on docking a thing when Vanilla was played beforr 1.1 came out?
In any case, it seems like the options are either:
So my thoughts still lean to going back to a clean setup with no plugins or alterations to see if the issue can be reproduced.
There’s no requirement for 1.1 on the client, it’s more a server side thing. He was pointing out the difference in the errors you are seeing.
HD edition should be the 1.1 common.dll afaik.
If you are installing the 1.0 version of the game from ISO, and then use the HD edition installer, you will end up with an up to date and patched version. During the installer/setup make sure to choose the different save folder option.
If in THIS state it still has the same issues with crashes then there is definitely something wrong that’s more systemic/unique to your machine/software setup.
That could be it - Discovery saves elsewhere doesn’t it? Plus it might explain the ntdll.dll generic error. Since it’s not a Freelancer module that’s faulting.
No, the original disc/ISO is known working, as is the Vanilla install, on Windows 11.
Please don’t take this as me dismissing what you are saying - this isn’t a common issue with FL, and the faulting DLL and offset isn’t directly Freelancer related its a more generic error, either in software, drivers, or hardware.
So, if you are saying it’s only happening with Freelancer then it’s isolated to how the game uses the system.
My only suggestions then are plugins, can you try disabling all plugins and play a while without them? Just to isolate this. It could be that since some of these plugins are quite old that they are making calls to Windows API that are no longer valid.
Also, since FL uses older DirectX components, you might want to run the DirectX web runtime if you haven’t installed FL from virtual CD/ISO.
This will probably be better dealt with on the Starport discord in #help-and-support, but here goes. This seems unique to your system.
ntddll.dll is probably not the cause, it’s something else deeper in the system. Exception 0xc0000005 is something called STATUS_ACCESS_VIOLATION. It usually means there’s something trying to be read (from memory or storage) and it expects a value but isn’t getting one.
Do you have this same issue with any other games/software? This type of issue has been seen across a multitude of other software in the past. I’d lean more towards driver software, and potential hardware issues.
Maybe do a Memtest/Windows Memory diagnostic tool. And then do a benchmark/health test with CrystalDiskMark. Check your temps with HWInfo etc.
No problem
If that doesn’t work, try the basic only version of this:
https://www.codecguide.com/download_k-lite_codec_pack_standard.htm
It has an option during install to fix broken codecs also.
Any situation in which audo plays but video doesn’t is a missing decoder for the type of video.
But, with default Windows Home/Pro etc these videos will play if the game is installed from CD. So infact this IS something with your Windows install otherwise nobody would have been able to play the videos without extra steps back in the day.
Freelancer uses WMV2 which is a Windows Media Video decoder, which is what is making me think you are on an N edition of Windows.
Try installing this.
https://www.softpedia.com/get/System/OS-Enhancements/Media-Feature-Pack-for-Windows-7-N-and-Windows-7-KN.shtml
You can look at your system information either through system in control panel, or by doing Win key + R and type msinfo32 and press OK.
@Drayman said in Black Cinematics:
Its Windows 7 64bit
There are different versions of Windows 7 64-bit, for example, home, pro, N etc. Windows N doesn’t have the Windows Media Player installed along with the needed codecs.
Based on what you’ve said the intro video files do not play video but play sound, this is tell tale signs your Windows do not have the correct video decoders to playback the video.
Do you happen to be on Windows that is an N version?
That doesn’t sound right, the cinematics ingame (except for the ones before the main menu) aren’t WMV, they are in-game animation scripts.
From where did you source the game?
Leaving a post here to remind myself of this topic as it relates to my installer/launcher/patcher project.
Placing a post here just so I can find it again later. This thread contains useful info to help me develop a new installer/launcher/patcher.
By them at least, yes.
PS: Bas, you elite by your post count (1337) I just noticed
I think he’s talking about the interest at GOG (petition) it has a good large number of people wanting it.
Adoxa,
Any issues with me including that in an all in-one patch?
I’ve pretty much solved this anyways:
I am going to simply offer the following as components to be ticked/unticked.
1. JFLP patch (or whatever final patch we can come up with)
2. Widescreen
3. JFLP DLL, with a warning that it may be seen as cheating on some servers.
Any dacom.ini particular edits will be done post-install by after script.
I think that will cover most bases tbh.
Anything else you think I should add guys?