Jump to content

peteb101

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

0 Neutral

About peteb101

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have updated my V4 320 and 330 and both now connect Ok. The 320 was flyable in CFD, just a couple of minor issues with brakes having a few second delayed release and the throttles no always idling when taxiing but these were present before the update. There were 2 new issue on the 320 as well in that the transponder and radio frequency no longer seem to sync. The 330 however seems to have reverted with the brakes sticking on when not using peddles issue so while it connected to the session ok, we couldn't fly it in CFD at all :-( .
  2. Hi Is your CFD.cfg file, located in Documents/Aerosoft/ correct? It should look something like: 0 3 6900 10 Cheers Pete
  3. Hi Guys, I can see that the guidance is to sort out Pilot roles after connection but is there a way to force connection as PM please? The behaviour we have seen is that whatever you selected before joining a session, the joining pilot always becomes PF. We have also noted that it looks like the settings, including location, come from PF. The reason for asking is that although when starting a flight both planes are clearly in the same location, sometimes it would be useful to join a flight in progess. For example yesterday we had the PM sim crash during descent so PF completed the f
  4. I have done some more testing and I think it might indeed be frames related. I need to test a bit more to be sure but lowering settings does seem to have helped
  5. I have done some more testing and I think it might indeed be frames related. I need to test a bit more to be sure but lowering settings does seem to have helped
  6. My 330 has been fine but since around the last update 1.0.1.0 I am getting a trim bouncing issue. It only does it with the autopilot engaged and seems to be Ok in manual flight. I am not sure if it was the update or the re- install when applying the update or a time coincident that introduced it. I don't use FSUIPC for any key mapping and have deleted the trim keys that I had mapped on the joystick as well as the default keyboard mapping for them, so I have no trim inputs mapped at all (I removed them one by one and it made no difference). I have tried various settings for the trim on
  7. I am having a very similar issue that has only started recently.
  8. Just to add that I dont seem to be able to adjust the trim wheel in the VC with the mouse either so it defiantly seems like is a trim input is coming from somewhere but I'm damned if it can find it! I have even now deleted the default keyboard mapping as well so there are no elevator trim control mapped anywhere! It is also worth noting that my 320 aircraft is not doing this which would suggest that I dont have a dodgy controller or anything like that. Any help or suggesting greatly appreciated. Thanks
  9. I know this tread is about a month old but just wondering if everyone manage to sort it out. My 330 had been fine but since the latest update 1.0.1.0 I am getting a trim bouncing issue. It only does it with auto pilot engaged and doesn't seem to in manual flight. I am not sure if it was the update or the re- install when applying the update that introduced it. I don't use FSUIPC for any key mapping and have deleted the trim keys that I had mapped on the joystick. I have also set the trim setting up in the Init page so am out of ideas if anyone can suggest anything else? Many thank
  10. Hi. Have you tried just starting the APU individually before connecting? Not totally cold and dark I know but would mean most of the the set up could be done together.
  11. Looks like you are sorted now which is good news but it if helps others, here is my folder and cfd.cfg file contents
  12. Me and my friend had the same problem and what we noticed was that if the latest a320 was also installed on the machine then the cfd.cfg file was created by the 320 installer ok but as my friend doesn't own the 320 (only 330) he was not able to to fix it that way. In his case we manually created the file and put the contents of mine is in it and that got him working. We didn't get to the bottom of why it was missing though. In my case there are 4 lines in the cfd.cfg file as below: 0 3 6900 10
  13. File is called cfd.cfg in your root Aerosoft folder, in my case C:\Users\USERNAME\Documents\Aerosoft and it a standard txt file with 4 lines as per below 0 3 6900 10
×
×
  • Create New...