Quote:
Originally Posted by TorpX
Thank-you Cap'n.
Is there anything which prevents us from putting in more than one visual sensor for a type of aircraft?
|
Well....the game only uses one o01 Visual sensor at a time from the specific object/craft its linked to.
You
can however have different values for that sensor at different points of time during the game's time span. I don't know why you would do this, but you could for instance make a new entry in the Data/Air/ADB_B5N2_Kate/ADB_B5N2_Kate.sns file....Adding another [Sensor xx] entry....linking it to your Visual sensor found in the .dat file, but change the "StartDate=", "EndDate=" to have it start sometime after the usual 19380101 start date. Then having it run until the games usual end of 19451231.
Don't forget to change the existing [Sensor 1] (the original Visual sensor) dates that cover the entire game span time. You'll need to have the EndDate of the first Visual sensor to end one day prior to the StartDate of the second....and don't use some unreal date like 19430431. There's no such date as April 31, 1943!! Only 30 days in the month of April. Some of the stock entries do exactly this....have their dates either overlap, or have dates that don't exist. Believe me, the 'ole computer can count two plus two!!
Like I said, I'm not sure why we would want to change the visual sensor to have different values at different time periods? It's not like the Japs used some kind of X-ray vision half way through the war.
To Crannogman's credit, the idea of having a plane with specific values greater than others is a sound one. A Mavis with several crewmen, SHOULD be able to spot an object better than a single pilot. That's why the idea of linking a specific visual sensor, with greater capabilities, to specific craft makes sense. Why RFB 2.0 doesn't do a very good job of that.....don't know? What I
do know is the MinSurface=-75.0 value for all of RFB's planes is like spotting a fly on the top of an ant hill at 1000 yards!!