ORIGINAL: YankeeAirRat
You both seem to agree that trying to change this issue is going to cause other issues in scenarios built. This seems to be one of those 'tween a rock and hard place issues. I say that because if we fix it to keep a unit with a 7.62mm from shooting down an airplane at the Vhigh altitude we might also prevent those guns which would be capable of engaging aircraft at the Vhigh bands. So one of the possible options would be to add to the database a flag at which the unit could effectively engage certain altitude bands. By adding this flag, we now bloat out the code because now it is going to interrogate this flag and area where the target is at, by bloating the code we now cause stability issues. Another issue by introducing a engagement altitude flag is what if our gun has been introduced into an aircraft unit (such as the M61A1 20mm that is in both aircraft and certain AAA gun systems) and this aircraft is already operating at a the Vhigh band trying to engage a Vhigh target. The game interrogates and goes "Whoops! target is at Vhigh band, DB flag says Surf to High only! I can't engage!". Now you have a new issue trying to fix another. Now we need to add even more db flags and code bloat to fix an issue like that.
A final issue is that we run across even more debates about DB realism. For example a .22 long rifle bullet is capable of traveling up to 2NM prior to losing a huge chunk of energy and begin its fall to the ground. Is it still effective to damage an aircraft at 2NM slant range from the shot? Possibly, there is a slew of math regarding gravity, the coefficient of drag, the power of the powder, and a slew of other ballistics related math. How would we quantify that to a single digit (or digits) for the database? Just because I rate it as a 9 (on a scale of 10) and Smith rates it on a scale of 5 (out of 10) and Jones goes 2 (out of 10) which one would be accurate?
My logic might be just a little faulty, but I think this might be one of those which scenario designer's would just need to work around. There is not easy quick fix for this issue and it might take a while to fix or it might be one of those things that we might just need to accept this is one of those items that can't be fixed.
Bang on, sir. I think that you see the full ramifications of
just about any change to a game system. The ripples of consequence can destructively reach every corner, especially with changes to the underlying fundamental principles of the game.
Your suggestion for Flags and Altitude Bands are interesting ideas and you predicted their possibile implications, too. I can also see additional complications from your suggestions.
Already, the AI seems unable to locate the proper engagement/release altitude for some weapons. Limiting the guns to certain altitudes might further emasculate the current AI. I'm sure that there are plenty of other potential pitfalls if everyone puts their combined heads together. That has always been the reason why
I advocate open and public discussion. No one person has all the best ideas nor the ability to forecast all the problems.
I believe your point regarding the Realism discussion is more easily resolved. Every editor can simply enter what he believes are the correct values. There is simply no need to point the finger and say that others are 'wrong'.
If the values achieve results the users like, then it works. [:)]
I agree that this problem will not be easily solved. In fact, it might be outside the practical parameters of the game as the cure may be worse than the illness. Sure, we might get the occasional CIWS shooting down a B-52 (hopefully not all the time), but it may have to be one of those 'recognized game limitations'. That's for AGSI to decide.