Jump to content
The simFlight Network Forums

Delvos

Members
  • Posts

    153
  • Joined

  • Last visited

Everything posted by Delvos

  1. Oh yes my friend; thx for reminding me; WM_NCPAINT - once i knew this and now i'll never forget:-) Now it works - as well as the Linkage modification depending on fs' version... Best regards,
  2. Good morning Pete... i've got one question concerning loadable modules: through the years i wrote some modules to be loaded into FS and they do they work ver well. The only thing that makes my a little bit unhappy is the gauge header. I used the gauge header for FS 8. So my modules are loaded into FS2002 as well as into FS9, but - of course - i have to make entry in the [OLDMODULES] section of my FS9 config file or say 'Yes' if FS9 wants a confirmation for loading third party software. How can i avoid this? Is there any "independent gauge header" or some thing else? What is going wrong, if i want to add a menu item to an existing menu with AppendMenu? After retrieving the handle of the desired submenu, i use AppendMenu menu function to add a new item passing the submenu's handle as parameter, MF_STRING and its menutext, AppendMenu returns true, after this i call DrawMenuBar which alo returns true, but the added item is not visible... I also tried InsertMenuItem but did not have any success. What's going wrong? Thy in advance, greeting from EDDL and best regards,
  3. Yes, i understand - i remember the notes when RTFM:-) and saw that effect when calibrating joysticks - different IN-values although i did not move the stick... Regards and thy,
  4. Hello Pete, everything is working well now; i've installed the latest FSUIPC version, assigned my axes and calibrated them via FSUIPC. The problem concerning my flap lever was, that i had to check 'Reverse':-) After this i could finish calibrating my flap lever... The axis assignment still works a little bit strange; when pressing the 'Rescan' button once (no movement of any device!), FSUIPC shows randomly(?) one of my joysticks that are already known to FSUIPC and an 'assignment' that is really not assigned to this stick, but to another one. Pressing 'Rescan' again, another joystick is shown and another random action. After pressing 'Rescan' again, all fields are cleared and the command 'Move Lever' is shown and i can move my desired joystick to be recognized... A little bit strange - but can be worked around as described... Regards,
  5. Hi Pete and thx for the fast reply! Well, when i'm back @home i will install the 3.918 version and try again. I don't think i misunderstood what this is for:-) In fact i really need the manually set detents, so i have to calibrate each of the notches individually because of the non-unique notch-distances on a 737 flaps lever:-) OK, now i understand the difference between IN and OUT values; initially i have only #0,#1 and #2 values set - so FSUIPC will only send these three values to FS until the intermediate notches are defined - logical, of course:-) Besides this - when using flap detentes calibration, the correct axis assignment for my flap lever would be: Flaps - via FSUIPC calibration, am i right? BTW: i would be glad if you'd like to visit my homecockpit-site - http://www.b737sim.de - and leave a view words in my guestbook:-) Regards,
  6. Good morning Pete... i have big problems assigning/calibrating joystick axes via FSUIPC 3.90. First i deleted all axes assingments in FS (FS9.1) and my FSUIPC.INI (not write-protected:-) doesn't have any joystick/button assignsments either, so everything is clean. First i wanted to assign an axis as a flap lever with detentes, so i went to the axis assignment page, moved my desired axis which was succesfully recognized and assigned it to 'Flaps' / send via FSUIPC calibration. I went to the joystick calibration page 6, pressed 'Set' and 'Dt' and tried to set the detentes - but the IN/OUT values did not change. So i went back to the assignment page, rescanned my axis and saw that my previous assignment was not stored. I reassigned it, pressed OK and re-entered FSUIPC to check. No assignment stored. The next attempt was successful and i found out that i have to assign twice(!) until FSUIPC stored my assignment! Back to the joystick calibration page 6 i wanted to set my flap detentes now... Pressed the Set button, the Dt button and moved the lever to the flap-up position to set the #0 and #2 values first. Moving the lever i saw that the IN values changed in a correct way from 16383 to -16384 whereas the OUT values displayed only show 3 different values when moving the lever from UP to DOWN: 16383, -130 and -16384. Number of flap detentes is set to 9 (B737) and the lever i use is the SAITEK Pro Flight TQ. Everything is running under Windows XP SP3... Can you tell me what's going wrong? Best regards,
  7. Good morning Pete... Well, concering the IN and OUT values - they seem to be correct, but when pressing the 'SET' buttons they only appear in the labels below the appropriate 'SET' button i pressed when i try to set the minimum/maximum values and flap #1 value. The other values for positions #2-#7 do not appear in the label below the center 'SET' button when the lever is moved and 'SET' was pressed... So i edited FSUIPC.INI manually while FSUIPC was opened, entered the IN values shown when calibrating the lever to FSUIPC.INI and pressed the 'Reload' button. Now i could see the manually entered values for all notches when scrolling with the trim wheel and - it worked! Another strange phenomenon - i do not know if it is important in this case:-) - is: when i want to assign the axes of my TQ using the 'Axis Assignment' tab and f.e. try to assign my left lever, the 'Axis Assignment' always shows the values and settings of my middle or right lever. I have to rescan once or twice to get the correct axis! This concerns every lever on my TQ... Note: the TQ axes are not assigned in FS itself, only in FSUIUPC! Regards,
  8. Well Pete - it's done! But not in the usual way - i did everything as descrobed before, but afterwards i had to edit FSUIPC.INI manually and change the values of FlapStarts and FlapsEnds by hand! "Scanning" and pressing 'set' gave the same results, i send you in my last entry of this thread - heaven knows why... After editing the wring values by hand, everything worked as desired... Regrads,
  9. Well Pete, now i tried to use reverse values - no success:-( The problem remains during setting the values... The FlapsUp position is now -16383 and the FlapsDown position is 16384. But - when adjusting the detent values - done as described before - the values stored in FSUIPC.INI are as follows: FlapsSetControl=0 FlapDetents=Yes Flaps=0,16380/16 FlapStarts=-16384,-13952,16381,16384,16384,16384,16384,16384,16384 FlapEnds=-16383,16380,16383,16383,16383,16383,16383,16383,16384 Note: when moving the flaps lever to the flaps-up position, flaps are moved to position #1 (not #0!); when moving the lever to flaps-down, the flaps are moved to the full flaps-down position - but moving the lever to the notches in between -> nothing happens! Regards,
  10. THX Pete! I'll check it out this evening and tell you:-) Regards,
  11. Hi Pete and thx for your fast reply... I'll try to describe a little more detailed what I did; mabe you're able to find out where I was mistaken:-) -after the initial settings, FSUIPC shows me exactly the same as the image on pg 47 of the user guide, with three 'set' buttons... -i moved my lever into the flaps up position and pressed 'set' under the left heading number (#0)... -i moved my lever into the flaps down position and pressed 'set' under the right heading number (#2)... -i moved my lever to the beginning of the flaps 1 range and pressed 'set' under center heading number (currently #1)... -i moved my lever to the end of the flaps 1 range and pressed 'set' again under center heading number (currently #1)... -incremented the spin control, so center heading number is now #2... -i repeated the last three lines until center heading number #7 was done... -finally i pressed 'OK'... Maybe the problem is the reversing - i remember a positive value (16380?) on flap up and a negative value (-16380?) on flap down positions. If so, do i have to check 'Rev' before doing anything else? Best regards,
  12. Dear Pete... the last evening i spent some hours trying to calibrate my flaps with specific detentes with no success:-( . I'm using FS 9.1 with WinXP SP3, registered FSUIPC version 3.85 and the flaps should be moved with the right lever of my saitek tq (r-axis). First i removed the former axis assignment (elev. trim) and set the new axis assignment to 'Flaps' and 'Send direct to FSUIPC calibration' - so far so good:-) Next i went to the 'Joystick calibration' tab and selected page 6, pressed the 'Reset'-button, 'Dt' & 'Cl' buttons and continued as described on pages 46-48 in the FSUIPC user guide. Everything worked as shown in the guide with one exception: after setting minimum and maximum positions, i continued with setting #1 flag; this worked - i pressed 'set' once at the beginning of the #1 range and once at the end of #1 range. Then i selected #2 on th spin control and moved the lever to the beginning of the #2 range and pressed 'set' once again, but the current range of my lever was not stored! This continued for all the other ranges... After pressing OK i took a look at FSUIPC.INI and saw my changes; i saw FlapStarts and FlapEnds; the ranges for min, max and #1 seemed to be ok, but the other ranges were all the same! In FS i tested the flap lever; min and max were ok, #1 was reached - but not the other positions. I closed FS and entered the ranges in FSUIPC.INI manually and restarted FS, i opened FSUIPC and saw that all my settings were gone... I made this test using FS default-737... What's going wrong? THX in advance... Best regards,
  13. Mornin' Captains... does anybody know how to use the Flight Simulator Skins for Dialogboxes etc. from within my own Addon-Software? Checking out with Spy++ if they use any specific class did not help me... Thx in advance...
  14. Well, the realmodules placed in fs\modules folder cannot use MFC! So you might do the following: write a MFC Dll that handles your dialogs, put it into your FS main folder and now you are able to interface with your module, that's all...
  15. Well, though this thread was created more than 1 year ago, U found one reason why this message can appear whilst loading FS: I got the message and tried to delete FSUIPC.DLL. The system reported an "access denied" error and I took a look at the list of running processes and found a fs session that had no window! Probably the process closed all its windows during shutting down fs but did not properly terminate for some reason. So starting fs causes FSUIPC.DLL to check for another instance in memory which could really be found! So - before reinstalling fs - take a look at your process list before you decide to reinstall:-)
  16. Hi Peter, i have one question a little bit absent of FSUIPC (i think so) - i would like to retrieve the nearest airport from a given location (lat/lon). I think i have to read one or more bgl-files, isn't it? But which ones? Best Regards
  17. Dear Peter, i'm currently writing a Module (MS VC6, SP5 running under W2K SP4) for both FS2002 and FS2004. When the module is activated through menu or hotkey (Shift - F8), a dialog box appears: This box is closed by clicking either OK or Cancel Buttons. So far so good. In FS2002 everything works fine. In FS2004 everything works when FS is running in windowd mode. When FS2004 runs in fullscreen mode i have the following phenomenon: activating the module via menu causes its normal work. Doing this by pressing the hotkey the dialog box opens but cannot be seen; it is somnehiw not being displayed, but - it is there and you can click its buttons which do their work. This happens most of the times activating by hotkey - sometimes it works.. Very strange.. Best regards and thx in advance, Michael Coded as follows: // // Dialog box // BOOL DoMdlDialogBox( VOID ) { DialogBox( hInst, MAKEINTRESOURCE( IDD_MDL_DIALOG ), hFSimWindow, (DLGPROC)DlgProc ); return( TRUE ); } // // // FS Windows procedure (subclassed) LRESULT CALLBACK FSimWindowProc(HWND hwnd, UINT uMsg, WPARAM wParam, LPARAM lParam) { fShift = (BOOL)GetAsyncKeyState( VK_SHIFT ); fCtrl = (BOOL)GetAsyncKeyState( VK_CONTROL ); switch (uMsg) { case WM_KEYDOWN: { if( wParam == VK_F8 && fShift ) { DoMdlDialogBox(); return( 0 ); } break; } case WM_COMMAND: { if (LOWORD(wParam) == ID_MY_MENUITEM) { DoMdlDialogBox(); return( 0 ); } break; } } // Call the original window procedure to handle all other messages return CallWindowProc(oldWndProc, hwnd, uMsg, wParam, lParam); }
  18. Hi Peter, i retrieved the relevant addresses using FS Interrogate: Address 0628 holds the flag for instant replay (0/1) Address 062C holds the remaining time Both Addresses have been found in FS2002
  19. Hi Peter, hi folks, i would like to retrieve whether the SIM is in instant replay mode - how is that possible? I didn't find any appropriate token variable or function in the SDK.. Thx, Michael
  20. Hi Peter, i have one question concerning module programming - can you give me a hint what is neccessary to make a dll module run in fs (2002/2004) with an entry under "Modules" in fs and a hotkey? I'm using VC6 with MFC. Thx in advance and best regards
×
×
  • 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.