Gunrunner

Yes, but the engine is clearly not from a IIIC, and it can neither be a CJ nor a CZ, hence I assumed illustrator error/laziness...

Unlikely, Iraq never bought any Mirage III or 5, at least directly and that I know of. We never sold them to Iran either and I don't see any other Arab Sunni country giving them to Iran... however... we sold Mirage IIIEL (they have all the external features of that profile) to Lebanon, and considering this country's relations with Syria and in turn Syria's relations with Iran, it's not entirely impossible that some Mirage IIIEL might have ended in Iran's hands... My research so far to validate that idea : - From 1968 Lebanon received 10 Mirage IIIEL and 2 Mirage IIIBL - The only recorded loss I found is of a Mirage IIIBL (with a possible EL loss in 1973 but unconfirmed) - The whole fleet was grounded for budgetary/political reasons in the late 70's and later put in storage - Around that timeframe Dassault considered the fleet to be in good shape with no cannibalization - In the late 90's 9 Mirage IIIEL were sold to Pakistan (it isn't clear whether the BL was part of the deal) - At some point the LAF apparently changed the planes serial numbers, making it harder to track That leaves 1, possibly 2, planes unaccounted for, of which at least one is a EL, the other one being either a EL or a BL.

From discussions with engineers : - Engineers with FMS knowledge believe their network is properly isolated from the IFE network. - Engineers with FMS knowledge seem conflicted over what he meant by "reprogrammed" but they seem to think he has misconceptions about how their software work (which is their polite way to say he seems clueless on the topic). - None of them exclude that in retrofits or to shave off weight and costs both networks might not be air-gaped as they should be but they have no personal knowledge of such case and consider it criminal negligence if it ever happened. - It's scary how most engineers have limited knowledge outside of the particular part of a subsystem they work on. When read properly Chris Roberts claims are as follows : - He did access the entertainment network of multiple planes, sniffed around the network and found flaws. - He has working knowledge of flight control networks and engine control software... in a virtual machine. (Which is weird in itself as it begs the question, where did he get a FMS virtual machine or source code ?) - He believes both network aren't properly secured and air-gaped. - He never claimed to have actually bridged the gap between the two systems or accessed the flight control network in flight. My take : - Chris Roberts presented theoretical possibilities in words that could be taken as actual events out of self-aggrandizing habit (He once claimed to have taken control of the environmental control of the ISS and raised the onboard temperature). - The FBI was perfectly aware of it but thought it was a good opportunity to justify their budget, security theatre and some legislation. - The media saw a perfect opportunity to prey on the public's fear to sell more ads. - Chris Roberts is trying to get his own TV show and pull a Walter O'Brien... - Chris Roberts, as a security expert, is bleeding credibility fast, other researchers and specialists in the field are combing through his previous work and claims and tearing him apart, he apparently committed professional suicide.

