Is there an alternative to the built-in blueprint editor?

[Rockdoc2174]

When I try to launch the built-in blueprint editor it fails because it cannot find the file mfc100u.dll. The .dll is present on my machine in amongst the files associated with my AMD graphics card software. I contacted RSC and they suggested making the editor the default launcher for this file which I did without result. They're now think that it was an error during installation and are suggesting that I delete the local content and re-download it from Steam, which I'm loath to do because my broadband isn't all that fast.

Is there are alternative program that can read and edit blueprint files (and save me a lot of time downloading my content again!)? I see a lot of praise for RW_Tools but have no real idea of its capabilities and whether this would do the job for me. All suggestions gratefully accepted.

Thanks,
Keith

[Gishank]

RW Tools has that caperbility I think... Though if you took that .dll file and copied it in to the folder where the Railworks exe files are it should fix the issue.

[Rockdoc2174]

Thanks for the confirmation on RW_Tools. I tried copying the .dll into the railworks folder but it made no difference.

Keith

[gptech]

You may need to register the .dll

Open a command prompt, and type in

Code: Select all

regsvr32 {path to file]mfc100u.dll

and press enter.

[path to file] means the drive and directory(s) to get to the .dll eg: c:\AMD\Shared\stuff

[Rockdoc2174]

Thanks. I'll give that a whirl tomorrow and report back.

EDIT Some long paths end up with contracted names ending ~1 and I've never got the hang of predicting them. Trying to keep things simple to avoid breaking anything, would I be better to make a new folder in the root directory and point to it there?

Keith

[gptech]

Thanks. I'll give that a whirl tomorrow and report back.

EDIT Some long paths end up with contracted names ending ~1 and I've never got the hang of predicting them. Trying to keep things simple to avoid breaking anything, would I be better to make a new folder in the root directory and point to it there?

Keith

I wouldn't, moving the file may lead to more bother.
You'd be better off navigating through the folder structure in the command prompt window to get to the folder where the .dll lives.
Fire up Command Prompt, you'll probably see something like C\Users\Keith>, so type in

Code: Select all

cd..

and press enter. This takes you back a folder level. Do this as many times as needed until you get C:\> before the cursor.
Now you can use the cd command again to move about, for example, typing in

Code: Select all

cd program files

will take you to the Program Files folder.
When you eventually get to the right folder just use

Code: Select all

regsvr32 mfc100u.dll

to run the register routine.

Hope thats not muddied the waters too much!!

[Rockdoc2174]

No, that's clarified things nicely.

Thanks a lot,
Keith

[gptech]

Must point out, you'll need Administrative privilages to run regsvr32, so make sure you're logged on with a suitable account.

[Rockdoc2174]

I did as you suggested and moved the CMD to the AMD folder conatining the .dll but I'm getting an error message when I run regsvr32:

The module "mfu100u.dll" was loaded but the entry-point DllRegisterServer was not found. Make sure that "mfc100u.dll" is a valid DLL or OCX file and then try again.

I haven't clue what this means!

Keith

[gptech]

According to Microsoft, that error means:

"Regsvr32.exe was unable to find the required entrypoint in the module specified in the command line. This can occur if the entrypoints are not properly exported from the module or if the module is not a .DLL or .OCX file."

which is probably of no use at all

Rather than navigate to the AMD folder, try using the full path in the command prompt. If that doesn't work I'm afraid I'm stuck.

Of course this could all be a wild goose chase and the file doesn't need registering at all!

Another edit.... are you spelling the file name right?... mfu or mfc?

[Rockdoc2174]

I'll have another go, then. I guess the next thing is to find the regsver32 folder and work from that.

I did spell it properly - at least once! When I got it wrong the resulting error message said that the file could not be found.

Keith

[Rockdoc2174]

I moved to the windows\system32 folder and ran regsvr32 from there with the full file path to the .dll. I got the same error message as when I tried to run the server from inside the same folder as the .dll.

I wonder what the .dll does?

Thanks for the help,
Keith

[Rockdoc2174]

YIPPEE! FIXED!!

It was a mis-installation of the VisualC++ distributable files. If anyone else has a similar problem you can download the pack (vcredist_x86.exe) from Microsoft at http://www.microsoft.com/download/en/de ... px?id=5555.

Keith