Weird Sensor Error/issue?

[poulviggen]

I have installed the 19.0 update, and the game playability is great.
What is weird, however, is platforms that formally had sensors, (18.3) now have none.
There is no radar or sonar, just a 20km surface search radar that I can't control.

I am thinking of the UK's Bristol DD (a very interesting ship) but now unplayable.

I added the ship to an existing senario, as well as the Ark, just for fun, but the ships are essentially useless.

I'm not sure what other information is needed, so I thought for my very first post, I would
start with this.

Thanks.

[Citadelvette]

I haven't had this problem. You might be experiencing some database corruption, I've had some with the MIg-23BN and Mig-23K. You might try Running NWPCall.bat or a virgin install.

[Mike D]

I have installed the 19.0 update, and the game playability is great.
What is weird, however, is platforms that formally had sensors, (18.3) now have none.
There is no radar or sonar, just a 20km surface search radar that I can't control.

I am thinking of the UK's Bristol DD (a very interesting ship) but now unplayable.

I added the ship to an existing senario, as well as the Ark, just for fun, but the ships are essentially useless.

I'm not sure what other information is needed, so I thought for my very first post, I would
start with this.

Thanks.

Yeah, I'm with Citadelvette. Your db is messed up. I just ran a test scenario with the Bristol DD, Ark Royal (1965). Ark Royal (1970) and the Tiger CL thrown in for good luck and the sensors were just fine.

I'd actually do a new download Of 19.0 too. I've seen files get corrupted more then once during the download or upon decompression by the installer.

[poulviggen]

Virgin install (2) does nothing. same problems.
(now I have Burke class with no radar).
now, I'm guessing that the platforms will have pretty much the same sensors that V18.3 did.

where is NWPCall.bat ?


another issue is that no surface ship has ever hit any aircraft with sams.
(related to sensors)?

I have noticed that there is no NWP section in the INI file, should there be?

How big/many should the database files be?

18.3 used to work pretty well, but I cant play 19.0 at all, which is weird, because I was used to the occasional CTD, but now everything is incredibly stable, the graphics work and look great, but no one can hit anyone else. (sams accually fly away from their targets, and I'm talking airliners here) I set up some easy kills according to 18.3, but 19.0
stumps me.

[Mike D]

Virgin install (2) does nothing. same problems.
(now I have Burke class with no radar).
now, I'm guessing that the platforms will have pretty much the same sensors that V18.3 did.

where is NWPCall.bat ?


another issue is that no surface ship has ever hit any aircraft with sams.
(related to sensors)?

I have noticed that there is no NWP section in the INI file, should there be?

How big/many should the database files be?

18.3 used to work pretty well, but I cant play 19.0 at all, which is weird, because I was used to the occasional CTD, but now everything is incredibly stable, the graphics work and look great, but no one can hit anyone else. (sams accually fly away from their targets, and I'm talking airliners here) I set up some easy kills according to 18.3, but 19.0
stumps me.

Ok, try this. Delete all the files in ../Fleet Command/Database and all the files in ../Fleet Command/Doctrines. Then reload 19.0 and see what happens.

Something is wrong with your db because those units in my master db, which is what the install was built off of, are just fine and also nobody else is reporting these problems. So it has to be something with your local installation. Its just figuring out what.

[poulviggen]

Sorry, no dice, Burkes only sensor is SAM as/ss radar 8.5 nm.

(it does have a sonar, right?)

[Mike D]

Sorry, no dice, Burkes only sensor is SAM as/ss radar 8.5 nm.

(it does have a sonar, right?)


Your objects table is all messed up, the objects table and the sensors table of the db are out of sync and/or mismatched. The only unit that has that sensor in NWP is the M163A2 Vulcan SPAAG. The Burkes have 2 radars, 3 sonars, and 2 visual sensors in NWP.

Did you delete all the files in ../Fleet Command/Database and reinstall NWP 19.0? Also what version of FC do you have, Janes, SCS, Steam? Could it be possible that you have FC loaded in two location on your machine. I've seen that happen before, especially with Steam installs, and then the game gets seriously confused.

The CallNWP.bat script won't help, that installs the graphics into your db.

I attached a screen capture of the 19.0 database files with sizes and dates. I also attached a screen capture showing the Burke sensors in NWP.

[poulviggen]

Did you delete all the files in ../Fleet Command/Database and reinstall NWP 19.0?
Done. still non-functional.

Also what version of FC do you have, Janes, SCS, Steam?
Janes.

Could it be possible that you have FC loaded in two location on your machine.
I've seen that happen before, especially with Steam installs, and then the game gets seriously confused.
No. file scan has only the files in ../Fleet Command/Database (the date is 1 hour off -5.59pm)

[cj95]

Was there ever a solution to this, because I have the exact same issue.....I was wondering why none of my missles were hitting anything...no guidance.

Bristol....Burke...probably a few others are seriously messed up.


Running Janes with only one install......is there a link to go back to 18.3 ??

[Lancer]

The situation with ship launched SAMs is true. I did a test where it is set up to be ridiculously obvious. I launched a 747 in flight and parked a Burke DDG below it with an initial range of 10nm. AS radar was turned on to ID it, as the plane approached, all launched SM-2MR SAMs would initially intercept, then at about half a mile from the ship, they disappear or prematurely shut down. Looks like a doctrine situation, can't help you check past the db specs.

[cj95]

Well I seem to be having a combination problem of the No Sensors bug in combination with the Subs dont respond to commands.

I cant help but figure they are related.

I wonder....if the obj database is the issue, perhaps somebody with a healthy database could just email that particular file to plug in.

if its something different....then perhaps someone could point out where to download 18.3 or a previous version?

Its a shame because it seems to be running real smooth otherwise.....a rareity for me. :)

[Mike D]

Well I seem to be having a combination problem of the No Sensors bug in combination with the Subs dont respond to commands.

I cant help but figure they are related.

I wonder....if the obj database is the issue, perhaps somebody with a healthy database could just email that particular file to plug in.

if its something different....then perhaps someone could point out where to download 18.3 or a previous version?

Its a shame because it seems to be running real smooth otherwise.....a rareity for me. :)

The way that your problems are related is brobably that you database is hosed. That will effectively mess everything up.

[Mike D]

The situation with ship launched SAMs is true. I did a test where it is set up to be ridiculously obvious. I launched a 747 in flight and parked a Burke DDG below it with an initial range of 10nm. AS radar was turned on to ID it, as the plane approached, all launched SM-2MR SAMs would initially intercept, then at about half a mile from the ship, they disappear or prematurely shut down. Looks like a doctrine situation, can't help you check past the db specs.


Drop me an email at mjdobbins@austin.rr.com I want you to try out some doctrines for me and see if it helps the disappearing SAMs.