Wait, 4 Battle-class ? AFAIR there only were two involved in Korea, besides the majority of Commonwealth destroyers were C-class (mostly from the RN and we, mostly, have them), then Tribal-class (the RCN ones, we don't have proper ones) and only then the two Battle-class RAN destroyers, followed by a V-class or River-class destroyer here and there. The majority of Sydney's escorts were Tribal-class and American destroyers, the two Battle-class destroyers only escorted Sydney during a few of its patrols, the rest of the time they were assigned to RN carriers escort, shore bombardment or islands protection. So yes, the Sydney has almost no escort, not because we are missing the Battle-class but because we are missing the Tribal-class. This was a message from the Tribal-class Appreciation Society... ahem...

quack74, the viewer makes decals quite a bit easier though, while you don't see them, when you mouse over the model it gives you the coordinates, which in conjunction with having the proper node name, makes the game only useful for resizing and the the last centimeters of adjustements.

1. When ? Study started in late 1951, early 1952. First flight 1953, entry into service 1954 2. Why was it made? Australian Meteors in Korea demonstrated that the Meteor's time as a fighter was over, still it proved a very competent CAS aircraft, wings were lengthened to increase loiter time and increase payload, engines were relocated to make them less susceptible to ground fire, provisions were made in the wing to add more guns 3. Who would have made it ? Gloster 4. What would be its official designation/name? Lance FB.1, to be thematically in sync with the contemporary Javelin 5. And what would be its unofficial, but cooler, name? The Boar, both because it spends most of its time close to the ground and because its stable, unsurprising, unimpressive flight characteristics made it a "bore" to fly

Yep, good times, especially knowing there's still a lot as a WiP, despite the occasional HD crashes. @Spinners, not necessarily but that would mean that we, as a community, need to make an ethical/legal decision (considering SF2 abandonware or not, how to go about it) and that we will require an entirely new type of modders to go forward (coders).

Skyviper, search for Julhelm's Shadowcat, it's his version of the AFX which is more or less what you want (the original SF1 thread which still has pictures : http://combatace.com/topic/27759-natf-again/).

That's intentional, MAPENEMYICON.TGA is entirely transparent, to "solve" it, just remove that file from the Flight folder.

View File Colourful Korea - A skin and decals pack for Wings over Korea COLOURFUL KOREA Some assembly required. --------------------------------------- WTF is this ? --------------------------------------- This is a mod of a mod, it's intended to be used as a "patch" for Do335 Wings over Korea mod, itself a mod of the semi-avorted Korean Air War mod. Its intent is to add more units, more skins and, above all, more named planes to the Korean War. It's meant to be a patch, to keep the footprint low, making it useless by itself. It's also a backport from my own Korean War install meaning that some things might not be as originally intended (for instance, in my own install the SAAF 2nd Squadron uses slatted wings F-86F-10's, which is - mostly - historically correct, however a standard WoK install gives hard-wing F-86F-30 - of which they only ever had 1 - to 2nd Squadron). My focus on these releases is maintaining compatibility with the WoK campaign at the cost of "authenticity" (which would require something much more grandiose with at least 3 campaigns, which is a work in progress but not aimed for release - too much unclearable content being used). --------------------------------------- Why such a miscellaneous and crippled package ? --------------------------------------- Because I'm slightly burning out on the Korean War, that Real Life is coming back and that rather than having "finished" work rot away on a hard drive, I'd rather release what can be so others can enjoy or build upon it. Also because I'm too lazy to walk the minefield of varying licences involved in packaging someone else's content. And yes, someday I'll finish the Thunderflashes, if Paulo doesn't beat me to it. --------------------------------------- What are the pre-requisites ? --------------------------------------- - Some knowledge of Strike Fighters 2 mod installation procedures. - A properly installed Wings over Korea 1.0 by Do335 installation ( http://combatace.com/files/file/13415-sf2-korea-terrain-v3/ , http://combatace.com/files/file/15221-wings-over-korea-1-of-2/ , http://combatace.com/files/file/15220-wings-over-korea-2-of-2/ ). --------------------------------------- What are the pre-requisites for the optionnal Razbam Banshee skins ? --------------------------------------- - A properly installed Razbam F2H-2 Banshee ( http://www.razbamsims.com/store/product_info.php?cPath=1_4&products_id=45 ). - Wrench's Korean Air War Tweak Pak for Razbam's Banshees ( http://combatace.com/files/file/14889-sf2-kaw-f2h-2-banshee-tweeks-pak-for-razbam-banshees/ ). - Do335 optional files for Razbam's Banshee (overwrite Wrench's tweaks). --------------------------------------- What is included ? --------------------------------------- - 4 new skins for Razbam's F2H-2 Banshee covering VF-172, VF-11, VF-22 and VF-62 for the Korean War (VF-22 used in campaign). - 2 reworked skins for South African 2nd Squadron F-86F Sabre, including 29 historical named planes (almost all of them) (one skin used in campaign). - 5 additionnal named Australian Meteor F.8, plus one modified decal for an existing one (used in campaign). - 1 partially modified skin for RF-51D Mustang (adding polka dots to the propeller nosecone), including an historical named plane (used in campaign). - 1 template for Razbam's F2H-2 Banshee. --------------------------------------- What is not included ? --------------------------------------- - Anything already present in the pre-requisites. - Razbam's skin parts that I haven't redone. --------------------------------------- What's the required assembly ? --------------------------------------- - South African F-86F : None, overwrite when asked - Australian Meteor F.8 : None, overwrite when asked - USAF RF-51D Mustang : None, overwrite when asked - USN F2H-2 Banshee : Copy the following files (some may not be needed but in doubt do it) from an existing skin into the VF-11 and VF-62 skin folders (VF172 and VF-22 are ok) ejection seat.bmp glossy_t.bmp glossy_t.tga gunsight.bmp gunsight.tga interior03.bmp interior04.bmp interior05.bmp interior07.bmp landing gear_t.bmp parts01_t.bmp tires.bmp --------------------------------------- Probable questions --------------------------------------- - Hey, why are you using an inefficient ZIP format when RAR5 and 7Z offer much better compression rates ? Because RAR5 breaks backward compatibility while using the same extension, leading to many confused people believing their download to be corrupted, leading to re-downloads, increased bandwidth consumption for CombatAce and overall a greater cost than a slightly larger archive and more headache for the player. Because 7Z requires to install a dedicated software while Windows does manage ZIP files natively, making it much easier for players. - Hey, why are your skin in a funky PDN format instead of a standard Photoshop PSD file ? Because, even with Creative Cloud, Photoshop can be too much money for some modders and I don't condone piracy. Because Paint.NET ( http://www.getpaint.net/ ), the software using PDN files, covers 95% of skinner needs, especially when using the PSD plugin ( https://psdplugin.codeplex.com/ ) to open PSD files (DO NOT use RLE compression when saving in PSD format though) and the Alpha Mask plugin ( http://forums.getpaint.net/index.php?/topic/1854-alpha-mask-import-plugin-20/ ). Because Photoshop makes me jump through more hoops than Paint.NET to obtain some layer interactions. - Hey, there shouldn't be rivets here / Hey, that colour is slightly off / Hey, 202 actually didn't have his code painted on the wing / Hey, the decal seems to be bleeding etc... Yes, I'm probably already aware of all that, some of it can't be changed by anyone so you'll have to live with it, some of it is ignored to keep things simple and tidy, and finally many are ignored because I've reached the point where, at the moment, I'm not willing or able to do better. Feel free to add your own corrections and changes and either submit them to me for another release (you'd be credited of course), or release your own mod of a mod of a mod. - How do I contact you ? Well, PM me on CombatAce, when Real Life is involved it might be some month before I answer though, or you can mail me, but unless it's important, it's highly probable I'll just ignore it, sorry. --------------------------------------- Acknowledgements --------------------------------------- - TK, even though he has forsaken us, he gave us a nice little engine to play with. - CombatAce, for being such a nice place full of nice, if at time weird, people doing their best to keep TK's little engine fun to play with. - The Korean Air War team, without whom none of this would exist in the first place, even though their grand scheme never happened, their years of work didn't go to waste. - Wrench, The, whose Banshee Tweak Pak gave me the weird idea that some people actually cared about a payware of an obscure, little used plane. - Jolley Roger, over at the unofficial SAAF forum, for starting and curating a thread that became a great refence for the SAAF sabres ( http://www.saairforce.co.za/forum/viewtopic.php?f=2&t=7069 ). - Mue, whose LOD Viewer ( http://combatace.com/topic/85079-lod-viewer/ ) is an invaluable tool to Strike Fighters modders. --------------------------------------- Credits --------------------------------------- Everything is either derived from Thirdwire's assets, those included in Do335 Wings over Korea mod - refer to the Readme of this pack for full details - or so trivial I can't be credited for them, with the exception of : F2H-2 Template ans Skins : Gunrunner (except the Bits and pieces layer, which is based on Razbam's skins). F-86F Template : Ravenclaw (90%), Wrench, The (9%), Gunrunner (1%), I mostly added a few details, a noise layer, reworked invasion bands, tail and nose decorations. VF-11 Squadron Badge, 2nd Squadron Badge, "Elyana" and "Bowl'Em Over !" nose arts for Australian Meteors : from my "decal vault", if it's yours, drop me a line and I'll credit you or remove/replace it. Gunrunner 14 February 2015 Submitter Gunrunner Submitted 02/14/2015 Category Other Origin

1952, somewhere over Korea Tailless designs, modern ? Pah ! And I'm pretty sure it should read Julie, but I'm yet to find solid sources to confirm my gut feeling.

Flogger23, if you only want to see changes in the texture, just hit the reload button. Of course, if you made any change to the LOD itself, it's another story I think (haven't tested it though, maybe the whole thing is reloaded not just textures).

It seems the meshing over textures doesn't work all the time and sometimes only on part of models (the F-86E-10 LOD doesn't display some parts, it's fairly weird, I'll upload a screenshot later on). Also, I may have missed it, but is there any way to unselect a node once selected ? Finally, a suggestion, is adding a "hide node" option on right-click in the node list on the table ? It would help when skinning overlapping rails/fuel tanks or when checking if parts you plan to remove don't leave a gaping hole.

