Crusader

For EXTERNAL stations, use only a single line AttachmentPosition= Not multiple positions 01 , 02 ... Add another 2 stations to have 4 total for the inboard positions , then configure them like (e.g.) LeftInboardLeft and LeftInboardRight and assign all 4 one group ID

Gladiator and Hart pics show several German instruments (Airspeed, VSI, turn needle/slip ball) which was Swedish AF specific. CR.42 is all Italian instrumented. Inclusive the gun ammo counters in the center below the compass.

They are in testing... Almost finished with bringing the new weapon panel of the AD/AZ to life .. New FM by baffmeister is very different from the existing FM, much easier to depart if one ignores the RED AoA light and stall audio warning (With FM set to Hard in the Options) Avionics are as good as finalized Still a whole bag of things on the to do list... think I take TWO WEEKS OFF for a break .... LOL..

mue, if I load 3d party cockpits the LodViewer stops functioning if the cockpit is using TGA files larger than 256 px. There are cockpits around which have TGA files of 1024 px or even 2048 px . I resize all TGAs to 256 px or remove them temporary to get the LV working.

He has got a big order for F1 equipment from me ;D

No.

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 :)

File Name: MB-339A cockpit INI update File Submitter: Crusader File Submitted: 02 May 2015 File Category: Jet Cockpits 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 Click here to download this file

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