Log In
Register Now!
Help
The Problem in replay #18 is fixed in X2723.
thanks very much.
Here I have reported a Problem with mainsignals in German Routes, described in replay #1 of this thread:
https://bugs.launchp...or/+bug/1403820
Lack of semaphore shape
Rate Topic:
#21
- Conductor
-
- Group: Status: Contributing Member
- Posts: 472
- Joined: 15-April 13
- Gender:Male
- Simulator:MSTS
-
Country:
Posted 18 December 2014 - 06:12 AM
#22
- Superintendant
-
- Group: Status: Elite Member
- Posts: 1,772
- Joined: 27-October 12
- Gender:Male
- Location:Budapest
- Simulator:OpenRails
-
Country:
Posted 18 December 2014 - 11:04 PM
Eugen, the test case you uploaded to launchpad is absolutely perfect! :pardon:
The problem lies in SignalShape constructor, at the place Carlo committed the fix for the other problem. There is the statement in comments: "All sub-objects except the first are hidden by default. The sub-object visibility comes from mstsSignal.SignalSubObj". I don't know the reason of it, obviously it must be true for 99% of the signals, but is clearly not true for this particular signal. For this signal to be shown correctly, all the matrix nodes must be displayed here. I wonder what could be the general difference to other signals. It is interesting at this signal, that the invisible nodes all have an animation node assigned. Maybe the nodes with acting as animation node also must be visible by default, even if they would be invisible after applying the "SignalSubObj" visibility mask?
The problem lies in SignalShape constructor, at the place Carlo committed the fix for the other problem. There is the statement in comments: "All sub-objects except the first are hidden by default. The sub-object visibility comes from mstsSignal.SignalSubObj". I don't know the reason of it, obviously it must be true for 99% of the signals, but is clearly not true for this particular signal. For this signal to be shown correctly, all the matrix nodes must be displayed here. I wonder what could be the general difference to other signals. It is interesting at this signal, that the invisible nodes all have an animation node assigned. Maybe the nodes with acting as animation node also must be visible by default, even if they would be invisible after applying the "SignalSubObj" visibility mask?
#23
- Member, Board of Directors
-
- Group: Status: Elite Member
- Posts: 7,013
- Joined: 31-December 11
- Gender:Male
-
Country:
Posted 19 December 2014 - 01:13 AM
Hi Peter,
after some email exchange with Eugen, I provided him this morning a patched Runactivity.exe to test if the problem has been removed.
As maybe this can interest you, here is the patch.
Signals_mainProtrain.cs.patch.zip (868bytes)
Number of downloads: 164
Pls. note that with the patch I could remove the comment "Note: parent matricies in the hierarchy are not considered" which I think was the reason of the problem.
Eugen and someone else are now testing the patched runactivity.
after some email exchange with Eugen, I provided him this morning a patched Runactivity.exe to test if the problem has been removed.
As maybe this can interest you, here is the patch.
Signals_mainProtrain.cs.patch.zip (868bytes)
Number of downloads: 164
Pls. note that with the patch I could remove the comment "Note: parent matricies in the hierarchy are not considered" which I think was the reason of the problem.
Eugen and someone else are now testing the patched runactivity.
#24
- Conductor
-
- Group: Status: Contributing Member
- Posts: 472
- Joined: 15-April 13
- Gender:Male
- Simulator:MSTS
-
Country:
Posted 01 January 2015 - 02:18 PM
With the X2675 from Rob, OR can now handle signals with moving parts which consist of multiple matrices.
Carlo has fixed with X2723 and X2750 the Problems with not showing shape parts and Speed limit numbers of some Signals in German PT-Routes.
thanks very much
EugenR
Carlo has fixed with X2723 and X2750 the Problems with not showing shape parts and Speed limit numbers of some Signals in German PT-Routes.
thanks very much
EugenR