If anyone have the "ding" problem when opening a blueprint, that means your blueprint xml is too big for the "improved" blueprint editor. If this happens, try to batch the child blueprint objects. For example you have 8 light child object attached to your engine blueprint, delete them, and make a scenery blueprint instead, and add the lights to it, and then add this scenery blueprint as a child for your engine blueprint.
For me, blueprints above 1 mbyte causing this "ding" error, with batching i reduced the size below it, so i can open them without problem.
October 9th Update
Moderator: Moderators
-
vlado960
- Well Established Forum Member
- Posts: 753
- Joined: Wed Jun 25, 2008 10:21 am
- Location: Croatia
Re: October 9th Update
Who know what's new in last update. Now is ver v25.1b ?
Re: October 9th Update
Most, if not all the utilities have been updated, also the two files in the plugins-folder. 'Last modified' in railworks-folder should tell the details, thovlado960 wrote:Who know what's new in last update. Now is ver v25.1b ?
-
tnleeuw01
- Very Active Forum Member
- Posts: 2493
- Joined: Sat Oct 08, 2011 11:17 am
- Location: Diemen, Netherlands
Re: October 9th Update
Yes, but knowing that Utilities.exe for instance has been updated.... doesn't tell you what's been fixed, if anything.Makeone wrote:Most, if not all the utilities have been updated, also the two files in the plugins-folder. 'Last modified' in railworks-folder should tell the details, thovlado960 wrote:Who know what's new in last update. Now is ver v25.1b ?
With route updates, yeah you can see that there's been an update to a route, or to some rolling stock for instance. Even that doesn't really tell you what's really been changed / fixed / broken with the latest update.