Unzip into a temporary file, Go into the temporary folder, into the Trains/Trainset folder, and then each individual folder has instructions on how to set them up correctly. From - neps_commonsnd.zip, mlw645turbo.zip, emdswmpc.zip, emd_cab1.zip, soo_4449.zip rf_gp38_sound_set_a.zip, rf_gp38_sound_set_b.zip
SLI.BN, SLI.BNSF, SLI.FREIGHT, SLI_22K_SOUND, SLI_26K_TANK, SLI_AUTORACKS, SLI_BNSF_FREIGHT, SLI_CENTERBEAMS, SLI_CN_FREIGHT, SLI_MAXI_STACK, SLI_UP_FREIGHT. From Streamlines Inc, You should be able to adjust certain shapes as needed if you have one but not the other. The following files will be needed in order for this set to be working properly. Included in this first package, is the GMTX, HLCX, and NBSR locomotives currently on the roster. This is the first of four parts to the first freight set of New Brunswick Southern Railway. dds acleantrack files solves the problem.File Category: Modern Diesels (Post - 1960) dds fix, while BSNF Selingman Sub 2 seems to run fine with just the. Also have the MSTS routes BNSF Scenic Sub and BSNF Seligman Sub 2 running.
Interestingly, TS's BSNF Senic Sub OR Optimized comes with. The route is Trainsimulator's BNSF Seligman ORTS. dds acleantrack files, all the others use.
2019.Īs far as I've checked, I only have one route which has.
#MSTS STREAMLINES UPDATE#
route, Twin Cities, does not seem to have the problem, its been loaded for well over two years with the last update Feb. dds acleantrack files, the track displays correctly. I got another update a few days ago, and the problem is still there. After an update in early May the missing acleantrack texture problem showed up. The Detroit-Toledo route was fine in April. My Midwest mini route has 15 routes installed and running okay. I've done some checking regarding mixing routes with.
#MSTS STREAMLINES MANUAL#
If it is, is this "restriction" documented in the OR manual or elsewhere? If true, should this actually be an OR restriction? My OR updates option has been "Testing, Weekly update. Also How does OR notice that routes in the Routes folder have different acleantrack textures? Does OR actually load other than the selected route?
#MSTS STREAMLINES PC#
I'll move one of my problem routes to that PC and have a look.īottom line, I'm pretty sure this is a problem which is of fairly recent origin, and appears to point to Open Rails changes as the cause. I know that I've not seen the problem on that PC as yet, but it s been awhile since I've run OR on that PC and the routes are different. My video card is having problems on that PC, but I'll go and see if the problem is there or not. Again, multiple mini routes which can run under either OR or MSTS. I have another computer which runs Win XP & Win 7 dual boot on which I run the last OR which runs under Win XP, X4334. dds acleantrack files was working okay until recently. I'm pretty sure the mix of routes and mini routes using. I've a dozen mini routes installed with almost a 100 routes freeware/payware and the newest and some of the very oldest MSTS routes. I've been using the "Load DDS in Preference to ACE" option since it was released. Even reinstalled Sherman Hill in another mini route. I thought perhaps I'd somehow lost some files (perhaps due to an uphappy anti virus iterarion), and I reinstalled ScaleRail. Then while poking about, I noticed the problem showed in other routes in the other mini routes. Same with Trainsims BSNF Senic Sub route. 2018, "suddenly" the track problem appears. As example, my 3DTS Sherman Hill route has been running several years and many updates, no. I did notice the change recently, since OR went beyond Win XP compatibility. There are routes that use ace track textures and associated shapes, and there are routes that use dds track textures with associated shapes, and the two types should not be mixed in the same installation. Certain sections, both straight and curved fail to show unless you provide the ACleanTrack.dds textures. It does not matter whether you check or uncheck the "Load DDS textures in preference to ACE" Experimental option. It affects all my mini route setups, and seems to affect MSTS payware and ScaleRail routes run under Open Rails. This missing track texture bug seems to be the result of a fairly recent Open Rails update (I'm running OR version X1.3.1-566-g58c69ee6). This is an effective workaround, but shouldn't this evident OR Bug be corrected in the Open Rails program? Has it been reported as a "Bug Report"? I also confirm that there seems to be no relevant error noted in the OR Log produced when OR closes. Inserting the ACleanTrack1.dds ACleanTrack2.dds and ACleanTrackBase.dds into each Route's Textures file did resolve the problem. I've a dozen Open Rails mini routes with about a hundred routes, both freeware and payware. I've encountered this problem with Open Rails.
0 kommentar(er)