And the guy is - given the mods presented and some of the links - at least a lurker here, so he should know better... That's what pisses me off most.

On the bottom list, right-click on a texture filename, click on show all nodes on texture, choose the mesh color and you can save it as jpg (just do it with a plain color file as "skin" if you want a clean file) and you're golden... or have I misunderstood what you wanted ?

Damn Mue, thanks a lot, again, I don't know how I did without your tool before, spending hours or days doing what takes minutes now; You really provided us with an invaluable tool. Any chance you'll add the handling of decals at some point ? (and fake pilot grafts, and loadouts, and... just kidding... even though, now that I think about it... ;) keep up the good work)

Let us be clear, "reverse-engineering" is not a crime, it might be a breach of contract under certain legal systems, but reverse engineering something you have a legal ownership or licence over is actually a good thing, it starts becoming a problem depending on what you do with that newly found knowledge/content. What is legally and ethically dubious is to use that ability to either pass someone else work as your own, or distribute in ways the original author didn't intend or allow. The first priority of the community should be to keep itself alive and make the work of modders easier while staying legal and ethical, not to handicap itself to increase revenues of payware, however good it is and however nice the people behind it are. Believe me, if someone wants to profit from your hard work, they will, whether honest modders have easy access to the tools or not. An acceptable compromise in my opinion would be to have a read-only version generally available, and a full version accessible though CombatAce only to members recognized as modders or having proven they will not use it to abuse someone else's work.

