Crusader

Thats the way it is. Each mesh in the cockpit ( for a light or indicator/needle of any type) can only be used one time, not for multiple functions or tied to multiple stations. Thats what makes building modern cockpits with MFDs such a nightmare (well.. depends on the individual modders patience..), they have hundreds of single mesh nodes for lights to cover all possibilities for the stores ...

Is the radar modeled pointing the correct way, i.e. forward ? Iraq had several Lupo's on order, some were build but never delivered..

mue, any chance for another addition to this tool... ? Could you make it visualize the CollisionPoints .. then its easier to check and edit them :)

Some functions i changed or modified in the 21bis cockpit They should generally be applicable/work for the M, SM, MF pits too ... - the gunsight has a red needle which presently works as a G-Meter I've changed it to use the proper radar range function Two scales ( the two middle ones / 2nd + 3rd ) are used indicating 2000 to 9000 meters (3rd - middle lower scale) indicating 400 to 2000 meters (2nd - middle upper scale ) - the old mod to hide the Camera which is in the way during air to air gunnery using the HUD Mode function with Light movment, where position is either 0.0 (OFF) or 1.0 (ON) value are the 3 HUD Modes ( 0 = NAV/CAGED sight, 1 = AA, 2 = AG ) my data below is set to hide the camera in AA and AG , modify to your liking.. - the stick, which can be in the way to read some instruments using same setup method as for the camera, its set up to be OFF in NAV , modify to your liking.. I use the NodeName=MandoRefl for it ... If its preferred to hide camera and stick permanently, the easy way is this: Type=INACTIVE NodeName=Camara Type=INACTIVE NodeName=MandoRefl instead of Type and NodeName in the data below, the Movment and Set values are not required make sure the Instrument number are in correct sequential order after copy/paste the new data! Instrument[120]=HideSightCamera Instrument[121]=HideStick Instrument[122]=GunsightRadarRange [HideSightCamera] Type=HUD_MODE_INDIDCATOR NodeName=Camara MovementType=LIGHT Set[01].Position=1.0 Set[01].Value=0 Set[02].Position=0.0 Set[02].Value=1 Set[03].Position=0.0 Set[03].Value=2 [HideStick] Type=HUD_MODE_INDIDCATOR NodeName=MandoRefl MovementType=LIGHT Set[01].Position=0.0 Set[01].Value=0 Set[02].Position=1.0 Set[02].Value=1 Set[03].Position=1.0 Set[03].Value=2 [GunsightRadarRange] Type=RADAR_TARGET_RANGE NodeName=AgujaBB MovementType=ROTATION_Z ValueUnit=METERS Set[01].Position=-21.0 Set[01].Value=400 Set[02].Position=21.0 Set[02].Value=2000 // 2000 to 9000 m scale Set[03].Position=-15.75 Set[03].Value=2001 Set[04].Position=21.0 Set[04].Value=9000 Other tweaks are (copy/paste and replace the complete sections): total fuel quantity unit fixed [Gas] Type=TOTAL_FUEL_QUANTITY_INDICATOR NodeName=Combustible MovementType=ROTATION_Z ValueUnit=KG Set[01].Position=-76 Set[01].Value=0.0 Set[02].Position=256 Set[02].Value=3124 all fuel warrning lights units+quantity fixed [LuzPanelM] Type=TOTAL_FUEL_QUANTITY_INDICATOR NodeName=LuzPanelM MovementType=light ValueUnit=KG Set[01].Position=1.0 Set[01].Value=351.45 //450.0 Set[02].Position=0.0 Set[02].Value=351.46 //450.1 [LuzPanelO] Type=EXTERNAL_FUEL_QUANTITY_INDICATOR NodeName=LuzPanelO MovementType=light ValueUnit=KG Set[01].Position=1.0 Set[01].Value=0.0 Set[02].Position=0.0 Set[02].Value=1.0 [LuzPanelP] Type=INETERNAL_FUEL_QUANTITY_INDICATOR NodeName=LuzPanelP MovementType=light ValueUnit=KG Set[01].Position=1.0 Set[01].Value=745.855 //955.0 Set[02].Position=0.0 Set[02].Value=745.856 //955.1 [LuzPanelQ] Type=INETERNAL_FUEL_QUANTITY_INDICATOR NodeName=LuzPanelQ MovementType=light ValueUnit=KG Set[01].Position=1.0 Set[01].Value=480.315 //615.0 Set[02].Position=0.0 Set[02].Value=480.316 //615.1 [LuzPanelR] Type=INETERNAL_FUEL_QUANTITY_INDICATOR NodeName=LuzPanelR MovementType=light ValueUnit=KG Set[01].Position=1.0 Set[01].Value=0.0 Set[02].Position=0.0 Set[02].Value=0.1 radar altimeter warning light unit fix [Emergencia4] Type=RADAR_ALTIMETER NodeName=Emergencia4 MovementType=light ValueUnit=METERS Set[01].Position=1.0 Set[01].Value=200.0 Set[02].Position=0.0 Set[02].Value=200.10 slipball direction reversed [slip] Type=SIDESLIP_VELOCITY_INDICATOR NodeName=Slip MovementType=ROTATION_Z ValueUnit=DEG Set[01].Position=5.0 Set[01].Value=-3.0 Set[02].Position=-5.0 Set[02].Value=3.0 ... [slip2] Type=SIDESLIP_VELOCITY_INDICATOR NodeName=Slip2 MovementType=ROTATION_Z ValueUnit=DEG Set[01].Position=5.0 Set[01].Value=-3.0 Set[02].Position=-5.0 Set[02].Value=3.0

