[FIXED B498] B469, The 4 Horsemen: Satellite classified as SSGN and 2 more problems

[gdir]

Hi,

I'm currently playing the scenario 'The Four Horsemen' with B469. I have three problems regarding the satellites. I'm not sure if I have messed up my installation or if these are real problems. Could you please have a look at it?

My installation: Was originally 1.01, then updated to B460, then updated to B469. No clean install directly from 1.01 to B469. It should be possible to unzip B469 over B460, shouldn't it?

Problem 1:
The Four Horsemen scenario is linked to database DB3000 build 369. If I look at the satellite Kosmos 1836 in the database, it is classified as SSGN (see attached image). This happens also when I link the database to the newest build (DB3000 build 400).

[gdir]

2. Problem:

The Kosmos 1836 has an optical sensor. The satellite flies at a altitude of 235 km, but the sensor range is only quoted as 100 km. Even when the satellite flies directly over the 2 CV groups (at daylight with clear sky) it doesn't spot anything. Is that a bug?

The other satellites with ESM sensors work fine.

[gdir]

3. Problem:

I wanted to provide a save file for both problems. I saved about 15 seconds after I made the screenshot. In the screenshot you can see that Kosmos 1836 is going to fly over Keflavik air base and then over the 2 CV groups. But when I open the save file, Kosmos 1836 has a different orbit far off Keflavik and the CV group.

[gdir]

Arrrgh, this thread should be filed under Tech Support. Can somebody move it, please?

Are these real problems or have I messed up my installation?

[gdir]

I found out that orca already reported the false classification of the satellites 2 weeks ago (problem no. 1). So it's probably not related to my installation:

tm.asp?m=3474770&mpage=1&key=satellite&#3474770

As orca writes all satellites are classified as some kind of submarine.

[Dimitris]

Thanks!

#1 was a typo, fixed in Build 472.

#2 is a toughie. We're aware some of the satellites have apogees higher than their sensor ranges and we need to figure out if this is a RL restriction or we need to adjust the sensor data (probably the latter).

We'll look into #3.

[gdir]

Thanks, Sunburn!

Regarding problem #3 I got the impression that the satellite positions and directions are different each time I open the save file. I don't know what's causing this. The scenario has only an event to randomize the submarine positions at the start of the game, but not on loading a save file.

[Dimitris]

Orbit position problem fixed in Build 498.

The sensor coverage problem has been fixed a few builds back.