Skip to content
This repository has been archived by the owner on Apr 27, 2024. It is now read-only.

Unable to sync RailDriver with NEC GP38-2 #7

Closed
moparacker opened this issue Apr 23, 2020 · 2 comments
Closed

Unable to sync RailDriver with NEC GP38-2 #7

moparacker opened this issue Apr 23, 2020 · 2 comments
Labels
bug Something isn't working
Milestone
0.1.6

Comments

@moparacker
Copy link

Loco(s): GP38-2
Map: NewRochelleNewarkMap
Scenario(s): Terminal Switch, New York Switcher, Back Track

Unable to sync game with RailDriver, even though RailDriver shows "CL". Connector is showing correct map, but will not register the loco.

Attempted restarting of Connector, no fix. Tried with V0.1.4 and V0.1.5, same result.

Affects all GP38-2's on all NEC maps.
@Yamazaki93 Yamazaki93 added the bug Something isn't working label Apr 25, 2020
@Yamazaki93 Yamazaki93 added this to the 0.1.6 milestone Apr 25, 2020
@Yamazaki93
Copy link
Owner

This turns out to be that there'a different variant of GP38-2 that's "slightly" different than the other ones, this will be fixed in 0.1.6

@moparacker
Copy link
Author

Rechecked issue with RDConnector v0.1.6-beta.0, able to sync and drive GP38-2 as expected.

Dynamic brake functions, but has same fluttering issue as GP38-2 on SandPatch. Updated Issue #6 with this info.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
0.1.6
Development

No branches or pull requests
2 participants
@Yamazaki93 @moparacker