Lewiston Clipping Issue [247510]

[Roadwhale]

Greetings, this is my first post ever here. I noticed this bug and thought it might be worth sharing.

In the port of Lewiston, there is a giant cliff asset clipping into the quay walls.

Game version: 1.49
Mods: None
OS: W10 64 Bit

Bug Location: Lewiston (Port), Idaho
Type: Asset placement

Bug_Lewiston_Port_Cliff_Asset_Clipping.jpg

Hope this helps

[Madkine]

Please follow the bug reporting process.

Game logs are important.

[Roadwhale]

I posted the log now. I saw some bug reports recieve a QA ID. Is this bug now accepted and forwarded?

[nautofon]

^ It doesn't happen automatically. Either a tester or SCS staff member has to read and verify each report.

An internal QA number will be issued automatically when the report is accepted and forwarded. The QA number doesn't appear on this forum unless they manually add it to the report in the way you saw for other reports. I believe they pretty much always do that when accepting a report (but since it's a manual process, mistakes can happen). That said, during 1.49, SCS has not exactly been spending a lot of time on the bug forums, to put it mildly. There are probably far over 100 bug reports for 1.49 that no one ever replied to, which is an unusual amount. Not sure what's going on.

Regarding the Lewiston issue you're reporting here—I see it, too. This ought to get fixed.

[Roadwhale]

^ It doesn't happen automatically. Either a tester or SCS staff member has to read and verify each report.

An internal QA number will be issued automatically when the report is accepted and forwarded. The QA number doesn't appear on this forum unless they manually add it to the report in the way you saw for other reports. I believe they pretty much always do that when accepting a report (but since it's a manual process, mistakes can happen). That said, during 1.49, SCS has not exactly been spending a lot of time on the bug forums, to put it mildly. There are probably far over 100 bug reports for 1.49 that no one ever replied to, which is an unusual amount. Not sure what's going on.

Regarding the Lewiston issue you're reporting here—I see it, too. This ought to get fixed.

Yup all good, just wasnt sure about the particular process here because every company does it different. Thanks for the heads up

[nautofon]

@Roadwhale Now it's been accepted: viewtopic.php?p=1946851#p1946851

QA ID 247510