el cid again
Posts: 16922
Joined: 10/10/2005 Status: offline
|
RHS Comprehensive Microupdate 6.42 https://1drv.ms/u/s!Ap7XOIkiBuUwhb0jGIADmOGILZhCKg?e=FMWDGf This important updated includes extensive changes to Scenario Files, as well as RHS Documentation files and pwhexe.dat files. Begun as a major effort to review most of the remaining Allied aircraft types (to integrate new or changed sensors, improve upgrade paths, improve and to the greatest extent possible automate production of aircraft, to recalculate aircraft payload ratings, and to improve performance of code with respect to drop tanks), major problems (dating from stock) related to the Canadian Air Force forced a review of related aircraft types. These in turn caused significant revisions in RHS documentation files. A few other issues were addressed, including device, location, air group, task force, ship and class eratta. It was found that the RCAF, which becomes the fourth larges air force in the world by 1945, was poorly modeled. Due to a lack of slots and the fact the RCAF is substantially integrated with the RAF, this was difficult to address. In particular, a review of Lancaster and Lincoln aircraft was undertaken which resulted in comprehensive changes. RAF, RAAF, RCAF & RNZAF were revised such that, late in the war, they can all share the same Lancaster FE and Lincoln aircraft model. One other case has the Lancaster X model shared with RAF and RCAF. Art issues were also discovered: we had a brown color scheme (vice white) for Lincoln, and several cases of Lancasters with the wrong color scheme and/or the wrong turret art. These were integrated using the existing art. This was easier because Lincoln is a renamed Lancaster variant. Indeed, counter-intuitively, the many Lancaster names differ mainly in respect to the origins of the engines or the subsystems (which can be British, Canadian or US), and sometimes with respect to turrets. In the end we ended up with more free slots for aircraft, with a much better modeling and upgrade route, still bounded by the nationality of the aircraft (even when shared). This also is likely the very last time we need to relocate industry (re airplane production) - so future updates won't produce odd outcomes in ongoing games. Drop tanks were invented by Matrix, but didn't work until RHS figured out how to define them in data. There is no code to make intelligent decisions, however, IF drop tanks are defined, and external bombs are defined, both will work even if on the same hard point. Thus, a centerline drop tank and a centerline bomb can co-exist, as far as code is concerned. The same for external drop tanks (meaning non-centerline). We had to only allow both when both are possible (which is quite rare). So some combinations cannot be defined in game. Nevertheless, full external loads were determined. Thus - numerous later P-40 types (in many nations) still can carry bombs on the wings in terms of maximum load rating even though we can't actually show them with maximum load. [Due to how code works, most of the time we use what should be called normal loads, not maximum loads]. Another effect of this review is to give fighters more range at extended range because they are "clean" - without external bombs. A new table of pilots is attached in documentation, but Mifune must put it into code - as my editors won't work with them. I will issue that as a microupdate when he completes entering the data. Other future work will include a review of Tiger Force - because I found a complete list of its squadrons. However, except for fixing minor eratta (which I do when it is reported or found), and for issuing the new files related to those pilots, I am suspending development for a while (so I can write a real report for a USAF think tank on today's airplanes). I also found names of some in game pilots who are commanding officers which at some point I will look at to see if they are in the database, and even if they are, if they have the correct assignments.
|