dtmdragon

The seat and pilot disappear as the stock TW ejection effect and camera angle are from the pilots perspective after ejecting. Hence you are the pilot sitting on the seat. That is why you see the aircraft and separated canopy disappear off below you.

Try this, provided the seat node name is correct the seat will disappear with the canopy when you eject. [XXX] SystemName=Pilot SystemName=EjectionSeat [Pilot] SystemType=PILOT_COCKPIT Position=0.0,3.10,0.9 PilotModelName=HGU26AW.lod SeatModelName= SeatPosition= MinExtentPosition=-0.25,2.86,-0.22 MaxExtentPosition= 0.25,3.87, 1.00 CanopyNodeName=Canopy_Main [EjectionSeat] SystemType=PILOT_COCKPIT Position=0.0,0.0,0.0 PilotModelName=FakePilot SeatModelName= SeatPosition= SeatID=2 Mass=0 MinExtentPosition= MaxExtentPosition= CanopyNodeName=seat_frame

F-111D had a HUD and CCIP bombing mode. Get it here: Or here: (Ignore the what if Israeli skin)

Out of curiosity how do you know?

Ah got you now, shame as thought I had found a fix

Any more detailed info on how to get this to work guys? I have tried with a HUD shoot/ in range cue for the F-15C but it only appears once the target is at the 'break x' range. So the 'AwayImageFilename=' tga image is not showing up when the radar target is in range of the selected missile.

Nuke Effects-Modified.7z

I have the KT030 and MT030 nuclear effects, all of the KTxxx and MTxxx infact as a package. I'm not home till tomorrow but will upload them here when I can.

Please share it you get your hands on, what an interesting read I bet!

Use mules lod viewer in the downloads section

Bump ?

First make sure the figures in BRU-55 data.ini you have can carry the weight and dimensions of the 2x JDAM in question. A 2br or ter will not carry a GPS guided weapon (EOGB) if loaded at the loadout screen. However if loaded via the loadout.ini file and not changed at the loadout screen it will. Eg: Loadout[03].WeaponType=GBU-38 Loadout[03].Quantity=2 Loadout[03].RackType=BRU-55

Re sizing the tracer textures 50% or 25% smaller can go long way to help this

Out of curiosity what do you think it would be worth market rate if he were to sell it to CA?

For a gunpod you do don't need change a thing just hit the 'next gun group' key and it will toggle between just the gunpod, just the internal gun or both together (default). Gungroup comes into it when you have 4 of the same internal gun as on the F-8 and want to toggle between being able to fire just two at a time.

Apologies as you are 100% right this changes between gun pod only, internal gun only or both together. It even worked on the F-8 to switch from firing all 4 cannons to just two at a time as they did in real life to conserve ammo. I see there is a GunGroup= entry that can be used with each internal gun, just give it a group number. How did I not know this!!! And of course it allows to to switch between cannons and/ or machine guns on WWII fighters... mind blown lol

The only work around is to change the gun fire command for your internal gun to "InputName=Fire_Secondary_Gun" in the data.ini and map the secondary gun fire button. Downside is the AI wingmen wont use/fire a secondary gun.

I just flew a few tests in ODS with the GAU-13 gun accuracy down to 10% I would consider the results below an area weapon. Enlarge the screenshots and look at the spread of fire hitting the ground. Each one is a 1-1.5 second burst. My ODS F-16A Block 10 with improved textures, cockpit, avionics, loadouts, effects and updated data.ini (to viper team standards)

Try adjusting the 'Accuracy= ' value of the actual gun [GunData001] TypeName=30MM_GAU13 FullName=30mm GAU-13/A Cannon Caliber=30.000000 ROF=2400.000000 MuzzleVel=1030.000000 AmmoWt=0.360000 WarheadWt=0.036000 CartridgeWt=0.739000 Reliability=100.000000 Accuracy=50.000000 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Try 25? or even lower and see what happens. AddLight=TRUE MaxLightRange=1200.000000 FireColor=0.500000,0.450000,0.320000 GunFireEffect=30mmFireEffect GunFireSound=Vulcan EffectClassName=30mmEffects EffectTime=0.100000 TracerTexture= <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< You should remove the tracer as USAF 30mm loads for the A-10 don't use tracer so I'm sure it was the same for the GPU-5 TracerSize=0.000000 TracerDistFactor=0.000000 TracerLength=0.000000 MaxVisibleDist=0.000000 MaxStreakVisibleDist=0.000000 //TracerTexture=Tracer.tga //TracerSize=0.200000 //TracerDistFactor=0.002000 //TracerLength=0.018000 //MaxVisibleDist=4000.000000 //MaxStreakVisibleDist=1000.000000 TimeFuzed=FALSE

Like so... P.s. the painted over squadron tail fin markings are from VF-24 as in the story on the first post.

Still not a bad idea for a skin...

No but it sounds like you haven't put the cockpit folder with the modified .tga files in the right place

View File Mirage III & Nesher Gun Sight Fix. Mirage III and Nesher Gun Sight Fix. This mod corrects the Stock Third Wire Gun Sights for the Mirage IIICJ Shahak, Mirage IIICJ Shahak (71), Nesher and as a bonus the DLC 17 RAAF Mirage fighters. I recently read the Osprey book Israeli 'Mirage and Nesher Aces' and 'Mirage III vs Mig-21 Six Day War 1967.' Both books are full of gun camera images of Israeli Mirage IIICJ and Nesher fighters killing MIGs. From these I realised Third Wire has made an error on all the Mirage gun sights by aligning the (horizontally elongated) aircraft reference cross with the gun bore-sight and thus the gun piper. In the Nesher and Mirage IIIO that leaves the actual gun bore-sight cross sitting above the gun piper doing nothing. This mod corrects the position and alignment of the aircraft reference cross, gun piper and gun bore-sight cross (Nesher and Mirage IIIO). This correction should be applied to any other version of Mirage III, Mirage 5, Nesher or Dagger you have that uses a Third Wire Mirage cockpit and/ or Mirage gun sight. CombatAce fair use agreement applies. Cheers, Dan. Submitter dtmdragon Submitted 05/03/2019 Category Avionics

Actually I have a better idea. Have invisible tip tanks that can be jettisoned like I said above but make the 3d model of the tip tanks part of the aircraft LOD. Set up the node name of the tip tank as the pylon 'ModelNodeName=' for the weapon station carrying that tip tank. Set up the 'PylonMass=' and PylonDragArea=' vales with the figures for what the tip tank would be. Thus when you hit the jettison drop tanks key the 'invisible' drop tanks with the fuel will be gone but the 3d model of the tip tanks (as the pylon that was holding the 'invisible' drop tanks) will remain on the aircraft. This method doesn't use multiple loadout stations etc