| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,815
» Latest member: Kaufman
» Forum threads: 6,474
» Forum posts: 53,632
Full Statistics
|
| Online Users |
There are currently 209 online users. » 1 Member(s) | 203 Guest(s) Applebot, Baidu, Bing, Google, Yandex, Philippe Hurbain
|
|
|
| Running DATHeader without UI |
|
Posted by: Ronald Vallenduuk - 2015-07-18, 0:27 - Forum: Parts Author Tools
- Replies (4)
|
 |
Is it possible to run DATHeader without the UI? I know there's a command line option but that still just starts the normal application.
Inspired by some of the build and deploy automation we use in work, what I'd like to do is set up a Powershell script that runs DATHeader every time I save a file and writes the report to a specified location.
Is that currently possible? Is it a feature you could implement in a future version?
|
|
|
| Train track 'resolution' |
|
Posted by: Ronald Vallenduuk - 2015-07-07, 22:45 - Forum: Parts Authoring
- Replies (12)
|
 |
After I finished 53400, the PF curved track, I started on the PF points (53404 & 53407). As these are going to be big files I wondered if I could reduce the file size. The most obvious way would be to make the steps or sections in the curved rails bigger so as an experiment I changed 53400 from roughly 10LDU sections to 20LDU sections. That took 42% off the combined file sizes of the sub files. I then viewed both versions in LDView and didn't spot a difference:
https://www.flickr.com/photos/duq/195108...ateposted/
So what do you think? Going forward, use 10LDU or 20LDU 'resolution' for curved track parts?
|
|
|
|