Recent content by PC_Ace

@H222 - Recommend increase your Virtual Memory to provide more resilience in these events. If you have 32Gb DDR4 or 5 RAM, then allocating 64Gb or more of PageFile memory on your fastest SSD is definitely helpful for smooth Trainz database and merge operations. Mine is set to 96Gb spread over a...

Nope - N3V will remove the DRM if things get that terminal - they have clearly stated this in the past. I'm confident that Trainz is here to stay for quite some time to come and have thoroughly enjoyed 'our hobby' for 20-odd years.

Bring my trees back!! Whilst the provided Tree Factory examples and imposters display ok in my routes when added to the scene - almost all others disappear/ fail to render at all, at intermediate LODs and in the distance. Persistence of objects is really important to me in Trainz scenarios. I...

You'll love your new 990 Pro SSD. Same as mine, which I installed as my C: Drive. Super fast and makes a huge difference for Trainz EDBRs and TrainzUtil.exe operations. (My current production/ gaming rig has five SSD drives for a total of over 10Tb physical storage space.) Each Trainz...

Time to upgrade your Trainz drives to SSDs, John! These are absolutely the best single performance upgrade possible for any build of Trainz (after ensuring that your GPU & VRAM combo is adequate for running Trainz, which in your case, is more than sufficient). They are amazingly affordable these...

Yup. The client refresh completed quickly on my beta build (129139) upgrade, but the Trainz Plus 128486 (PC) to build 129343 patch resulted in a VERY lengthy, Full DBR/ Client Refresh. Seemed to be longer than a 'normal' EDBR in fact. As it was 'silent and in the background' many users would be...

Thank you!

Success. No thrashing database repairs either... Thank you.

Somewhere between 20 and 30 minutes of threshing fans and overheating cores - i.e. much longer than ANY previous EDBR has ever taken (me). I replicated the experience as mentioned above. Each time it became clear that it was stuck on some intractable process, it was time to terminate the...

Following run; TrainzUtil.exe repairdatabase patcher Command completes (63s) I click on Start Trainz in Launcher. Window opens (slowly) as there is a silent EDBR/ client refresh going on in the background, which I reveal by invoking 'Show client logs'. It lasts indefinitely. Last record revealed...

I can reliably repeat my above experience. The (not so silent) EDBR after running the repairdatabase patcher command (which completes within 63 seconds) and then starting the simulator from the Launcher to the main splash menu runs indefinitely in the background and utilises all CPU cores at...

Ran the above Trainzutil command and it took 63 seconds to complete. Then I started up Trainz from Launcher and observed an EDBR taking place silently behind the scenes via "Show Client logs" command... Did you see this too, @pware? Have not been able to run any tests so far whilst this EDBR is...

Running Trainzutile exe 'repairdatabase extended' took 549 seconds on my installation rather than the 22 seconds taken by the plain 'repairdatabase' but net result was the same - no additional spline errors noted following subsequent testing.

Thanks for this update @n3v_laurence. Running repairdatabase from trainzutil.exe appears to be a standard DBR and not an EDBR. Is that your impression too? (No issues, BTW).

Suggest check that you have 'Enable 3D sound' in the main in-game settings dialog. They seem ok here on cursory examination, but what is your exact use-case where you've observed this? (Which specific assets no longer exhibit doppler sound effects?)