AFAIR, the problem is that you are modeling it as a SARH missile, which to the game engine means you need a constant link, what you want to do is model it as an ARH, besides, I'm quite sure the R-77 had been done over and over as part of red birds or in weapons pack, by people actually knowing what the hell they are doing, so please save yourself (and those trying to help you) the frustration and headache and just use that, believe me, they know what they are doing, the reason why it's been modeled as an AHM is not because some of the finest modders in the community are complete idiots and you are a genius, but because it's how you should do it to have it behave as closely to the real thing as possible. ;-)

It so happens that currently the site is in recurring financial difficulties, the paying members being too few relative to the free members, which means that the site can't cover operating costs and more importantly the bandwidth costs (when you download a mod, it costs money to the site, publicity covers part of it but is not enough, subscription are there to try and cover the rest). I would gather that Jarhead1, a long-time member of the community made a sizable donation to help relieve that situation, hence Dave's enthusiasm and well-deserved recognition of Jarhead1's contribution to the community (btw, I tip my hat to you, sir). I must point that the situation is due to too many people thinking that they can just download and not give anything back, be it by being an active member on the boards, becoming a modder or simply paying for a subscription plan you can afford. I think we all understand that you might not have the age or financial means to contribute, which is probably why Erik et al really don't want to resort to limiting download access, but for those of us who can and as of yet don't, please consider subscribing.

Dave, could you discuss with Eric the possibility of a financial breakdown of the site's operation, maybe as a sticky, so that non-subscribing members can get a better idea of WHY they need to subscribe if they can afford it (of course it's understandable not to if you can't) ? By the way, how much money would you actually need (on that note, I know you usually don't like it but maybe the donation could be back for those of us who don't have the option to further upgrade our existing subscription - through wire transfer would be nice too) ? Maybe also work out something that would remind each of us how much bandwidth we've used so far (and how much it did cost), maybe as a private information like our warning status ?

