Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About kbowman17

  • Rank

Profile Information

  • Gender
  • Location
  1. Hi I have a similar problem to the previous post, but for a different reason. I have the latest UK2000 scenery installed into P3D v4, but after running the DBManager and setting P3D at any of these airports, taxiway, rwy and other info which would be available from the appropriate bgl files is missing from the FSC9 display. I suspect this is because, the latest UK2000 installers allow the scenery content to be installed elsewhere than in the main P3D v4 folder. In my case, I opted to store the content on a separate drive (drive D) on the same computer, to save space on the main drive (C:). Is there any way to get the database manager to look on drive D to pick up the missing information? I have confirmed that scenery from other developers, whether using the old scenery cfg file, or the new add-on.xml method is showing correctly as this content is all stored in the main P3D v4 folder. Thanks Keith P3D v4.0.28.21686 (no hotfix) FSUIPC5.11 I Use FSC in a Network! NO FSC 9.7 (+ hotfix)/DBManager 21-August-2017.hf2 Navigraph 1709 Rev.1 Aerosoft Download Windows 10 64 (Home) 2 Monitors
  2. Hi Volker Perhaps I had not made myself clear enough. I could make the program links, but the icons of these shortcuts had disappeared and so had the icon of FSC.exe, to be replaced by the Windows default ones. After some Internet research on missing icons, I discovered it was a corruption of the Iconcache. The workaround solution was to go into Control panel\Personalisation section and change the Windows DPI to, say, medium (120dpi), then log off. Then log back on, and revert back to the default DPI. Finally log off and back on, and the icons now show the correct FSC9 ones. Thanks again for your help. All works perfectly now. Thanks Keith
  3. Hi Volker Thank you for the help above. It is so long since I had to deal with the more detailed intricacies of FSC9 and the fact that I have used it only with FSX, that I had no idea that the parameter system had been part of the workings of this software. I updated the database manager to 9.6 rev 2, and installed the database for P3D successfully. All seems OK, but one minor issue with using the parameter method is that my icon on the toolbar now uses the default program icon, rather than the specific FSC9 icon. If I do not use the parameter method, the icon used is the correct one! Any thoughts? Thanks Keith
  4. Hi Volker I wonder if you or anyone on the forum can help me with this problem. I have an installation of FSC v9.6 on my main C drive, with FSX SP2 and operating system Windows 7 64 bit. I have just installed the latest P3D v3 onto my D drive, which is working fine. I do not want to convert fully over to P3D yet, but keep both simulators working. Is it possible to alter my setup so that FSC9 works with either simulator. At the moment, I am getting FSC9 recognizing and connecting with P3D without doing any changes whatsoever. However, it is obviously still using the database which is associated with the scenery in FSX, not P3D. Is it possible to get it to use the correct database for the simulator in use, and how would I achieve this (in a simple way if possible). Thanks Keith
  5. Hi Pete Just to finally close the issue, I checked on the logging and particularly the monitoring of offset 07BC, by showing it in the FS window. On pressing the 0 button to send a key Z command and engage the autopilot, no change was seen in the value of this offset, which remained at zero, and certainly there was no change either when pressing the 0 button further times. I think this must clearly show that PMDG are not using a standard approach or toggling this offset in their use of the autopilot in the B777. By the way, your flag programming instructions worked brilliantly and now the whole operation seems to better mimic what I believe happens in the real aircraft. Best wishes Keith
  6. Hi Pete Thank you for the suggestions as to improving the flag technique. I think your improvements will help to improve my operational experience. I accept there is probably no offset that could be tested to see whether the horn is sounding, or the autopilot off as PMDG do a lot of their programming outside of the standard FS program, and as you say these three conditions do not all exist in FSX itself. Unfortunately, I cannot say exactly what Shift + Ctrl + Z does internally to FS, though it obviously does the equivalent of switching off the autopilot, but also switching on the warning horn as the autopilot goes off. Then it also then silences the horn on a second press. Whether this toggles the offset at 07BC I do not know. Anyway thanks once again for your help. I'll now go and put your suggestions into FSUIPC INI and give it a try. Regards Keith
  7. Sorry about the posting problem Pete. I caught a wrong key and posted too early. The offset test was not a red herring. Ideally, I want to use offsets to test the state of the autopilot. If you read the last paragraphs. most of which were missing, you will see more details of this. Thanks Keith
  8. Hi Pete, thanks for the prompt reply. Both Z and Shift + Ctrl + Z are assigned via PMDG B777's own internal key commands menu which is part of the PMDG setup section built into the FMC display. I am guessing that since a lot of the B777 programming is separate from FSX then they decided to split the autopilot commands into two parts. Z and Shift + Ctrl + Z are their default keyboard commands to accomplish autopilot on and autopilot off respectively, though you can obviously assign different keys through their own menu. Regarding the flag setting technique, I'll show you the lines I put in based on you examples in the advanced user guide. They are 0=P3, 0, C1005, 3842 1=CP(F+15,2) 3,0,K90,8 2=CR(F-15,2) 3,0,K90,11 My limited understanding from your guide means that the above do the following. Line 0 toggles the flag based on unused joystick 15 button 2 when joystick 3 (CH Yoke), button 0 is pressed. It then defines the two definitions Z and Shift + Ctrl + Z for button 0 depending on whether the flag is set or not. Thus pressing button 0 (assuming the flag is toggled correctly) switches autopilot on; the next press switches it off. However, due to the programming in the PMDG aircraft, a warning horn then sounds. You will note that line 2 repeats the command, and provided you continue to hold down button 0, after a short pause, (presumably built into the PMDG programming) the horn then also silences. As I said in my first post, the weakness is that the flag would not get toggled if you switched the autopilot on/off using the keyboard directly, and so the next press of the button 0 on the yoke would not do what was expected. Also you have to remember to hold the button down when switching off the autopilot off, otherwise your next press of button 0 does not silence the horn which is still going but puts the autopilot back on. Sorry about the typo, it should have been "D07BC=0". Yes I am trying to test an offset, and using it to define my three definitions for button 0, rather than relying on the flag method. Unfortunately, that is where my knowledge and understanding fall down amongst the theory of bits and bytes and so on. What I would like is to test a suitable offset to find out which of the three conditions is appropriate (I) autopilot off, horn not sounding - define button 0 to switch autopilot on next press of button 0 (ii) autopilot on - define button 0 to switch AP off at next press (iii) autopilot off but horn sounding - switch horn off at next press. As I said earlier, the PMDG as set up by their own keyboard commands menu, requires a Z key equivalent for (i) and Shift + Ctrl + Z for both (ii) and (iii). I hope I have been able to answer your questions adequately. Thanks Keith
  9. Hi I would like to set up a single button on my CH Yoke to operate the Autopilot for the PMDG B777 (which works differently to the standard autopilot), which requires the following action definitions via FSUIPC INI if the defined button is pressed (i) Send the equivalent of a Z key if the autopilot is already off to switch it on, (ii) Send the equivalent of Shift + Ctrl + Z if the autopilot is already on to switch it off .... in this case the autopilot switches off, but a warning horn sounds (iii) Send the equivalent of Shift + Ctrl + Z again on a second button press, if the horn is sounding, to silence it. I can set up a flag on an unused joystick button as described in the Advanced user guide and then use conditional button programming to define two different button definitions, the first to carry out (i) above, and the second (a repeat) to do (ii) and (iii) together. The weakness in this method is that the button for the actions (ii) and (iii) has to be held down to switch off the autopilot and then a second or so later the horn, rather than be two separate button presses. If you forget to hold the button down, only the autopilot switches off, not the horn. Pressing the button again then switches the autopilot back on - not what was wanted. Also, if any of these operations are partly carried out on the keyboard, the flag does not get toggled, so everything is out of step with what you expect to happen when the button is next pressed. Instead, I thought I would try to use offsets to test which of the conditions (i) to (iii) are in effect at any particular time, so that I can then define the three required actions separately independently of how the conditions came about, i.e whether by yoke button or keyboard key presses. Unfortunately, I do not adequately understand offsets and what values these should have for each of these conditions. I noted offset 07BC seems to be linked to the autopilot master switch, but cannot seem to get anywhere with (ii) and (iii). I wonder if the complexity of this aircraft means that standard offsets do not apply anyway. Also, there are three conditions to test, not just whether the autopilot is on or off. The line 0=D0&BC=0 P3, 0, K90, 8, put into the B777 button definitions section seems to work to carry out (i) by setting my joystick 3 (CH Yoke), button 0 to emulate the Z key press, but I have got nowhere with suitable lines for (ii) and (iii). Any help you can give would be appreciated, perhaps even a totally different approach? Thanks Keith
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.