Skip to main content

Replies sorted oldest to newest

@MartyE posted:

The "Ghost Whistle" was a really cool feature.  It was cool having the sound guy there to delve into what goes into the sound process.

Having heard that a few times at Strasburg it was indeed pretty darn cool. I also loved how Ryan and Dave sorted alluded to a future use of the announcements that usually go along with the "Ghost whistle" story. So I would expect that there could be plans for a station sounds coach of some sort that will come down the pike.

I just got a message back from Dave Olson, the drivers are the new ones that will be on the final model not the smaller ones. When Ryan was explaining it yesterday I wasn't sure if he was saying that they were the newer larger sized diameter ones or not. So that is a really good thing. I would still have liked to see it in motion though.

I heard that too. In the live video they mentioned they recut the tooling for the wheels and loco frame. Also, they had to recalibrate the speeds for the legacy system. Thats a lot of work to redo. Though I am not getting this locomotive, I very much appreciate lionel’s attention to detail.

Great video and I can’t wait to get mine! Super excited  

Wheel size changes should be super simple. We do it all the time for the 1:1’s as the wheels wear. Wheel size and pulses per revolution of the wheel is all it takes. Maybe they use #defines instead of making these configurable parameters.

-Ryan

#defines.  I lol'd.

I remember one of the first computer science classes in college that I took. The professor came in and wrote some really long number on the board on the first day and asked, "what is this number?" No one knew.

Turns out it was the deceleration constant for the green line metro that some b*tthead left in the code with no comments.

@Ryan Mc posted:

Wheel size changes should be super simple. We do it all the time for the 1:1’s as the wheels wear. Wheel size and pulses per revolution of the wheel is all it takes. Maybe they use #defines instead of making these configurable parameters.

#define is fine if you properly comment it.  I suspect it's probably easier to simply compile the code for each model rather than have a bunch of configuration parameters that have to be loaded for each engine.  #define must be good, I use it.

I like to err on the side of more code comments rather than less.  It makes it easier for me to figure out what I was thinking when I get back to the code a couple years later!

@rplst8 posted:

#defines.  I lol'd.

I remember one of the first computer science classes in college that I took. The professor came in and wrote some really long number on the board on the first day and asked, "what is this number?" No one knew.

Turns out it was the deceleration constant for the green line metro that some b*tthead left in the code with no comments.

What Green Line metro are we talking about? I can say with absolute certainty the LA metro green line code is very well commented. 😂😂

Too bad they didn’t run the engine in the video. It would have been great to see it move under its own power.

@Ryan Mc posted:

What Green Line metro are we talking about? I can say with absolute certainty the LA metro green line code is very well commented. 😂😂

It might have been the DC metro, I'm honestly not sure this was more than 20 years ago, lol.

Too bad they didn’t run the engine in the video. It would have been great to see it move under its own power.

My guess is that with the retooling that was required with the drivers, they are still working on the drive components like the gearbox, driveshafts and linkages.

Add Reply

Post
This forum is sponsored by Lionel, LLC
×
×
×
×
Link copied to your clipboard.
×
×