-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Suggestion] Behavioral differences in AnnounceAll and last car #1005
Comments
Fixed the AnnounceAll rear axle trigger issue, which was unintentional. Adding a new event type which triggers on all axles would possibly be do-able, although I'm not sure that your joint idea is going to work in a sensible way in terms of performance. With regards to DopplerAll, I suspect the difference you're seeing is because the train speed is calculated each time the event occurs. If the train speed is changing as each car passes over the event, you'll inevitably get differing pitch values. |
My idea of rail joints will be discussed in the next issue. |
Apologies, errant return statement that I thought I'd removed.... |
Description
The axle of each car will trigger a sound, and the rear axle of the last car will not be triggered.
Only the front axle of each car triggers a sound, while both axles of the last car trigger a sound.
Out of the meaning of "all (axle)", I would like to exchange features with Announce.
The sound triggered sequentially by the front axle of each car, strangely, both axles of the last car triggered the sound, causing repetition.
This is not the sound event I imagined. What I thinking is for all cars to play simultaneously.
I even think it can be used for pitch fixed joint sounds, but it lacks a rear axle and repeatable triggering.
Funny thing, I made a derailment sound event based on the #997 to entertain myself:)
I want to ask about the difference between DopplerAll.
The text was updated successfully, but these errors were encountered: