Railworks America

https://github.com/ElPerenza/VSCode-serz
For anyone who uses VS Code, there's now an extension that allows you to convert Railworks .bin files to the XML format and vice versa for editing. If nothing else, it's an editor that allows you to always have the most up to date version automatically (and a dark mode too). Right now it's only compatible with .bin, but an update Soon™ should bring support for .geopcdx, .xsec, and .tgpcdx files. Being able to use VSC for pretty much all of my text-based workflow is definitely a big plus, rather than having to keep several windows of stuff open between blueprint, geometry, and code work.

Railfan722 wrote:https://github.com/ElPerenza/VSCode-serz
For anyone who uses VS Code, there's now an extension that allows you to convert Railworks .bin files to the XML format and vice versa for editing. If nothing else, it's an editor that allows you to always have the most up to date version automatically (and a dark mode too). Right now it's only compatible with .bin, but an update Soon™ should bring support for .geopcdx, .xsec, and .tgpcdx files. Being able to use VSC for pretty much all of my text-based workflow is definitely a big plus, rather than having to keep several windows of stuff open between blueprint, geometry, and code work.

I don't quite understand. TSTools does this for .bins and .Geos now.

buzz456 wrote:I don't quite understand. TSTools does this for .bins and .Geos now.

Hi, I'm the developer of that extension.
I made this extension as a sort of replacement for the .bin and (in the near future) .GeoPcDx editing capabilities of TS-Tools.
Why? Well, TS-Tools is now officially "End of Life" software. Mike Simpson, the original developer, announced that he has stopped working on TS-Tools for good. Secondly, TS-Tools has always been quite sluggish when opening and saving .bin files (on large Tracks.bin files, it can take minutes for TS-Tools to load or save).
This extension is orders of magnitude faster than TS-Tools when working with larger files, while also providing a better experience when working with .xml files thanks to Visual studio Code, which offers a better Search and Replace feature, syntax highlighting and a generally faster and more polished editor experience.

None of these ever took "moments" to open or save on my computer, but I applaud new software that will be supported in the future. Time will tell if this gives us another tool to replace one of the great editing tools ever produced for TSC. I salute Mike for his great work and encourage your efforts in this area.