spankerj

I tried but you cannot change the path as it automatically detects 2.5 folder to install. I don't know if this is true of a clean install as I didn't want to remove 2.5 or ORBX until V3 was fully up and running. I have issues with FSUIPC. It installed fine but I cannot set up the control mappings correctly from within FSUIPC. If I want to assign a controller button for flaps there is no flap option in the dropdown. Same with differential brakes and the same with the axis for main flight controls. I can set up axis using the direct to Fsuipc option but buttons and sending the axis to FS does not have the options for certain controls.

Fsuipc installed without problem. However I have an issue with the assignments for controls. I cannot assign a button for flaps as the offset is not in the dropdown box, same for toe brakes which I want to assign to 2 buttons to the stick but no option. The are no offsets for aileron or elevator axis either and I set them up using direct to Fsuipc instead. It is as if the offset codes changed or something. There are a few new ones in there too.

I probably saw the same twitch stream and he intentionally tried to get a crash and succeeded after maxing everything more or less. What was promising from the stream was the fact that he was showing realtime VAS usage and you could see V3 purging memory along the way. He was running an I5 @ at 3.5Ghz and his framerate was around 5fps when he got it to crash at max settings. In real flight you would not be maxing the settings like he did on that hardware. In essence, yes you can get OOMs in V3 but in reality you probably wont get them as often as we used to.

Yes I think it is the map that is the issue and not the waypoints. Using the GPS on autopilot gets me where I want to go and like you say everything is correct in the other pages. Strange!

I have an issue with the GPS and Navigraph data. All the waypoints, VORS airports etc. move from their correct positions. http://imgur.com/ZdbvFwd The above image shows Northwest England. The Wallasey VOR is a few miles north of where it should be as are the airport labels. The further North I fly the further they will be offset from the correct place. It will only be in the correct place if I fly directly over the waypoint or VOR. If I fly South the offset is to the South of the correct position. It is as if the zoom level is incorrect for the overlay against the map. Someone offline mentioned a possible floating point error but I have no idea what that means. I am running P3D and the phenom and navigraph extention are the latest files. I have also installed the AIRAC cycle 1510. Any ideas?