Recent content by Paul_Bert

Download of build 131307 was fast and works fine. So far, I have not noticed any issues when running several of my large routes. Frame rates look good, and CPU and GPU usage is very good even with a draw distance of 22,000 m draw distance. Will keep testing some more today.

I install my beta tests, both the program and data on a separate drive. That way there is no confusion or risk on altering my official release version.

John, these are the only built in JR US tracks I have. I cannot find <kuid:66128:44547> JR US track (pro) KSC2 -1 (narrow ballast) on my installed version (build 131068). Any ideas? Built in JR track on my installed system. <kuid2:506034:4357297:7> JR US track #3-132 (narrow ballast)...

Here's what I have found. I took my largest route with the route size of 1285.2MB and the session size of 36.6 MB. The route is running in HD and a draw distance of 22,000m. The track I am using is TRS19Trk Jarrah 5 Procedural Seasonal running on PBR Crushed Stone 27 Ballast. This route has...

I have not noticed any issues here. I have my draw distance set at 22,000m for all my routes. I have tested the issue on several of my large routes in the HD mode and find no difference between this build and build 129343.

Question about the imposters. Does this affect all the speed trees or only some. I use mostly the RMM trees. If only some use the imposter feature, how do you know which ones?

Update went smoothly. Ran several of my large routes and saw no issues. No faulty assets after update.

I have Trainz Plus running build 128486.

My computer has Directx 12 installed. When I go to the setup option in Trainz it only shows Directx 11 as available. Am I missing something? At some point will Directx 12 be available?

Any update on when DirectX 12 will be available for Trainz. I am in the same situation as Forester1. DirectX 12 is installed in my system but only DirectX 11 is available in the Trainz setup.

Updated two computers from build 128486 to 129343. Updates took less then 10 minutes including rebuilding the data base. No problems, no errors. Everything works as expected.

What has worked for me is to go into the CM and selecting the problem track. I then delete it and then re-download it from the DLS. This has worked for me on about 10 different tracks. It changes the status from “modified” to “installed from DLS”

To fix the problem I delete the asset and then reinstall from the DLS, as mentioned above. This has worked in all the "incompatible spline" I have encountered so far.

Thanks. I was including the "p" in the search field and the were no results. I in fact had the package installed as it turned out and still was getting the "not active" message. I un-installed the package and then reinstalled it. This solved the problem.

I have two assets that are marked Packaged Payware (not active). When I select the asset and open "Report Container Package" I get sc242p. Where do I find sc242p? Why should it appear in my content manager if I did not purchase it?