Quote:
Originally Posted by Suhiir
Without going into techweenie detail that will make most forum readers skip this post cause they were lost after "The Random Number Generator (henceforth RNG) takes as input the current Tick (1000th of a second) Count of the CPU Clock."
Not all RNGs are created equal, and some do have flaws. Also depending on the exact code WinSPMBT uses to access a random number minor (but significant) bias can be introduced.
One reason the gambling industry took a looooooog time to adopt electronic slot machines.
Now I'll put this specific issue to rest as well.
|
OK but... yer computer is not it... and neither is the code in SPMBT... unless... well...
shifting the airstrikes from the 1 known datum to alternates nearby would generate different spotting and firing results in a 1 known datum plus nearby assumed situation.
It is like Andy telegraphed the algorithm... there is no way that anything VISIBLE could be ignored if it is in the same or very close hex of an airstrike. The big catch here is that the new visible unit is a crew that almost certainly didn't have the smoke cover available that the original firing arty did. There is no whoops we blew it up check. The check for crew while last in priority also fails since it is right in the same hex ( a failure in logic ). Only possible approach is the one Andy suggested... without FO with LOS spotting spread them out. Who knows... they might ignore that crew?
Re: Air Strike PriorityTarget - Crews
Hybrid Mode
