![]() |
#11
|
|||||
|
|||||
![]() Quote:
First of all, available stores can be simply listed for the plane. If the SC 500 is not on that list, because it was not available for a plane type the player is not able to select it in the first place. Again, historical accuracy has nothing to do with the method wheter you choose your aircraft`s loadout from a rigid preset or put it together from single pieces. Secondly, incompatibility with other loadouts also is simple to program as attribute; simply you give it attribiutes that if player chooses Loadout A (say, droptank) he can no longer select Loadout B (say, an SC 250), but he can select something else, like an external armored glass, tropical filter or such. So, in a practical example, there`s nothing preventing the developer, should evidence arise - other than your belief that it wasn`t if I may add - to that the 500 kg bomb could not be used with gondolas, then he could simply add a line to the section describing the gondolas that once they are choosen, 500 kg cannot be choosen, and vica versa; or to add a line to the 500kg bomb that it cannot be used with certain plane subtypes (because it is too big for them). Again, if you`d have actually bothered to read what I`ve written, you`d stop having the false idea that I propose that every plane should be able to choose every loadout, 109s with SC 1800 and the like. That is NOT what I propose. What I propose is basically a streamlining of the GUI to a much more user friendly one, which is easy to overview, and perhaps easier to develop in the long term. Otherwise, when you will have aircraft with 2-3-4-5 attachment points, historical possibility for rear tanks to be filled, extra ammunition, you will either have to spend a lot of time having either a, an EXTREME number of loadouts listed, with high probability that something will be overlooked and bugged b, simply not having several important, and historical loadouts available to the user PS - 109K was the first one to have been officially cleared for the 500kg bombs, and I suspect it was possible on late versions with the long tailwheel - it was a ground clearance issue with bigger bombs, not a takeoff weight issue. Quote:
I am not in favour of 'purist' players dictating 'casual' players what they can fly and cannot; he majority of the customers are not 'purist', nor for the matter of fact these 'purist' have the right idea always; often they only have just some strong-headedness. Not that historical accuracy should be sacrificed, not at all - it should be available to the server HOST as a tool to decide what equipment does he makes available, and to what extent (ie. no rare/experimental loadouts allowed, limited number of plane types that saw service in small numbers etc.) I've written that down clearly in my previous post, it`s a pity you don`t bother to read them. Now, if one would want to fly in a 'purist' enviroment, he is free to create his own server or join a server made for 'purist' players with full real settings. But others should able to select more casual simulation experience. The limitations of the plane are written down in their manuals. The manuals are available. It`s easy to sort out what can be fitted to each plane and what not. It`s also irrelevant from the point of historical/technical accuracy, wheter you choose that from a pre-set list or 'build' your own loadout from given modules (bombs, rockets,etc). The advantage of a modular ordonance system would be : - ability to use any and all historical combinations, not limited by the amount of resources spent on it by the developer - much simplier and less work for the developer on the long term - and actually easy-to-use GUI, thinking ahead when we will have dozens of planes with hundreds of loadouts. Overall, you completely miss the point and simply do not get what I propose. Quote:
Problem starts when you have to apply it to all others - eventually, there will be hundreds of loadouts, and dozens of flyable aircraft. Will you do the historical research on availability for EACH and EVERY aircraft, bomb type and so on? How many FW 190s were available on June 1942? How many droptanks for them in September 1943? How many P-47s had paddle props in March 1944? How many gondolas were issued to Bf 109 units on November 1944? How many SC 1800 bombs dropped by Stukas in 1943/ You have any idea how difficult would that be? Quote:
And again, it has nothing to do how the loadout it selected; the adding of the MK 108 gondolas had nothing to do with how the loadout was selected; the lacking of Panzerblitz rockets have nothing to do how the loadout is selected. Historical accuracy has nothing to do how the loadout is selected. It`s purely a practical question of GUI and development. This decision must be taken early, as later it is difficult to revise it. Quote:
It`s simply inflexible, limits your choices to those that could be done in a limited amount of time, and later there`s usually no big change - new developments taking away resources simply.. for how long do we lack vital loadouts for the 109F and others because of this??!! The other thing in the GUI that would be definietely useful with over time is a FILTER function for PLANE SELECTION. I.e. ability to show only FIGHTERs, BOMBERS, ATTACK aircraft etc; this combined with some advanced, multi-lever filtering (ALLIED + BOMBER + MID WAR for example). Again, it`s not an issue yet, but it will be when there will be a lot of planes.
__________________
Il-2Bugtracker: Feature #200: Missing 100 octane subtypes of Bf 109E and Bf 110C http://www.il2bugtracker.com/issues/200 Il-2Bugtracker: Bug #415: Spitfire Mk I, Ia, and Mk II: Stability and Control http://www.il2bugtracker.com/issues/415 Kurfürst - Your resource site on Bf 109 performance! http://kurfurst.org ![]() Last edited by Kurfürst; 12-23-2007 at 04:49 PM. |
Thread Tools | |
Display Modes | |
|
|