Railworks America

When using the build tab and opening up a route to edit, in this case Tehachapi Pass, sometime I get black silhouettes with a blue sky at ground level. I need to exit then go into world editor to make changes. is this an aberration? Also I have noted that not all assets are listed on the assets fly out at the upper RH corner when attempting to enable certain assets.

32 bit or 64 bit? Can you take a pic?

This is what I have. I am using 64 bit. If I exit via the orange arrow in lower right and re enter using world editor all is normal.

I don't know if these is one of those situations but there have been reports of the 64 bit doing odd stuff. There is supposed to be a fix coming this month but in the meantime I suggest using 32 bit for editing. It seems to work fine for painting but other tasks seem to be a bit suspect.

Thank you for the feed back. I am curious if this happens in 32 bit. I will try later. I am not having many issues in the 64 bit editor. Very few access violation issues at all in 64 bit.

I've had this happen on both versions... It lags my game quite seriously, but after pushing the orange "play" triangle, the problem disappears and I can go back to editing by hitting "World Editor" in the pause menu. The problem seems to occur at random.

Interesting to see someone else has the same problem.

AmericanSteam wrote:This is what I have. I am using 64 bit.

Use 32bit, 64bit editor is unstable at the moment.

AmericanSteam wrote:Thank you for the feed back. I am curious if this happens in 32 bit. I will try later. I am not having many issues in the 64 bit editor. Very few access violation issues at all in 64 bit.

RailWorkshop wrote:

AmericanSteam wrote:This is what I have. I am using 64 bit.

Use 32bit, 64bit editor is unstable at the moment.

Allow me to try understanding. Until this is fixed, I do edit a route using the 32 bit version, I test in 32 bit and finally I go back to 64 bit to play a completed scenario. Is that the way?
But it is not logic as the editor should be much more stable using 64 bit (but I understand there is some sort of bug).
I suppose this would also behave that (wrong) way, when designing (editing) a large scenario where you add a lot of static rolling stock and additional scenery. In 64 bit this kind of scenario should be much more stable in 64 bit.

I don't think I would call it unstable. I think from what I read from a statement from DTG that there is a bug of some kind that needs to be fixed in the 64 bit and they indicated that this was going to be done this month yet. This black issue seems like it might be unrelated. I have done a ton of repaints in 64 bit with no issues however there I'm just hitting the restart button not going into world editor very often.

It would seem there are at least two different kinds of "effects" in the 64 bit version (maybe more):

1- The "access violation error" in scenarios in some routes (not all) as in the New Haven - Springfield.
2- The editor with some anomalies (unstable?).

And I agree the black effect could be something else.

jalsina wrote:It would seem there are at least two different kinds of "effects" in the 64 bit version (maybe more):

1- The "access violation error" in scenarios in some routes (not all) as in the New Haven - Springfield.
2- The editor with some anomalies (unstable?).

And I agree the black effect could be something else.

Hi,

About (2), in its current, bugged, state, the 64-bit route editor has the habit of randomly destroying your work. This could manifest itself in signals losing their links, track markers becoming truncated at a track ribbon joint over which then no other marker can be extended any more, or complex (slip) switches becoming broken ("unrendered"). These issues can happen anywhere on your route when you save changes, not only on the tiles/track sections you have edited. As far as I know, all these issues can only be repaired by manually deleting and rebuilding the affected items and/or track segments with the 32 bit exe.

I have personally witnessed all of the above in my own routes. There have also been reports that the scenario editor can fry QD scenarios when editing them in 64 bit mode, but I don't know any details about that.

Bottom line, better don't use the 64 bit exe in its current state for any editing purposes.