+Wrench Posted June 13, 2009 Posted June 13, 2009 View File Ordway's Early MiG Pits -Upgrade/Repair Package Early MiG Series Cockpit Upgrade/Repair Pakage for SF/SFG/WoV/WoE/WoI & SF2/SF2:V/SF2:E This is a rebulid of Ordway's Early MiG pits for use in ALL the 3rd Wire Series. It's designed for the following aircraft (and/or variants thereof): MiG-15bis (by Pasko) Stock 3rdWire: MiG-17 Fresco-A MiG-17F Fresco-C MiG-19S Farmer-C It is also, therefore, completly useable for any of the myriad 3rd-Party mods of variants of these aircraft (excepting those Frescos and Farmers that are radar equipped -doh!) Specifialy, it's designed to REPLACE the original versions, as some (including myself) have experienced odd CTDs with an 'aircraftobject.dll' fault in the SF2 series.. By rebuilding these with a STOCK A-4B cockpit lod (albeit from WoE), and reusing Mr. Ordway's VERY COOL gauge bmp repaints, and re-editing the A-4B_cockpit ini, this has been eliminated. This mod has been EXTENSIVELY tested in SF2, as this was the basis and reason for the 'fix', and will work in the Classic Series just as well as the originals. All necessary parts are included. I even snuck in some Generic WoE-style Hangar screens for the 17 & 19. These will also work in ANY version of the sim. As always, it's reccomended that you unzip this package to temp folder, or your desktop, to gain access to the rest of the readme for it's specific instructions. Which are gonna run a bit on the long side....so you probably (read: SHOULD) read the document all the way through first before installing. Just to be safe, doncha know :yes: With expecial thanks to Mr. R. Ordway for creating these in the first place!! Good Hunting! Wrench Kevin Stein ps: yes, that's still the original screenie. why mess with a good shot? Submitter Wrench Submitted 06/13/2009 Category Jet Cockpits Quote
+ordway Posted June 13, 2009 Posted June 13, 2009 Thanks Kevin, deeply appreciated! Keep converting my cockpits if you have the time. I'm deep into making the six Mig-23 cockpits and their associcated Starfighter2 specific HUDs. "This is a rebulid of Ordway's Early MiG pits for use in ALL the 3rd Wire Series. It's designed for the following aircraft (and/or variants thereof): MiG-15bis (by Pasko) Stock 3rdWire: MiG-17 Fresco-A MiG-17F Fresco-C MiG-19S Farmer-C" Quote
+Wrench Posted June 13, 2009 Author Posted June 13, 2009 Thanks! I can't wait for the New Flogger pits!!! wrench kevin stein Quote
+paulopanz Posted June 13, 2009 Posted June 13, 2009 Sir, the cockpit upgrades are very good (as usual for Your works), but for the Mig-15bis you missed to do this: [RangeCounter] Type=RANGE_INDICATOR CounterNodeFormat=distance_dig%Remd <--------- change this to: distance_dig%d MovementType=ANALOG_COUNTER ValueUnit=NM Like I and Suhsjake discovered upgrading to SF-2 standard old Pasko's Mig-15bis models (see topic). Paolo Quote
+Wrench Posted June 13, 2009 Author Posted June 13, 2009 Oppps!!! Well, missing one entry ain't so bad!! Actualy, I really didn't DO anything, other than simply copy/paste the bmps over existing A-4B ones! Same for the cockpit inis, just a little clean up (and looks like I missed a spot...where's my Windex and shop rag????) If you look further down, into the "moved items", you'll see the range counter moved away, so it really isn't even there!! wrench kevin stein Quote
+guyran Posted June 13, 2009 Posted June 13, 2009 Hi Wrench Excellent job, I didn't get the RWR tone in both Mig-17 and Mig-17F, until I have copied the MIG-19_avionics.ini file from Mig-19s folder to both Mig-17s folders. Without it there is no audible tone. Thanks, guyran Quote
+Wrench Posted June 14, 2009 Author Posted June 14, 2009 hmmmm.... -Editing the Main Aircraft ini to Activate the Cockpits/Avionics: Ok, now that you've got the cockpit folder into their various aircraft, lets activate one. In this example, we'll be using the MiG-17F Fresco-C. ALL the steps are the same for EACH, excepting the MiG-15, were you won't be adding the avionices.ini, as it has no RWR. Open the MiG-17F.ini, and you'll see this: [AircraftData] AircraftFullName=MiG-17F Fresco-C AircraftShortName=MiG-17 AircraftDataFile=MiG-17F_data.ini LoadoutFile=MiG-17F_loadout.ini Obviously, missing and all lines that make it player flyable. So, you'll need to add the following lines: CockpitDataFile=Mig17_Cockpit.ini AvionicsDLL=Avionics60.dll AvionicsDataFilename=MIG-19_avionics.ini HangarScreen=Fresco_Hangar.bmp Just stick them under the original statements. You'll see on this one, I've given the Fresco-C the avionics ini statement; this will give you an audio-only RWR. You don't have to use it, if you don't want to. For the MiG-15bis, as this has really nothing electronics/avionics wise, just use THIS line: CockpitDataFile=MiG-15bis_COCKPIT.ini Take the 4 wav files I've supplied -as I couldn't remember exactly which one I used-, and toss them into your /Sounds folder. You may already have them, so don't worry if asked "OVERWRITE?". They're the same, so say YES. Yeup, you're right! I forgot to include that step!!! ADDENDUM to the Above Install Instructions: "Take the Mig19_avionics.ini, and toss a copy into each folder you want to activate the audio-RWR. It's reccomended for the MiG-17F and MiG-19S only, as I could find no data if the MiG-17 Fresco-A had any type of warning device" Ok, 1 oppsy and 1 almost oopsy (the range counter) wrench kevin stein Quote
shiden Posted July 21, 2009 Posted July 21, 2009 I tried this today and the MiG-15 cockpit would not work. than I checked the .ini and saw this: [CockpitSeat001] ModelName=MeteorF8_cockpit <---? I changed this to A-4B_Cockpit and it worked again...not sure why it would change like that Offset=0.0,-0.08,-0.03 Position=0.0,0.55, 0.7 ViewAngles=0.0,0.0,0.0 MaxYaw=155 MinYaw=-155 MaxPitch=90 MinPitchFront=-50 MinPitchRear=-20 LightRange=1.5 LightInnerConeAngle=43 LightOuterConeAngle=60 LightAngles=0.0,-35.0,0.0 DiffuseLightFactor=0.5 NightLightOn=0.25 NightLightColor=0.5,0.2,0.3 Gunsight=GunsightFront Instrument[001]=AirspeedIndicator Instrument[002]=Accelerometer Instrument[003]=RangeCounter Instrument[004]=Altimeter Instrument[005]=AtitudeIndicator Instrument[006]=VerticalVelocityIndicator Instrument[007]=HSIWheel Instrument[008]=CourseArrow Instrument[009]=BearingMarker Instrument[010]=TotalFuelGauge Instrument[011]=Slipball Instrument[012]=TurnIndicator Instrument[013]=Tachometer Instrument[014]=ClockMinute Instrument[015]=ClockHour Instrument[016]=FireLight Instrument[017]=Reflection1 Instrument[018]=Reflection2 Instrument[019]=Mirror1 Instrument[020]=Mirror2 Instrument[021]=AoAIndexerSlow Instrument[022]=AoAIndexerOnSpeed Instrument[023]=AoAIndexerFast Instrument[024]=Compass Instrument[025]=MAGNETIC_COMPASS Instrument[026]=MachScale Instrument[027]=ClockSec Instrument[028]=ExhaustTemp Instrument[029]=ClimbDiveIndHoriz remInstrument[030]=ClimbDiveIndVert Instrument[030]=MoveLabsKnob Instrument[031]=MoveFrame remInstrument[033]=MoveCompassNeedle remInstrument[034]=MoveCompass Instrument[032]=MoveFIREWARNINGLIGHT remInstrument[036]=MoveSlipball remInstrument[037]=MoveTurnIndicator remInstrument[038]=MoveClimbDiveIndHoriz remInstrument[039]=MoveTachometer remInstrument[040]=MoveExhaustTemp rem Instrument[039]=MoveExhaustTempKnob rem Instrument[042]=MoveneedleRPMKnob Instrument[033]=MoveRangeCounter Instrument[034]=Movemirror1 Instrument[035]=Movemirror2 Instrument[036]=MovemirrorFrame3 Instrument[037]=MovemirrorFrame4 Instrument[038]=RotateADI Instrument[039]=RotateADI_watermark Instrument[040]=MoveClockSec Instrument[041]=MoveClockMinute Instrument[042]=MoveClockHour Instrument[043]=MoveFIREWARNINGLIGHT Instrument[044]=MoveClimbDiveIndHoriz Instrument[045]=MoveClimbDiveIndVert Instrument[046]=MoveCompassNeedle Instrument[047]=MoveCompass Instrument[048]=MoveClock Instrument[049]=MoveClockKnob Instrument[050]=MoveExhaustTemp Instrument[051]=MoveAoAIndexerSlow Instrument[052]=MoveAoAIndexerOnSpeed Instrument[053]=MoveAoAIndexerFast Quote
+paulopanz Posted July 23, 2009 Posted July 23, 2009 I tried this today and the MiG-15 cockpit would not work. Look up at n.6 post, please. Paul Quote
shiden Posted July 23, 2009 Posted July 23, 2009 I tried this today and the MiG-15 cockpit would not work. Look up at n.6 post, please. Paul Before you 'roll your eyes' I would appreciate it if you actually read my post rather than have a knee-jerk reaction. I applied your fix already and read the thread...thank you. This wasn't the problem. this was in the MiG-15bis_COCKPIT.ini...and I already fixed it for me...but it was in the download: ModelName=MeteorF8_cockpit <---? I changed this to A-4B_Cockpit and it worked again...not sure why it would change like that Quote
+paulopanz Posted July 23, 2009 Posted July 23, 2009 (edited) Before you 'roll your eyes' I would appreciate it if you actually read my post rather than have a knee-jerk reaction. I applied your fix already and read the thread...thank you. This wasn't the problem. this was in the MiG-15bis_COCKPIT.ini...and I already fixed it for me...but it was in the download: ModelName=MeteorF8_cockpit <---? I changed this to A-4B_Cockpit and it worked again...not sure why it would change like that I'm not born english spoken and sometimes I don't understand everything so well. BTW I have the Shusjake new SF-2 Mig-15bis with his (fixed) cockpit and don't use this pit. In that pack there is the MeteorF8_COCKPIT LOD file in cockpit folder. So it woks well without any change in MiG-15bis_COCKPIT.ini. Ciao Paolo Edited July 23, 2009 by paulopanz Quote
shiden Posted July 23, 2009 Posted July 23, 2009 I'm not born english spoken and sometimes I don't understand everything so well. BTW I have the Shusjake new SF-2 Mig-15bis with his (fixed) cockpit and don't use this pit. In that pack there is the MeteorF8_COCKPIT LOD file in cockpit folder. So it woks well without any change in MiG-15bis_COCKPIT.ini. Ciao Paolo it's okay I just didn't want anyone to have trouble with the file with the old game. I need to grab me SF-2 and try the new pit! Quote
+Wrench Posted October 29, 2009 Author Posted October 29, 2009 (edited) It has been just brought to my attention that with the release of SF2:I, there are some small issues with this mod, when attempting to add it to the latest 3W sim. The gunsight tga called out for in the 17 & 19 comes from the F-100D. Now, just like WoI, the Hun and all it's bits don't exist in SF2I. So, if you have any of the Original Series , you can simply extract the F-100D_sight.tga from the Objects.cat, and drop it into the offending aircraft's cockpit folders. If you have a merged install of SF2/V/E/I, it SHOULD work as designed. If not, see above. If that alternative is not readily available, you can revert to the A-4B sight that's included with the package. You will, however need to make some "adjsutments" in the cockpit ini to use the Scooter sight. For the MiG-17, 17F and 19S (and by inference, all variants of the Fresco & Farmer, excepting radar equiped P/PF/PFU/PM, etc). 1st: backup the original cockpit ini from the package by doing a 'save as...' ori-****_cockpit.ini, where *** is the name of the aircraft. Then, reopen the cockpit ini, and copy/paste the following directly OVER the statement that calls for the F-100D gunsight: [GunsightFront] HasGunsight=TRUE GunsightMilSize=50 GunsightName=A-4b_sight.tga LeadComputing=TRUE MinLeadRange=150 MaxLeadRange=600 DefaultLeadRange=300 MaxDepression=125 DefaultDepression=0 I've left the Mil Size sort of small, you can adjust it to fit you visual needs. But I'd reccomend NOT going over 75; it might wind up a bit too big. That should take care of that. As to the statement on upgrading the wingman AI, you'll still need to extract the data inis for the Frescos and Farmers, but they'll not be in the ObjectData006.cat in SF2:I (as it apparently ain't got one!). I don't know WHICH cat they're in, as I don't have SF2I yet, so you'll have to experimentally extract the likely suspects. Oh, and don't forget the 2 little fixes above! wrench kevin stein Edited October 29, 2009 by Wrench Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.