Check you have the correct bullseye loaded, if not sure, load it directly from the cam/tac file.
Latest posts made by Monster
-
RE: F4AWACS Just an other question regarding AI Spy
-
RE: Shared Memory and Current Position
Here’s a quick example in C++ to convert these values to coordinates. You need the coordinates of the SW corner of the theater you are currently in. There are some tools to obtain this information (e.g. TerrainEditor). For default Korea, the values are in the code.
#include <math.h> #define FT_PER_DEGREE 365221.8846f #define RTD 57.2957795f //Radians to Degrees #define DTR 0.01745329f //Degrees to Radians #define EARTH_RADIUS_FEET 20925700f float StartCoord_Lat = 33.84375; //The Latitude of the SW corner of the theater in Degrees. Stored in MAP theater file float StartCoord_Long = 123; //The Longitude of the SW corner of the theater in Degrees. Stored in MAP theater file float ownship_North = 0; //Your input value in feet float ownship_East = 0; //Your input value in feet float cosLat = 0; //Temporary var float outCoordLat = 0; //Output Latitude float outCoordLong = 0; //Output Longitude //Latitude in Radians outCoordLat = ( StartCoord_Lat * FT_PER_DEGREE + ownship_North ) / EARTH_RADIUS_FEET //Cosine of Latitude cosLat = cos( outCoordLat ) //Longitude in Radians outCoordLong = ( ( StartCoord_Long * DTR * EARTH_RADIUS_FEET * cosLat ) + ownship_East ) / ( EARTH_RADIUS_FEET * cosLat ) //Converting to Degrees outCoordLat = outCoordLat * RTD outCoordLong = outCoordLong * RTD</math.h>
-
RE: HydPressureA/B incohérent values from FlightData.h …
You’re casting the same memory region to two different kind of variables, so of course you’ll get back values that don’t make sense.
The problem is with your OpenFileMapping call that I assume is something like this:
gSharedMemHandle=OpenFileMapping(FILE_MAP_READ, FALSE, "FalconSharedMemoryArea")
You should add another handle for the second shared memory region (with proper declaration of the gSharedMemHandle2 variable of course):
gSharedMemHandle2=OpenFileMapping(FILE_MAP_READ, FALSE, "FalconSharedMemoryArea2")
Then, you can retrieve the data:
FlightData *flightData = MapViewOfFile(gSharedMemHandle, FILE_MAP_READ, 0, 0, 0); FlightData2 *flightData2 = MapViewOfFile(gSharedMemHandle2, FILE_MAP_READ, 0, 0, 0); hydPressureA = flightData2->hydPressureA; hydPressureB = flightData2->hydPressureB;
*Edit: I suggest using the Flightdata.h file that comes with the BMS install, as it is the latest and you can be sure it will be working. This file should be under the Tools\SharedMem folder.
-
RE: Monster Terrain tool
Hi,
just installed the Tool (V3.1.1) but i am not able start it
First appears a message regarding Autoupdateno matter what i choose , i always get this:
Which file is missing ?
Maybe this will help
http://docs.sakgiok.gr/manuals:terraineditor:faq#i_have_a_runtime_error_starting_the_program_and_i_m_stuck_in_v311_since_i_cannot_update -
RE: Online Squadron Collection v2 is out
As I’ve explained before, AISPY is a “hack”, it just reads raw memory and tries to get AI aircraft data. Usually, there are two returns of the same contact (very close to each other) because that’s what exists in memory.
I could have implemented a filter to eliminate one, by using the callsign and the position (e.g. if we already have a contact named Cowboy1 within 3nm of the new one, drop it).
The problem is with contacts named “Bandit”. Since there are usually a lot of them and there is no other way to identify the contact, this method wouldn’t work. I just chose to have AISPY sent (almost) everything and let the player decide is a contact is valid or not. -
RE: Online Squadron Collection v2 is out
Very nice points, I’ll see what I can do about it.
-
RE: F4Awacs & 4.33.u1
AISpy should be working fine with BMS 433U1, as long as BMS is in the map screen and not 3D.
-
RE: Online Squadron Collection v2 is out
I have some thoughts about some things that could be improved, but unfortunately, I really don’t have so much free time to work on it right now.
Do you have anything specific in mind?
-
RE: Monster Terrain tool
I just found a bug that might produce the errors you’re getting.
Please, open TE.ini (in program’s folder) with a text editor and make sure the line DEBUG has the value of 0 and not something else. It’s under section [SYSTEM].
If not, change it to 0 and try again. It should be 0 anyway since debug should be used for short periods of time, because the Debug.txt that is produced gets very big over time. If the value is not 0, you should delete Debug.txt as well to save disk space.