Hi
I'm still thinking about few smaller improvements on Tauruses, however it's hard since RSC/DTGs new 3D model export plugin, as it's nearly impossible to achieve the same amount of specularity, and reflection effects with the new plugin, as it was in the old plugin and old exports. I hope i can sort it out eventually.
But i'm thinking more about a new locomotive model, but i don't know which, and if it's wanted... any tips? :) Edit: (it should be a non-steamer, with available raw materials (sounds, photos, blueprints maybe)
August 20, 2016
March 8, 2014
Repaint packages
- A1, AUDI, Greenmobility, Hitradio, Telekom
- Cargo Serv, WLC Roland, SLB, RTS, LTE (have own package in game)
- CFI, FUC, FuoriMuro, InRail repaints for 1216
- Dispolok VK, ITL Knorr Bremse, MRCE, PKP IC (have own package in game)
- GySEV 1116 061 weathered
- OBB 175 Jahre, and Leonardo da Vinci (have own package in game)
- PKP Heineken (have own package in game)
- SZ 541 001 Manner, SLB, WLC 1216 954
October 24, 2013
RSC's new Taurus
Hi
Some of you probably noticed that RSC/Dovetail is showing screenshots about a Taurus locomotive, that looks very similar to the HRQ Taurus. That's not stolen or such, they've bought the source of it.
The ES64U2/1116 with the DB repaint have been sold to RSC/Dovetail, through the parnership programme.
This was a one time thing, they have bought the copy of DB Taurus in it's state of late august, then they can do with it whatever they want, that will be their own totally independent version.
However the HRQ tauruses will remain the same, will be updated, will be sold as usual. Simply the players will have the choice to buy a taurus from HRQ or RSC. I expect the handling of RSC Tauruses will be simpler(similar to br101, or ICE), while the HRQ Taurus will remain to aim on realism.
In short: nothing will change with HRQ Tauruses. The 1216/ES64U4 is not sold to RSC so it won't be available from RSC/Dovetail.
It's something like GR's br 143 and 151. It was released once by RSC, but GR/VR continued to sell and develop their own variants.
Some of you probably noticed that RSC/Dovetail is showing screenshots about a Taurus locomotive, that looks very similar to the HRQ Taurus. That's not stolen or such, they've bought the source of it.
The ES64U2/1116 with the DB repaint have been sold to RSC/Dovetail, through the parnership programme.
This was a one time thing, they have bought the copy of DB Taurus in it's state of late august, then they can do with it whatever they want, that will be their own totally independent version.
However the HRQ tauruses will remain the same, will be updated, will be sold as usual. Simply the players will have the choice to buy a taurus from HRQ or RSC. I expect the handling of RSC Tauruses will be simpler(similar to br101, or ICE), while the HRQ Taurus will remain to aim on realism.
In short: nothing will change with HRQ Tauruses. The 1216/ES64U4 is not sold to RSC so it won't be available from RSC/Dovetail.
It's something like GR's br 143 and 151. It was released once by RSC, but GR/VR continued to sell and develop their own variants.
June 2, 2013
Reskin blueprint what makes repainting much easier.
Update: It seems this feature is bugged too, so the game ignores the texture entries except the first. Which means, only one texture can be replaced with this. However this one, is just enough for Taurus repaints :)
With the latest update, RWTools is capable of swapping reskin blueprint rolling stock too!
I strongly suggest for all repainters to use this method instead of the old repainting methods and convert the old repaints to use reskin blueprints, because this is better, smaller and more robust.
(Use Kinderdorf's bin/xml as the base repaint for your reskin blueprints without dynamic numbering, or WLB for the 3P repaints, and Adria for 1216s)
I've just seen a topic on UKtrainsim forum, where this "Reskin blueprint" was discussed, and it's actually works! Using this, can make repainting MUCH easier.
The reskin blueprint is simple, you can add names to your resking, set the category in editor, then a reference to the original, normal blueprint, and at the end of it, "texture entries" which a list where you set which texture should be replaced with another one.
The benefits of using this:
First, as always, you need to have a developer/provides structure.
In "source" you should create a developer/provider structure by creating a new folder with name for example "myaddon" then the provider folder in it "taurusrepaints" then a "RailVehicles" folder(this name is probably need to be exactly this), in RailVehicles folder, the further structure is depends on you. But let's make one with name "examplerepaint1".
Select this folder and right click on it, then select "new blueprint", then find "Reskin blueprint".
Now you should have the "reskin blueprint" in editor.
Fill the names, set the Category, now it's "Locomotoves" (but you can see, that you can repaint every kind of objects with this). Set Valid in Scenarios to true (this means it will appear in scenario editor's asset list).
Then set the Blueprint set ID, this is the reference to the original blueprint. This is set to HRQ/Taurus Adria transport blueprint, because that blueprint don't have dynamic numbering, what is not needed now.
Then insert texture entries(you can have multiple entries if it's needed), to set what texture should be replaced with what.
"Texture name" is the name of the original texture, without path.
"Texture ID" is the replacement texture, with relative path from the addon folder (you can get this by clicking on the ace texture file in source file tree, and select "Copy filename" and then paste to Texture ID, and export. And you're done, blueprint editor does the rest for you!
If you don't use ace file (referenced ace files will be converted to TgPcDx at export), but other way to make a TgPcDx, just leave the Texture ID blank, export it, and edit the exported xml/bin. Note that, in the exported xml/bin the referenced file in Texture ID should not have extension, but a [00] before the file name, See in the exported reskin xml example.
Exported example blueprint xml (use the browsers right click menu on this link to download, otherwise it will open the xml)
If you want to make repaints for ES64U2/4 tauruses, try to reference on base package blueprints, and not on optionals. (OBB(no italia), DB, Kinderdorf, WLB, Adria). This makes sure everyone has it installed.
I strongly suggest for all repainters to use this method instead of the old repainting methods and convert the old repaints to use reskin blueprints, because this is better, smaller and more robust. However as a normal blueprint and a reskin blueprint stored differently, those scenarios that have been made by using locomotives with old repaint method, and these repaints are converted to use "reskin blueprint" will cause these scenarios to crash, because locotives that using full blueprint and reskin blueprint are stored differently in scenario.bin files. I hope RWtools for example will have a fixing method for this.
Until that here is a little tool that fixes these in scenarios (updated at 2013-05-18, better compatibility with 32bit systems, and added ability to set serz.exe path manually if it can't be read from registry) and here is the same application in EXE. You need to select scenario.bin files which you want to fix, or select directiories which are contain scenario bins in this case it will search for scenario.bins in unlimited directory depth. The tool will search through the bins and the references to rolling stocks, and fix those that are wrong. If there is no problem, the tool won't change it.
With the latest update, RWTools is capable of swapping reskin blueprint rolling stock too!
I strongly suggest for all repainters to use this method instead of the old repainting methods and convert the old repaints to use reskin blueprints, because this is better, smaller and more robust.
(Use Kinderdorf's bin/xml as the base repaint for your reskin blueprints without dynamic numbering, or WLB for the 3P repaints, and Adria for 1216s)
I've just seen a topic on UKtrainsim forum, where this "Reskin blueprint" was discussed, and it's actually works! Using this, can make repainting MUCH easier.
The reskin blueprint is simple, you can add names to your resking, set the category in editor, then a reference to the original, normal blueprint, and at the end of it, "texture entries" which a list where you set which texture should be replaced with another one.
The benefits of using this:
- cleaner asset structure
- efficient memory usage, and rendering (3d models not needed to be loaded for each repaints, but only once, and it can be instanced)
- no need to supply geopcdx files, just the reskin blueprint and the texture
- as the reference on the normal blueprint is include provider and addon name(so the cross package reference is possible), reskins can be put in seperate packages/folders, not just in the main addon folder.
- smaller repaints
- Independent from the original blueprint's changes (as this is referencing the original blueprint), these will remain useable if the original blueprint is changed.
First, as always, you need to have a developer/provides structure.
In "source" you should create a developer/provider structure by creating a new folder with name for example "myaddon" then the provider folder in it "taurusrepaints" then a "RailVehicles" folder(this name is probably need to be exactly this), in RailVehicles folder, the further structure is depends on you. But let's make one with name "examplerepaint1".
Select this folder and right click on it, then select "new blueprint", then find "Reskin blueprint".
Now you should have the "reskin blueprint" in editor.
Then set the Blueprint set ID, this is the reference to the original blueprint. This is set to HRQ/Taurus Adria transport blueprint, because that blueprint don't have dynamic numbering, what is not needed now.
Then insert texture entries(you can have multiple entries if it's needed), to set what texture should be replaced with what.
"Texture name" is the name of the original texture, without path.
"Texture ID" is the replacement texture, with relative path from the addon folder (you can get this by clicking on the ace texture file in source file tree, and select "Copy filename" and then paste to Texture ID, and export. And you're done, blueprint editor does the rest for you!
If you don't use ace file (referenced ace files will be converted to TgPcDx at export), but other way to make a TgPcDx, just leave the Texture ID blank, export it, and edit the exported xml/bin. Note that, in the exported xml/bin the referenced file in Texture ID should not have extension, but a [00] before the file name, See in the exported reskin xml example.
Exported example blueprint xml (use the browsers right click menu on this link to download, otherwise it will open the xml)
If you want to make repaints for ES64U2/4 tauruses, try to reference on base package blueprints, and not on optionals. (OBB(no italia), DB, Kinderdorf, WLB, Adria). This makes sure everyone has it installed.
I strongly suggest for all repainters to use this method instead of the old repainting methods and convert the old repaints to use reskin blueprints, because this is better, smaller and more robust. However as a normal blueprint and a reskin blueprint stored differently, those scenarios that have been made by using locomotives with old repaint method, and these repaints are converted to use "reskin blueprint" will cause these scenarios to crash, because locotives that using full blueprint and reskin blueprint are stored differently in scenario.bin files. I hope RWtools for example will have a fixing method for this.
Until that here is a little tool that fixes these in scenarios (updated at 2013-05-18, better compatibility with 32bit systems, and added ability to set serz.exe path manually if it can't be read from registry) and here is the same application in EXE. You need to select scenario.bin files which you want to fix, or select directiories which are contain scenario bins in this case it will search for scenario.bins in unlimited directory depth. The tool will search through the bins and the references to rolling stocks, and fix those that are wrong. If there is no problem, the tool won't change it.
August 18, 2012
PZB fix
As you know the PZB system of default routes are incomplete. The 500hz magnets are missing, and it's script is not works. Also every main signals have a 2000hz magnet, that can only send 2000hz pzb messages, which is OK for HP (main only) signals, but HPVR combined (main+ distant) signals should be able to send 1000hz too. Other magnets are correctly placed and working.
Here is a signal fix pack, that overwrites the default 500hz magnet script (should not cause problem, as 500hz magnets are not placed at all on default routes, so these are not used by default), and a new PZB magnet type, with name "De PZB 2000hz/1000hz Combo".
To make fully work PZB on default routes, you need the following changes:
- place 500hz magnets along the route (should be placed 250m before the main signals)
- at HP only (main only) signals, the default 2000hz pzb magnets are good no need to changed, but at combined, HPVR signals you need to replace these with the De PZB 2000hz/1000hz Combo
-place the magnet links correctly with care on direction of the links, and the placement
You could do this with vR pzb magnets, but here is a free solution what is reachable for everyone, which is also compatible with both vR and default rolling stock, and of course with Taurus.
Important: as the 500hz script will be overwritten, STEAM probably will revert it to default at every updates and verify game caches. So if one of these happened, make sure that you have reinstalled this RWP.
Here is the pzb fix
Here is a signal fix pack, that overwrites the default 500hz magnet script (should not cause problem, as 500hz magnets are not placed at all on default routes, so these are not used by default), and a new PZB magnet type, with name "De PZB 2000hz/1000hz Combo".
To make fully work PZB on default routes, you need the following changes:
- place 500hz magnets along the route (should be placed 250m before the main signals)
- at HP only (main only) signals, the default 2000hz pzb magnets are good no need to changed, but at combined, HPVR signals you need to replace these with the De PZB 2000hz/1000hz Combo
-place the magnet links correctly with care on direction of the links, and the placement
You could do this with vR pzb magnets, but here is a free solution what is reachable for everyone, which is also compatible with both vR and default rolling stock, and of course with Taurus.
Important: as the 500hz script will be overwritten, STEAM probably will revert it to default at every updates and verify game caches. So if one of these happened, make sure that you have reinstalled this RWP.
Here is the pzb fix
Subscribe to:
Posts (Atom)