zaelu

But first coordinates are always wrong... wouldn't your alignment be off then?

Makes sense jojo. The error I was doing was either not to select to launch all 4 bombs or to space them which meant not all at once release. I tried again once today and after I entered the F10 Map data instead of ME data (basically the angle was not 340° but 339°) I managed to bomb with all 4 Mk82s pretty close (all enemies survived...). If it's realistic behavior I can live with it. Next time I take MK20s. edit I mean this close :D

I know but... :)

Now is clear :thumbup: Thanks!

So the small random error in 00 Latitude/Longitude coordinates we have at each cold start that before alignment we need to check them and correct them is intended, right?

I observed that using ZBI in conjunction with IP makes the diamond to get low. However the effect is the same. BUD is way off. I placed the Waypoint/IP to Groom Lake airfield and the BAD/targets at the end of the runway exactly 3 miles off and only 30 feet lower. but the BAD was way way way off. I killed the Shilka with the guns because dark side took over :D. Also. If you carry 4 bombs... how do you do multiple passes on same BAD? Currently after first release you need to take it from beginning.

Normally you have a millitary map :D @Zeus Just thinking... What if the errors we see with the maps are related to Elevation? What if we choose a waypoint situated on flat surface? Would the errors disappear?

He placed the waypoint on the TACAN Antena on that mountain so it was easy to spot. Without bombs you do an OBL update.

1. From the F10 map. You place the mouse cursor above the point and read on the top left corner the coordinates/elevation. Preferable set your map to show imperial units. 2. You already know it because it is one of your waypoints and should be situated on an object from scenery (A bridge a tower, etc). This is part of mission preparation. In the example made by Zeus it was the Antena of the TACAN station near Boulder City. He placed the diamond near it and not on top because there are some bugs about F10 map - Mission editor Map coordinates translation... I think.

This look to be the case even in INS bombing tutorial made by Zeus. He doesn't update on the building but rather beside it. Maybe for now this is a work around till the small bugs are fixed.

I thought so. So this formulation in this thread with minimum x, emergency y is not 100% correct. Emergency can be 1 gram of fuel. Because that means it was an emergency and the fuel was used. It's useless if you reached the so called Emergency value but you still can't land because of the emergency. Say one gear won't come out while the others are stuck outside... in bad weather... with some bombs that won't jettison for some reason... battle damage or something.

Zeus I observed something. After I modified my mission to start the plane Hot on ramp not Cold rampstart, the starting coordinates were far far better than before. The INS was aligned already obviously. Then when I arrived at IP to update my diamond was not wrong at the top but down in the HUD. Also although the cross was off after I did the update the BAD was pretty much dead on target. (I heave two groups, one on the bridge, the other where the cross is) The single GBU16 bomb fell badly though, way over the target. Also once during the attack run the steering cues were glitching telling me abruptly to bank 90°.

What happens if you come to land with a lot less fuel? Lets say your engine dies after you stopped the landing run scenario? Is the plane harder to balance? 1600lbs of fuel seems to me a lot of fuel and if is mandatory to come back with it why not use that space or weight for other stuff?

So Mirage is modeled after F15? Where did CptSmiley said it's not a bug because F15 does supercruise "with 2 bags"? or you mean "it might be realistic after some stories?"

Is this the reason the Diamond stays up? Does this modifies in any way the precision of Updating? My solution was to move the targets at exactly 6 n-miles. Then I observed that the Mission editor map and F10 Map had a difference of one degree when measuring the line from BUT to BAD

I think you should send your resume to Belsimtek ;)

+2 And put an explanation to that LHA abbreviation...

To all that think a heavy lifter is useless in DCS... you don't imagine the possibilities: You just keep your engines spooled for when the sh... hits the fan(s)

Chinook because awesome!

I tried several times for now. It's not working. - IP position is not updating on HUD - the cross remain off and most importantly: it's off always in other place. More than that. Coordinates in Mission Editor differ from F10 map in multiplayer by a bit, especially the North coordinates. Basically when I do the INS alignment on the ground I always have to enter different coordinates (a tiny bit different) although I always spawn in the same place. - The BAD position is also always in some other place but never on the target. - Bombs impacts are also way off. Funny thing. I moved the targets from the bridge to the road that goes from the dam towards Boulder City (not far, same 6 miles off from IP but 2 degrees North) and when I released my bombs once they fell on the bridge where the targets used to be. LOL. I modified the mission a bit so now there are 2 sets of targets. One on the bridge and one in the new position. I placed also a soldier to be FAC in case someone wants to test the lasing. There are 2 MIrages to pick. One with Mk82s the other with one single GBU16 bomb. The offset from WP02/IP are like this: First group 6nm, 77°, -2164feet altitude difference (actual altitude of targets: 1391feet) Second group 6nm, 79°, -2000feet difference (actual altitude of targets is : 1557feet on bridge, 709feet the ground bellow) INS.miz

Thank you jojo. It helps. Some more questions though :). When you set up the BAD (on the ground... at least I do it on the ground) you need to press VAL after you entered the offset distance/heading and altitude? Also just to clarify. INS update is for OBL and IP update? NAV update is for overflight update? OBL works now? (at least in 2.0?) - @Frederf Nice findings but a lot of work and the game should do it properly I think...

That skin is awesome!

you can brake gently before 110 and it will lower somehow more slowly the nose.

Yup. I tried again same results but now I understood what that steering cue wants from me. I see the release cue and I press and hold trigger before it reaches the FPM and still the bomb falls way after the target. Notes: -I really don't know what is the correct name of the button for TAS position update. I know is trivial but seriously... this shouldn't be let like this. There are 2 buttons for NAV and INS updating and one for radar locking yet the instructions say that RADAR Update should be pressed. -GBU 16 bombs are not released all even if I programm them to do so. Is this because they are laser bombs? -the BAD setting is not clear (again too much uncertainty) if you need to press VAL after you set its values on the ground. Instructions say that you should not press VAL after the IP position update. I am not sure if as a result of this all waypoints share same BAD. Meaning I set BAD for WP2 and it I switch Dest to WP3 still has the same values for BAD. Or are they the same untill I set new ones? Because I set values just for WP2. - cross of the IP does not move after update. That's known I think now - cross of the target is off by some good distance too. Bombs are not falling there anyway. I will try tomorrow with Snake Eyes.

Target elevation was not zero. The cross looket to be on the hill not under the bridge. At least I did entered it correctly the "delta alt" and it showed some hundreds of feet in PCN after I subtracted the difference (the IP is high on that hill). But it was on that bridge... maybe that was the little problem? Maybe in the end I got decent result after all the unknowns? Let me try one more time. I attached the mission Zeus. I played it in single player so no record and also I deleted the movie after I took the screenshots because it was big. INS.miz