Symon
Posts: 1928
Joined: 11/24/2012
From: De Eye-lands, Mon
Status: offline
|
Moved it here to keep it separate from the Airplane Thread. Good question.
quote:
ORIGINAL: packerpete
I understand your position sir, but let me try to explain my reasoning. I do not have the resources that you possess as to the actual/practical load outs on every aircraft or weapon ever made. I do not have access to the code either (Thank YOU JESUS!!) . You have mentioned that code does not handle certain weapons well or at all in some cases like depth charges, rockets and parafrags. I am also aware of the debate on the US dive bombers getting the bigger bombs. I guess what I am asking for is a common baseline that the AE community can use a starting point with a listing of the weapons that are excluded because of code incompatibility reasons. There just does not appear to a one stop shopping list for this and many areas in regard to weapons that known only to the devs.
I do hope that you would consider my request sir. I do not wish to offend anyone. It just seems to me that on this issue there is a lot of gray areas that need to mapped out for the less informed ones like myself that love this game.
Thank you for your time.
No offense in your question, at all. It is rather extensive and takes a lot of explaining. Reason for that is because some things don’t work because of the game concept and structure, not because they don’t work, per se. Perhaps the best way to say it is that certain things don’t work the way their proponents think they should. There are reasons for this, but to understand why and why not, one needs to get their hands around the scope, concept, and structure (organization) of the game’s various combat algorithms. I’ll try and explain it using one specific example – ASW. The concept extensions apply to other areas, as well.
First, one must understand that every one of the combat modes are separate, distinct, and totally unrelated to each other. Naval ASW is utterly different from air ASW. The weapons used in each of these are optimized for the specific algorithm that controls that form of combat. Simply adding a Nav DC device to a plane’s load-out won’t turn the plane into a DD.
Michaelm made sure that the Device Filters had a bit attribute for ASW. But all that means is the plane will load a device for an AIR ASW MISSION. It does not mean that the device will function the same way as it does for a NAVAL ASW MISSION. That functionality is controlled by two different algorithms. The device filters for aircraft are based on the MISSIONS they can be set to fly. They are not based on weapon device characteristics.
If one wants a “DC” as an aircraft weapon for the ASW “mission”, I suggest adding a device in the file, “Typing” it as an 03 GP bomb, but naming it as a DC and setting the specs where you want them. Now you got Air “missions” and Air “devices” that work together.
Am I making sense, or …
_____________________________
Nous n'avons pas peur! Vive la liberté! Moi aussi je suis Charlie!
Yippy Ki Yay.
|
Printable Version
Alternate Loads - 
but not OUTRAGEOUS
And if any one of the usual suspects complains, to bad. You did your best with a hole hell of alot more information and knowledge than anyone of us has to work with and no one is forced to use it. Just thought it would be a good idea to throw a baseline out there as a starting point for everyone to start with. You and the rest of the Babes team DO set the standard for everyone else to follow and you all do not get enough credit or appreciation. Just my 2 sheckels. 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread