Jump to content

Kuban map zero level -1mt - How to repair?


Recommended Posts

Posted (edited)

I have all my ships that are about 1 meter under the normal zero level.

This  problem appeared with one of the recent updates where we had to resave all the missions. I did not see it before as I was mainly working on the editor and testing trains, vehicles and planes.

This on the Kuban Summer map.

This problem does not appear on the Rheinland Summer map.

 

I remember there was an issue on height and a correction had to be done, which I did not do. I cannot find the post of Jason regarding this correction.

It seems to have disappeared as we do not have access to older update posts.

 

If anybody is kind enough to remind me how to correct that I will be very grateful.

 

 

 

Edited by IckyATLAS
Posted

resaving the mission should fix altitudes (as ships cannot be set manual)

make sure that the correct height map is selected (season, ...)

 

If that results in 'no success' -> bug report

 

Deci

Posted

I made a full stock reinstall but nope. There is an elevation bug with Kuban Maps. 

Posted (edited)

Here you can find pictures of the bug:

 

1)Moscow map:   Submarine and Torpedoboat on lake

1551374958_SubmarineandTorpedoboatonlakeMoscowmap.thumb.jpg.94da588bf7ffa29d1e5b06404e6b3ede.jpg

 

2)Rheinland map:  Submarine and Torpedoboat on sea

1456266737_SubmarineandTorpedoboatonseaRheinlandmap.thumb.jpg.ae0345f358ab8263ec1018dfbe9eea09.jpg

 

3)Kuban Map: Submarine and Torpedoboat on lake

1006758098_TorpedoBoatandSubmarineonlakeKubanMap.thumb.jpg.df9aab403e9dca72a7800743ca60210f.jpg

 

4)Kuban Map: Submarine and Torpedoboat on sea

615928030_TorpedoBoatandSubmarineonseaKubanMap.thumb.jpg.c9031fe265690b053d01f1e794af3344.jpg

 

You can clearly sea that on lakes there is no problem. But on the Kuban sea (sea state 0) the base level of the ships is approx -1mt.

This is true for all model of ships. So when there are some waves the torpedoboats become submarines.

 

You do not sea this error on the Rheinland sea because on Rheinland map the sea is in fact treated as a lake. It is not a real sea.

On the Moscow map you have only lakes.

 

I suppose the devs to shorten development and simplify things just because the sea share of the Rheinland map is small and action takes place on the mainland they have not bothered to properly model the sea, and used a lake model much simpler.

 

The only map where the sea is modelled is the Kuban map and the sea is buggy.

 

This is probably so since version 4.501 at least. This was not so before. This should be corrected.

 

Edited by IckyATLAS
Posted
5 minutes ago, IckyATLAS said:

Here you can find pictures of the bug:

 

1)Moscow map:   Submarine and Torpedoboat on lake

1551374958_SubmarineandTorpedoboatonlakeMoscowmap.thumb.jpg.94da588bf7ffa29d1e5b06404e6b3ede.jpg

 

2)Rheinland map:  Submarine and Torpedoboat on sea

1456266737_SubmarineandTorpedoboatonseaRheinlandmap.thumb.jpg.ae0345f358ab8263ec1018dfbe9eea09.jpg

 

3)Kuban Map: Submarine and Torpedoboat on lake

1006758098_TorpedoBoatandSubmarineonlakeKubanMap.thumb.jpg.df9aab403e9dca72a7800743ca60210f.jpg

 

4)Kuban Map: Submarine and Torpedoboat on sea

615928030_TorpedoBoatandSubmarineonseaKubanMap.thumb.jpg.c9031fe265690b053d01f1e794af3344.jpg

 

You can clearly sea that on lakes there is no problem. But on the Kuban sea (sea state 0) the base level of the ships is approx -1mt.

This is true for all model of ships. So when there are some waves the torpedoboats become submarines.

 

You do not sea this error on the Rheinland sea because on Rheinland map the sea is in fact treated as a lake. It is not a real sea.

On the Moscow map you have only lakes.

 

I suppose the devs to shorten development and simplify things just because the sea share of the Rheinland map is small and action takes place on the mainland they have not bothered to properly model the sea, and used a lake model much simpler.

 

The only map where the sea is modelled is the Kuban map and the sea is buggy.

 

This is probably so since version 4.501 at least. This was not so before. This should be corrected.

 

 

Thanks, I have reported this in the closed  beta forum as issue for public version 4.502

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...