Civil_Genius Posted November 26, 2005 Posted November 26, 2005 Taking all player Flyable Aircraft for the (USA) and replacing them with one of these old school aircraft A-6 Intruder, A-7 Corsair, or the A-4 Skyhawk.
GGTharos Posted November 26, 2005 Posted November 26, 2005 ... Why? [sIGPIC][/sIGPIC] Reminder: SAM = Speed Bump :D I used to play flight sims like you, but then I took a slammer to the knee - Yoda
britgliderpilot Posted November 26, 2005 Posted November 26, 2005 Taking all player Flyable Aircraft for the (USA) and replacing them with one of these old school aircraft A-6 Intruder, A-7 Corsair, or the A-4 Skyhawk. Hey . . . . . that's a stunning idea!! Why has nobody thought of this before? ;) Not going to happen. The game is called "Modern" Air Combat - and while they take a bit of artistic license as to what that means, the A-6, A-7, and A-4 just don't fit in properly. I believe Strike Fighters models at least one aircraft in that list (the A-4), and the upcoming Jet Thunder is going to model the A-4 as well as the Mirage, Pucara, and Sea Harrier - a fantabulous list of stuff we don't normally get to play with. I'm really looking forward to Jet Thunder . . . . http://img.photobucket.com/albums/v121/britgliderpilot/BS2Britgliderpilot-1.jpg
504 Wolverine Posted November 26, 2005 Posted November 26, 2005 Welcome to the forum, and replacing flyable isnt possible. Lock-On has not got open architecture like MSFS and only ED can add flyables. After the Black shark add-on (1.2). ED will be dropping the Lock-On sim (well prehaps patches for 1.2) to work on their next simulator. One that they have all legal rights to. [/url]
britgliderpilot Posted November 26, 2005 Posted November 26, 2005 Welcome to the forum, and replacing flyable isnt possible. Lock-On has not got open architecture like MSFS and only ED can add flyables. After the Black shark add-on (1.2). ED will be dropping the Lock-On sim (well prehaps patches for 1.2) to work on their next simulator. One that they have all legal rights to. To clarify - they will be dropping the Lock On NAME, which Ubisoft have rights to in the Western world. The Fighter Collection still own the rights to the code, so ED further developing the code they have is just fine. http://img.photobucket.com/albums/v121/britgliderpilot/BS2Britgliderpilot-1.jpg
504 Wolverine Posted November 26, 2005 Posted November 26, 2005 To clarify - they will be dropping the Lock On NAME, which Ubisoft have rights to in the Western world. The Fighter Collection still own the rights to the code, so ED further developing the code they have is just fine. Yeah i know all the publisised legal stuff but........ Ford dropped the Escort name and updated the chassis as well. Do you still call the Focus an escort. ;) :p :D [/url]
britgliderpilot Posted November 26, 2005 Posted November 26, 2005 Yeah i know all the publisised legal stuff but........ Ford dropped the Escort name and updated the chassis as well. Do you still call the Focus an escort. ;) :p :D I don't know enough about the progression from Escort to Focus to answer that question :p It is likely that the code from Lomac will be developed into a newer and better product with a different name. It won't be all-new, it'll be built on Lomac . . . . that's basically what I'm trying to say. http://img.photobucket.com/albums/v121/britgliderpilot/BS2Britgliderpilot-1.jpg
Woodstock Posted November 26, 2005 Posted November 26, 2005 I wonder what makes more sense: Reworking a code that 2 years after its release still doesn´t run on any existing system in full detail and with lowered detail still makes a $4000.- system go down to single-digit fps over a lively battlefield. Code that might not even have found the hardware to run smoothly by the day LO´s successor is released. Or writing something new from scratch and avoiding mistakes made. "For aviators like us, the sky is not the limit - it's our home!"
upyr1 Posted November 26, 2005 Posted November 26, 2005 hi, Since LOMAC dose take a lot of CPU power to run, I hope ED's plan is to keep the basic and just add theaters AC and a few other touches to it I'd love to see what this game can do as the hardware evolves.
SuperKungFu Posted November 26, 2005 Posted November 26, 2005 Taking all player Flyable Aircraft for the (USA) and replacing them with one of these old school aircraft A-6 Intruder, A-7 Corsair, or the A-4 Skyhawk. lol so you want to take the planes that are already modeled....and just throw it away. And remake A-6, A-7 and A-4....hmmm....interesting....:icon_jook [sIGPIC][/sIGPIC]
Brit_Radar_Dude Posted November 26, 2005 Posted November 26, 2005 I wonder what makes more sense: 1. Reworking a code that 2 years after its release still doesn´t run on any existing system in full detail and with lowered detail still makes a $4000.- system go down to single-digit fps over a lively battlefield. Code that might not even have found the hardware to run smoothly by the day LO´s successor is released. 2. Or writing something new from scratch and avoiding mistakes made. That's easy - the answer is 1, rework. I have been in the business of writing software for military radars, military comms, ATC systems etc. for over 20 years on projects ranging from a few man-months to 300+ man-years. Sensible rework of a existing system is much cheaper and reliable than starting from scratch. What you have to understand is that writing the actual software is a tiny part (about 10% or less) of the overall project timescale, most of the time is spent on testing. Write a new system from scratch equals total retest. Whereas rework of an existing system equals retest of the bit you changed plus some regression tests to check the rest of the system still works. Point 2 You need to add another line at the end so it reads - writing something new from scratch and avoiding mistakes made, and adding hundreds of new bugs ;) [sIGPIC][/sIGPIC] Sorry Death, you lose! It was Professor Plum....
Woodstock Posted November 28, 2005 Posted November 28, 2005 That's easy - the answer is 1, rework. I have been in the business of writing software for military radars, military comms, ATC systems etc. for over 20 years on projects ranging from a few man-months to 300+ man-years. Sensible rework of a existing system is much cheaper and reliable than starting from scratch. What you have to understand is that writing the actual software is a tiny part (about 10% or less) of the overall project timescale, most of the time is spent on testing. Write a new system from scratch equals total retest. Whereas rework of an existing system equals retest of the bit you changed plus some regression tests to check the rest of the system still works. Point 2 You need to add another line at the end so it reads - writing something new from scratch and avoiding mistakes made, and adding hundreds of new bugs ;) I see your point, but from a user´s point of view I have to say: I am in the business of using software for radars, comms and ATC systems for quite some years now and the last time we were bound to get an update for our crapy RDPS at Munich that patch was delayed until further notice since it downed the whole Frankfurt (Langen) Center after install there. Sometimes sh** remains just that, no matter if you change colour, smell or flavour... But no need to dig further into this. Cheers, m8! "For aviators like us, the sky is not the limit - it's our home!"
Recommended Posts