Jump to content

Recommended Posts

Posted

Hey all back with another question that I'm sure has been answered before but search yields no solution...

 

I believe it is a known bug that when placing an INU fix point in the ME, the point will appear somewhere else on the ABRIS in mission. Has anyone figured out how much and in what direction this error typically occurs? Producer's note 4 shows Wags using the ABRIS location to update the INU, but with this bug it is impossible to follow this procedure. Is there a work around?

 

Also, I was messing around with route planning in the ABRIS, and created a new route in it. I wanted the autopilot to follow these routes, so I took the coordinates from the ABRIS and created new waypoints in the PVI 800 using these coordinates. The autopilot then proceded to fly me on a direct heading to what I can only assume was Jamaica or some other island in the caribbean. Maybe it needed a vacation? I did take a long time..... Perhaps this bug is in the ABRIS coordinates in general, and that the map is unreliable coordinate-wise, but accurate when it comes to visual representation, i.e. where there is a bridge on the map, there is a bridge in the real world, but the coordinates do not match the actual coordinates.

 

I know the INU does not accumulate any errors in the game, and the sat consteallation never has poor correlation, so it's entirely procedural to do this, but I'd still like to try it out. I'm bummed that it doesn't work right :(

Posted

^^ not sure sorry, HOWEVER, if I'm not mistaken, Wags or EB has mentioned that the INU fix / innacuracy acumulation may be adressed in the patch (ie. it will start accumulating errors, and become necessary to do the fix .. presumably this will also mean that the INU fix point placement will be fixed in the ME?)

Posted (edited)

There is some coordinate error between the ME map and the world map (used by the ABRIS and F-10 view). However, this should not be so significant as to throw you in a different direction. More likely, your input of the coordinates into the PVI was incorrect.

 

You are correct in that the INS does not currently accumulate error. I don't believe this will be corrected in the 1.0.1 patch. However, you are incorrect in that the satellites never have poor correlation. GPS accuracy does depend on the number, strength, and relative proximity of satellites. For example, when the U.S. is not in your coalition, you have no signal from any NAVSTAR satellites, leaving you with GLONASS. Because there are fewer GLONASS satellites, you are likely to lose LOS to some of them when flying in the mountains, resulting in erroneous GPS readings. For more info on the satellite model, see here:

http://forums.eagle.ru/showpost.php?p=484281&postcount=357

Edited by EvilBivol-1

- EB

[sIGPIC][/sIGPIC]

Nothing is easy. Everything takes much longer.

The Parable of Jane's A-10

Forum Rules

Posted

Good news they are working on this. I really hope they implement the errors soon. I calculated the error between ME and ABRIS. ME point will be 74 degrees and 1100m from the point you place on the ME. It's enough to throw the point way off of your landmark on the ABRIS and make it difficult to identify. The odd thing is, the graphical representation is dead on, so the external targeting system markers are all accurate, just the coordinate readout on the ABRIS is wrong.

 

Perhaps i did enter the coordinates wrong, but the display on the PVI 800 is different than the coordinate readout on the ABRIS, there is a digit missing, so I wasn't sure whether to round up or down. I don't think that would have caused such a significant error, but you never know.

 

We can always hope for a suprise in 1.0.1 :music_whistling:

Posted
Good news they are working on this. I really hope they implement the errors soon. I calculated the error between ME and ABRIS. ME point will be 74 degrees and 1100m from the point you place on the ME. It's enough to throw the point way off of your landmark on the ABRIS and make it difficult to identify. The odd thing is, the graphical representation is dead on, so the external targeting system markers are all accurate, just the coordinate readout on the ABRIS is wrong.

 

Perhaps i did enter the coordinates wrong, but the display on the PVI 800 is different than the coordinate readout on the ABRIS, there is a digit missing, so I wasn't sure whether to round up or down. I don't think that would have caused such a significant error, but you never know.

 

We can always hope for a suprise in 1.0.1 :music_whistling:

 

Are you using WGS84 geoid in ABRIS?

 

Regards!!



Posted
You are correct in that the INS does not currently accumulate error. I don't believe this will be corrected in the 1.0.1 patch.

 

Thats too bad. Any idea of whether this is on the eventual fix list for later patches? Having to INSfix is something I am certainly looking forward to!

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...