Hi there. Recently I am having an issue running the blueprint editor. Every time I try to open BlueprintEditor2 it immediately throws the error message "Exception Processing Message 0xc0000005 - Unexpected parameters" and closes when the error message is closed. The only workaround I have used is by using the 64 bit version located under RailWorks\Tools\x64 but even that has issues due to requiring to have files copied over and even then it cannot properly export due to it believing that there is a "missing export tool" despite Serz and Serz64 being in the correct directories. Resulting in me having to manually run the xml files through Serz to make them into bin files. This is still a mystery to me since BlueprintEditor2 worked fine for me when I first began using it around last summer when I created my first asset, a custom sign for a scenario pack I made. This January I reinstalled TSC since I wanted a clean assets folder and it still worked while I was making child objects for a reskin pack. But then I attempted to use it recently in March and to this day, the issues began. My OS is currently Windows 10 version 22H2 build number 19045.7058
Update on the situation. I think the problem lies with the "blueprintschema.xml" file that the game generates. I made a fresh install using the download depot method and tried that version of blueprint editor. It launched without issue but it requested blueprintschema.xml which I copied over from my main install. Same error as previously described. I have a feeling this might be due to a TSC update DTG pushed out. I even tried deleting and re-running TSC to generate a new file but no luck.
Probably unrelated - the only "blueprintschema.xml" file I have is in Assets\MBIWSIGNALS\RailNetwork\IW Signalling\Signals\Temp The file is 573Kb and is from December 2016 Since found another "BlueprintSchema.xml" file in Steam\steamapps\common\Railworks\Temp The file is 602kb and from April 2016
I am pleased to say it now seems to work. The problem wasn't with TS. It turned out to be a Windows issue which has been fixed in the latest update.
