JointedRail stuff [screenshots/renders]

@22alpha

What will happen to the current content at jointedrail.com that is compatible with trs2010,etc..?Will it be "archived" or deleted?

Content compatiable with the supported versions of Trainz at this time (TS2012 and up) will be kept unless beyond repair for TANE. We are currently working to make everything TANE compliant on our side, which will still work for 2012. 2010 is not supported so if any fixes for 2012 or TANE broke something for 2010 or prior, its unfortunate but we need to keep moving forward. We cannot maintain content for 6 different versions of Trainz as the sim progresses forward.

-Kevin
 
He was joking.

Kev, I think what sonofham meant was; update the content if you guys have to, but leave the old version in an unsupported "legacy" section on the site. There is no need to maintain it.
 
cad25a828d6900628798646ab903efde.jpg


Textures done for the flat, as well as a preview of one of the loads I'm doing. I'm planning on this front-end loader (currently without a front end), some tarped machinery, some kind of steel plate load, and why not throw on dylanviey's box beam for good measure.
 
He was joking.

Kev, I think what sonofham meant was; update the content if you guys have to, but leave the old version in an unsupported "legacy" section on the site. There is no need to maintain it.

So far if things are still working in TANE and are not up for a planned update they don't get any kind of change and will not be removed. However, if some item does require TANE updates it will be updated to trainz build 3.3 (the latest version JR supports). There will be no legacy copies of the files retained for older versions. The reason for this is more the fact that we do not keep local testing copies of old trainz versions around for testing and cannot make changes to the items and leave them untested in old versions. If the changes made for TANE would somehow remove functionality or break an item for an old version we don't want to have to support that too so moving the trainz build to the highest JR supported version is the best option.

Now, here are a couple of items that were getting a planned update and are now available at the site in their updated form.

1e09236f243c3de52b9e28e2910d7705.jpg

These have new mesh parts, updated textures, full TANE compatibility, and brand new blomberg truck models (which will also get an across the board update in the coming few days for all the other applicable JR items). As a side note, the model supports drop in addition of the HP trainz F40PH cab (if you happen to like such things - I certainly do). The update is free to all who have the model previously - just re-download from your account page. If you have a purchase from the old site and don't have access in your downloads section send us an order number and we can add it. Of course, if you purchase the F40PH's from now forward you will receive the updated files.
 
Last edited:
So far if things are still working in TANE and are not up for a planned update they don't get any kind of change and will not be removed. However, if some item does require TANE updates it will be updated to trainz build 3.3 (the latest version JR supports). There will be no legacy copies of the files retained for older versions. The reason for this is more the fact that we do not keep local testing copies of old trainz versions around for testing and cannot make changes to the items and leave them untested in old versions. If the changes made for TANE would somehow remove functionality or break an item for an old version we don't want to have to support that too so moving the trainz build to the highest JR supported version is the best option.

Now, here are a couple of items that were getting a planned update and are now available at the site in their updated form.


These have new mesh parts, updated textures, full TANE compatibility, and brand new blomberg truck models (which will also get an across the board update in the coming few days for all the other applicable JR items). As a side note, the model supports drop in addition of the HP trainz F40PH cab (if you happen to like such things - I certainly do).

Does that mean I can look up my order, and if there are downloads remaining, I can acquire the newer ones you shown here, by downloading again?
 
For those of us who are not versed in content creation jargon, can you explain what "drop in" means? is it just changing the config?

I agree, HP's F40PH cab is great.
 
Last edited:
For those of us who are not versed in ontent creation jargon, can you explain what "drop in" means? is it just changing the config?

yes boc that is correct. it will come with the dd40 cab attached (yuck) but if you have the HPtrainz F40 cab you can replace the interior kuid in the config and that cab will position in the correct place.
 
He was joking.

Kev, I think what sonofham meant was; update the content if you guys have to, but leave the old version in an unsupported "legacy" section on the site. There is no need to maintain it.

Exactly what I meant.

So far if things are still working in TANE and are not up for a planned update they don't get any kind of change and will not be removed. However, if some item does require TANE updates it will be updated to trainz build 3.3 (the latest version JR supports). There will be no legacy copies of the files retained for older versions. The reason for this is more the fact that we do not keep local testing copies of old trainz versions around for testing and cannot make changes to the items and leave them untested in old versions.

You don't need to have keep local testing copies of old Trainz versions as if the content runs in TRS2010 for example with no errors then just put it into a legacy section for TRS 2009\2010\2012 at the site with a disclaimer and continue to make content for newer versions of Trainz...
 
You don't need to have keep local testing copies of old Trainz versions as if the content runs in TRS2010 for example with no errors then just put it into a legacy section for TRS 2009\2010\2012 at the site with a disclaimer and continue to make content for newer versions of Trainz...

But that would mean I need a local testing copy of TS2010 to be sure the item works after the changes are made because if it does not work, guess where those people come for support?
 
But that would mean I need a local testing copy of TS2010 to be sure the item works after the changes are made because if it does not work, guess where those people come for support?
I can fall on that grenade for you if you'd like! But in all seriousness I agree 100% with moving foward.
 
But that would mean I need a local testing copy of TS2010 to be sure the item works after the changes are made because if it does not work, guess where those people come for support?

With all due respect Justin I think you are still missing the point here. If you guys are going to start adding TS12SP1/TANE features to a product, export a CDP of the current one first, dump it in the legacy bin and forget about it. There is no "testing" or "support" any of any sort involved, period.

Regarding the F40PH updates, these are great. Do you think it would be possible to have a page or simple list called Recently Updated Products so that folks who don't follow JR updates closely or have missed announcements can re-download their purchased products?
 
Last edited:
If you guys are going to start adding TS12SP1/TANE features to a product, export a CDP of the current one first, dump it in the legacy bin and forget about it. There is no "testing" or "support" any of any sort involved, period

Actually there is. Most people seem to expect support for anything we have on our site period irregardless of whether its freeware or payware. You'd be amazed how many inquiries I get for problems with freeware. Now we've said before we don't actually support freeware, but I let it slide and help people out. For the most part I've already gone thru and updated alot of anything with TANE issues to be TANE compliant which will be backwards compliant with TS12 which we support so if you are using TS12 you are in luck.

With that all said we can't keep going back and supporting everything old. Time advances, software advances, we need to keep up with that. This is our decision to move forward with. Unfortunately not everyone will be happy with that and that's fine, we respect that, but this is our decision to make as a team.

We will see on recently updated bits, this may be easy to do on our end.

-Kevin
 
Back
Top