You can't remotely operate a mule, you can't have mules mount weapons (well, you can, but the results might be a tad... underwhelming). Further research/training into real mules won't have them being autonomously useful. Even trained mules have a tendency to wander around, or if under fire, behave erratically, I don't think soldiers under fire would welcome having to deal with a panicked pack mule on top of that... It's easier and faster to deal with attrition with robot mules (field repairs are an option) rather than real mules (who can't get back right to service after changing some parts, meaning you need to have 2/3 times the number of mules you need to replace the casualties). Even not taking into account the higher number of real mules it would take to perform the same mission as robot mules, one should consider that real mules need to be fed, their pens need to be cleaned, there arise a need for field veterinarians, and suddenly the support necessary to operate real mules is superior to the one needed to operate robotic mules, of course the cost, including R&D, of robotic mules still maybe higher, but it's so much easier, more predictable. Robot dogs... a dog sensor package is fixed, varies depending on the individual, requires years of training and gives information fairly incomplete and subject to interpretation, a robot is immediately operational, upgradeable, the efficiency is a given, the readings are supposedly unequivocal, you can send it to it's "death" without batting an eye should the situation require it and so on. Of course it's horrendously costly if you take the R&D costs into account, but the end result has the potential to be far superior and more useful than their biological inspirations. On another note, one can't complain about these programs and still find the F-35 costs entirely justified. (I HAD to ! ^^ )

Are you really missing the point ? Do I really have to explain why choosing the wrong tool for the job at the cost of procuring less of them is not a good solution (in the F-104 case, it was the wrong tool but at least it was compensated by the fact A LOT of them were procured). The less aircrafts you have, the more crippling a loss is. The less aircrafts you have, the quicker it will age and/or the less training your pilots get. The less aircrafts you have, the less aircrafts you can get in the air at any given time. The less adapted to it's main mission an aircraft is, the more planes you need in the air to fulfill the same mission. Norway and the Netherlands are placing themselves in a situation were it would be simpler and less costly to simply abandon their air force altogether, with their current plans in a decade they'll be where Switzerland currently is, forced to operate minimal hours, reduce training and be on the verge of not being able to fulfill its mission in a credible manner. Of course some would say that the F-35 is more survivable and less maintenance intensive than alternatives, increasing its availability and thus making fewer planes as efficient, and that is partially true, however there is little chance that the increase in survivability and availability are in the vicinity of what is needed to compensate for the very small fleets (by some estimates the F-35 gains make it up to 1.5x as efficient, but they cost 2x to 3x time as much...). Now, concerning Australia and Canada, it is true that it has indeed better range than the Hornet (and AFAIR the Super Hornet), however that range increase comes at the cost of a smaller air-to-air payload in air defense role (which would mean the need for more planes etc...). It is also true that for decades Canada made do with planes falling very short of their needs anyway. The curse of the F-35 is that its cost progressed faster and further than its gains in operational advantages, making it a poor choice for anyone not being able to afford a large fleet and intending to use it as their main or only asset. Is that so hard to understand ?

Indeed, suppositions, and what do you think the optimistic estimates are ? Suppositions as well... No one ever got the best result by just assuming that everything will be rosy and work as expected, always prepare for the worst-case scenario, and in that worst-case scenario the F-35 is simply NOT the right tool for the job for at least a third of the buyers... It doesn't matter that a Bugatti Veyron is the fastest and most luxurious car money can buy, when what you have to do is haul a family of 5 and their luggage, there are cheaper and better alternatives.

Yes, because it's so much better to assume success based on gross exaggerations from the manufacturer and a government desperate on selling the plane to lower it's own unit price... Look, for what it's worth the F-35 is a great choice for the US (inflated cost and teething problems notwithstanding) , it will be a great asset for Israel as well (they intend to use it in a manner well suited to its design), Italy, Japan, South Korea and the UK should have no real problem with it either (they'll use it primarily for its VSTOL features and/or as a primarily strike oriented asset, it might be overkill for Italy and Japan, but still, these countries will use it as one plane among others). For Canada it's a stupid choice, it lacks the endurance for its main air defense role (but that's been a constant for Canada), and the benefits it brings in its secondary strike role are too small and come at too high a price considering how little (if ever) it will be used in that role. For Australia, again a lacking choice, it is barely adequate in its air defense role and lacks range in its long range strike role. For Norway and Netherlands, it's an inferior choice for it's main role as an air policing asset, which costs forces them to have a smaller, less competent force, all this for a theoretical advantage in its secondary role that will materialize only in scenarios those countries almost never participate... For Turkey the plane itself is irrelevant, the F-35 procurement is above all a political status symbol and as such will perform admirably, politics is the only dimension that matters in that particular case. Any country buying the F-35 as its main air defense asset is making a costly mistake, it's not a fault of the aircraft though, it's not the hammer's fault if its owner's using it to hammer screws.