View File MB-339A cockpit INI update Updated cockpit ini for the ID(io)T Team MB-339A available here http://combatace.com/files/file/12063-aermacchi-mb-339a-for-sf2/ and http://combatace.com/files/file/11304-aermacchi-mb-339a-pan/ Updated instruments/functions are - position of the cockpit (minor tweak) - gunsight, added gyro function - fuelflow gauges, show correct consumption - station lights now show correct selected stations - g-meter, new calibration, 1 G at level flight - mach-indicator new calibration, shows correct mach at all altitudes - airspeed-knots new calibration, - variometer, new calibration, now shows correct vertical velocity Submitter Crusader Submitted 05/02/2015 Category Jet Cockpits

From my notes, dont remember by who :

Theres a great new book released on this topic, covering both the air and ground war. EDIT: On the Ethiopia vs Somalia part, I mean..

Check the data ini engine sections if they have the pressure and temperature entries ...

blurry radar.. thats the 10 nm scale, once you select 20 or 40 + nm its smoother ...

Maybe ask in the Spanish forum , theres pics of the boat in this post.. http://combatace.com/topic/37391-wing-over-patagonia/page-9?do=findComment&comment=439400

Take a look in this thread: http://combatace.com/topic/24930-lcos-ccip/?do=findComment&comment=125123

If you are based so far from the frontline, fly a hi-lo-hi profile. Use AB only when really needed for TO (you can do without on large bases with long rwys) then climb as fast as possible in mil power to 25000 - 30000 ft Up there you can cruise at Mach 0.8-0.9 with low throttle setting without burning much fuel Throttle back to 0 for the let-down to the target area, depending on the cruise alt that can be done from 50+ km out Same procedure for the return leg Just be careful, if you know that Blue has HAWK and NIKE, its a good idea to go low level a bit sooner on ingress... ~

It was added for tanks in First Eagles, iirc

The RangeUnit entry is missing add below RadarType line : RangeUnit=KM And that stuff, i took it from a MiG-23MF data RadarSearchFreq=10.5 RadarTrackFreq=10.5 RadarMissileGuidanceFreq=10.5 RadarSearchCW=FALSE RadarTrackCW=FALSE RadarMissileGuidanceCW=TRUE add above the RWR related entries

Probably the DetectSystem section in the data ini, missing some entry/data for the radar copy/paste that section here ..

Very nice All prospective F1EQ pilots should get some flight time in the Mongol Because the F1EQ HUD and Instruments use the metric system ....

M5F convoy attack TBA M5D 1977 off to Siwa Oasis Local snackbar on fire ?! ...

And for Component meshes, the meshname in the data must be correct to start with or the hitbox is not visualized by the LODviewer

All the cash gone, new aircraft (with cool camo) but no seats ...

The updates are underway .. :)

I hope for potential KSA, Iraq and Iran skins...

Slowly but surely... WIP pics, not final lods and loadouts! This AZ/AD pilot has IR missile selected, radar lock, range less than 3600 meters, closure rate of 10 knots but is inside minimum missile range! And some EQs after some action vs F-4's...

Reminds me of the Iraqi Foxbat with the BVP-50-60 mounted on the wings and decoying several AIM-9M (2, iirc) and a 7M Maybe more tweaking of game L and M SW's is in order ...

The La-11 technical description has several graphs for max speed vs altitude and engine stuff But I cant read russian, only a few parts where i exactly know what it is about..