I was working on self guided missiles and then the update came i updated and it no longer works now it gives random pitch numbers. Note: it only happend on the small missile radar for me.
Votes by users: 6
Sat 09 October 2021 20:30
CPU
AMD Ryzen 5 5600X 6-Core Processor (x64)
AMD Ryzen 5 5600X 6-Core Processor (x64)
GPU
NVIDIA GeForce GTX 1650/PCIe/SSE2
NVIDIA GeForce GTX 1650/PCIe/SSE2 4.6.0 NVIDIA 536.23
RAM
81920MB RAM
81920MB RAM
OS
Windows 10 Pro 10.0 64bit
Windows 10 Pro 10.0 64bit
Product
Stormworks
Stormworks
Version
v1.3.5
v1.3.5
Closed (Implemented)
Defect
I was working on self guided missiles and then the update came i updated and it no longer works now it gives random pitch numbers. Note: it only happend on the small missile radar for me.
Duplicates of this issue:
3829 3830 3833 3836 3878 3932 4017 4065 4139 4266 4283 4320 4452 4470Wed 13 October 2021 19:04
User
Developer
Thank you for the report. This has been fixed in an upcoming version.
Issue closed
Tue 19 October 2021 09:15
User
Developer
Correction - should be fixed in v1.3.7
Fri 22 October 2021 18:28
Issue described in Defect #1894 is still not fixed in 1.3.7, see issue in Defect #1894. It is not a duplicate of this issue, as is stated in the description of that defect.
Fri 22 October 2021 19:07
Found out the issue: the radars are adding the magnitude of the pitch angle to the magnitude of the azimuth angle. This should be an easy fix for v1.3.8 I hope.
Fri 22 October 2021 21:35
Sorry about that. I did not read the ticket #1455 sufficiently and misunderstood that #1455 reports a bug regarding the Azimuth Angle value.
#1894 is a report of a different bug than #1455.
Nevertheless, it has been clearly stated many times by others that #1894 is a report of a different event, and I don't think that #1894 would be considered to be a duplicate of #1455 if dev were to sort out the bug reports based on those statements.
I don't know who in dev is sorting this out, but I'd be interested to hear what the intention was for #1894 to be merged into #1455.
(Or maybe dev simply considers this to be a specification, not a bug, and merged it into a similar topic.
This is clearly not something that happens only in my environment, and it doesn't seem to be a specification to me either.
I would like to hear an explanation of how dev thinks about this, rather than just having it sorted out in a bug report. Is this just a trivial event for dev?
Translated with www.DeepL.com/Translator (free version)