Jump to content
The simFlight Network Forums

draci

Members
  • Posts

    84
  • Joined

  • Last visited

Everything posted by draci

  1. Thanks John, do you think a simconnect stall could lead to this behaviour? Especially for the edited part in my above post concerning FSUIPC?
  2. Hello, I use Active Sky as my weather enine and I use REX SkyForce for cloud textures injection in P3Dv5. I have a strange issue in P3Dv5: Quite regularly, mainly after a few hours flight time or over the ocean my clouds get deleted completely immediately after injection by Active Sky. I can see the clouds for a sec and then they get cleared. It happens for example when flying over the ocean, although Active Sky has complete coverage through interpolation I lose clouds and shortly before the coast, thex show up again. But this happens also over the continent, where coverage should be complete. The strange thing is that this doesn't happen with all clouds, especially departure and arrival weather is usually correct. It seems that overcast conditons are especially prone to get removed, my trans-atlantic flight with overcast conditions from Newfoundland to Ireland happened in clear weather. Very annoying. Since Active Sky uses FSUIPC to inject weather, I hope that someone here can help me. What should I log? Can it be a simconnect stall? Or are there some interfering weather engines active? is it FSUIPC overruling the weather injection? I made sure that the REX engine is off and only the cloud sync facility stays on. A very strange issue is also that after a few hours flight time the FSUIPC inflight menu behaves very strangely: If I click on a tab, the tab vanishes, if I click all tabs, the FSUIPC menu is empty, no way to recover the tabs. Any help appreciated.
  3. Wrote a little simconnect client to implement the above functionality. Works without any problems, no recursive calls at all, brakes failures efficiently blocked, me a happy camper. 🙂
  4. Ok, I have tried to reset the P3D brakes failure via .lua scripts for weeks without success. Here's what my main problems are: 1. Writing to the offset 0B63 with ipc.setbitsUB and ipc.clearbitsUB doesn't work. The failure in the PMDG->Vehicles->Failure Menu persists for Left and Right Brake. 2. Toggling FS-controls 66310-66312 via ipc.control(6631x) in order to reset randomly occurring failures doesn't work either or seems to end up in infinite recursions since event.control(6631x,"callback") is called everytime the callback-function calls ipc.control(6631x). Cancelling the recursion via event.cancel("callback") does not help. 3. The FSUIPC Fs-controls "Toggle Left/Righ/All Brakes Failure" surprsingly DO work to trigger a failure, however, repeated use doesn't clear the failure. However, since there are Add-Ons like FS-Flight Control which can both trigger and reset failures, there must be a way to control the failure state somehow. My lua scripts are correct and FSUIPC Debugging/Tracing for them doesn't reveal any issues with my code, the logic runs as intended. What else can I try?
  5. Corrected the typo: leftFailed <-> LeftFailed and rightFailed <-> RightFailed, but still no success.
  6. Hi everyone, I have an add-on that randomly triggers brakes failures in my sim which is really annoying. The only FS controls I found are toggle_left/right_brake_failure which are controls 66311 and 66312. The following simple lua script brakesresetevent.lua intends to reset the brake-failures when ever they occur randomly. The second script brakesevent.lua (further below) should give me the opportunity to overrule the resetting such that I can sill fail the brakes if I intend to. brakesresetevent.lua: ipc.set("leftFailed",1) ipc.set("rightFailed",1) local lfail = 0 local rfail = 0 function leftreset() lfail = ipc.get("leftFailed") if(lfail == 1) then ipc.set("leftFailed",0) ipc.control(66311) ipc.sleep(1000) ipc.set("leftFailed",1) end end function rightreset() rfail = ipc.get("rightFailed") if(rfail == 1) then ipc.set("rightFailed",0) ipc.control(66312) ipc.sleep(1000) ipc.set("rightFailed",1) end end event.control(66311, "leftreset") event.control(66312, "rightreset") The problem is that although I try to prevent recursive triggering of the event with the global vars leftFailed and rightFailed this seems to happen. In general lua there is the possibility to temporarily unregister and reregister an event. Is this also possible in FSUIPC? brakesevent.lua: ipc.set("LeftFailed",0) ipc.set("RightFailed",0) ipc.sleep(200) ipc.control(66311,0) ipc.sleep(100) ipc.control(66312, 0) ipc.sleep(200) ipc.set("LeftFailed",1) ipc.set("RightFailed",1) ipc.runlua("brakesresetevent") The idea is the following: The first script runs from the beginning of the sim session (Run by FSUIPC.cfg). Whenever I hit the key combo, the first script gets killed by KillLua and the second script is started when releasing the key combo. That's why I restart the continuously running first script at the end of the second script by ipc.runlua. However, whatever I try I get recursive callbacks since the brakes flicker wildly from on to off. I'd appreciate if anybody could help me see my mistake. regards draci
  7. Ok, the problem is resolved, using "toggle brakes failure left" and "toggle brakes failure right" WITHOUT the "toggle all brakes failure" does the trick: it resets the failure on both brakes. However, pressing the key a second time does NOT reactivate the failure, so it's not really toggling, but I don't mind, since for my purposes resetting the failure is all I need. Thanks anyway.
  8. Dear John, thanks for your reply. The 0B63 was just a typo, unfortunately also the parameter 7 has no effect. If I let the brakes fail in the P3D menu, the FSUIPC assigned key does not remove the failure.
  9. Hi Pete and John, I noticed that one of my add-ons triggers random brake failures on my PMDG 747 in P3Dv5 (Unfortunately, I don't know yet which). It's not the PMDG failure from the FMC being triggered but rather the P3D failure from the Vehicle->Failures Menu. So I tried to use the Offset Byte ClrBits Command on the 063B offset with parameter 2 (to reset all brakes at once) but so far without success. If the offset is not working (?-SimE), is there another method to achieve this or am I simply applying the wrong command? Any help appreciated. Regards draci
  10. Thanks John for helping me. I realised that the problem is in fact the SHIFT-key. If I use key-combos without SHIFT (eg. TAB-1, TAB-2, .., etc) the toggling works fine as if I used a button. However, I didn't know that the SHIFT-key doesn't work in FSUIPC commands. Is there a special reason for that? Kind regards, Maik
  11. I'm trying to fool one of my Add-ons into believing that one of the aircraft doors is open when in fact it's still closed. This is needed for the Add-on to work and doesn't influence my PMDG 747 since the aircraft logic uses its own offsets for doors anyway. In order to achieve this I use the "Offset Byte Toggle Bits" Command on the 0x3367 offset in FSUIPC and hand over the bit to toggle as a parameter. This works flawlessly on all doors if I use a joystick button to trigger the toggling (at least on the most important ones since the aircraft has 10 doors but the byte has only 8 bits to toggle). The problem is now that I don't have 8 buttons to spare for the toggling of individual doors, hence I use key-combos (SHIFT-1, ... SHIFT-10). However, if I try use the very same Offset Toggle Bit commands with these key-combos as a trigger nothing seems to happen. This puzzles me a little since the logic of the FSUIPC-command should be independent of the trigger so I'd expect the toggling to work either with both or none of the triggers. What do I miss here? Any help appreciated. Thanks in advance. Kind regards, draci
  12. Thank you John for your valuable help. I will try to do this and report back.
  13. One of my add-ons deletes the P3dv5 GPS-flightplan after touchdown. This is a problem for other add-ons relying on the GPS-flightplan to work properly and that are active until gate arrival (for example a Traffic Board displaying user flight information). All these add-ons immediately fail after touchdown. I had the same problem in FSX times and I remember that I could solve by using the FSUIPC event.intercept function to inhibit the deletion of the flightplan, but unfortunately I don't remember how I did this. Perhaps anybody can point me in the right direction. For example: Which is the right flightplan-event variable to intercept? (I don't find anything suitable in the event list) And how exactly do I do this? Is simply intercepting the event enough to prevent it from happening or do I need to inject the flightplan again after the interception?
  14. Hi to all, I occasionally get sim freezes of a few seconds on long haul flights. Whenever such a freezes takes longer than usual (eg 5 seconds) FSUIPC logs the freeze and afterwards doesn't work correctly anymore: I can't use my lua plugins anymore, if I want to open FSUIPC GUI via Add-ons menu all the tabs are empty! Also Active Sky seems to behave very strangely: after download clouds get injected and stay for half second, then they disappear and skies remain clear for the rest of the flight, even if metar says overcast. I tried to make the simconnect_stall-time larger in the FSUIPC.ini (12 sec) but that didn't help much. Here's the relevant log part: 1439953 ### Mode: PAUSE on 1801891 ### Mode is NORMAL 7377110 ### Mode: FREEZE_ATT on FREEZE_ALT on FREEZE_LATLON on 7436563 ### Mode is NORMAL 12464485 **** Restarting traffic scanning due to non-reception *** My flight still continues without crash but FSUIPC quit logging which indicated for me that is does no longer consider the sim running. I'm running latest P3Dv5.3 with HF2 and latest FSUIPC6 registered version. Is there a way to prevent FSUIPC from quitting? Regards draci The full log is attached for convenience. FSUIPC6.log
  15. Thanks for your help, Pete, ugrading P3D to version 5.3 solved the issue, hence it was a P3D problem (eg. a messed up wxstationlist.bin file???) as you guessed above and neither related to FSUIPC nor to VoxATC.
  16. Sorry Pete, to bother you again, but do I understand your quick reply correctly that I have a wrong setting in P3D weather or Active Sky? II'm not aware of any global option...I don't understand why P3D reflects the correct weather conditions reported by active sky and FSUIPC doesn't use them. I have no idea what I could have messed up here? <not even reinstalling the P3D client helped...
  17. Hi to all, I'm using VoxATC and ASP3D in P3dv5.2 mostly flying the PMDG7478i and since a few days I have the strange problem that VoxATC ATIS always gives me winds calm no matter what ASP3D metar for departure is. Today I realised that the FSUIPC weather log also has the issue of calm winds, with ???? where the airport locator should be iin its metars. It seem as if FSUIPC could not detect the airport at which the aircraft is located. Here is the extract of the log file: 388563 Weather Read request (At Aircrft) to area 4: Lat=37.61, Lon=-122.36, Alt=7.8, Req=2 388625 Weather Received (type 4 request, Interpolated): "????&A0 171801Z 00000KT&D3NG 100KM&B-450&D5450 CLR 10/05 Q1014 " 388625 WX Received in (62 mSecs), WX request type 4, Lat=37.6118, Lon=-122.3584, Alt=7.8m Perhaps anybody can help me out here, since I've no idea why this happens. Please find the full log of the short session attached. FSUIPC6.1.log
  18. In the PMDG747 I realise that I need to move the joystick throttle unrealistically far forward until the aircraft starts moving, hence I would like to get the effect that a small movement of the joystick throttle on the lower end of the axis corresponds to a larger movement of the PMDG747 throttle. I imagine that I can do that by simply creating a suitable sensitivity curve (is there another way?) but somehow I haven't been very successful so far. Similarly the elevator responds very late if I draw the joystick back which leads to bumpy takeoffs (aircraft suddently jumps off the runway) and ugly flares (only millimeters of joystick movement decide between flying the aircraft into the runway or stalling it by excessive flare). Any help appreciated. (The joystick is an old SAITEK Hotas.) Best regards draci
  19. Dear Marc, I have a similar problem in P3dv5, when the MPC Combo is LINDA-driven. I wouldn't call the behaviour "erratic" but when I turn the heading knob - let's say - 1 click to the right, the HDG sometimes jumps up to 3 degrees to the right and sometimes even three to the left, although I turn the knob to the right. Whether FSUIPC or LINDA is the culprit, I don't know, most probably it is just a worn-out knob-mechanism since I have been using the MCP Combo for ten years now, and the HDG knob was turned thousands of times. What helped a little is disabling the fast movements (++) and (--) which seems to give a little more control precision. My problem is even worse than yours, since I constantly get ucrtbase.dll errors on every flight in the PMDG QOSII and I have the suspicion that it must be the VriSIm-software causing it. Reading your discussion above brought me to the idea that I could try the VriSim Software instead of LINDA (since I already use it successfully for the CDUII in P3dv5), perhaps this will prevent the CTD, however, I don't remember exactly how to set it up: In the keymap-file I assign key shortcuts which I then assign in FSUIPC to PMDG offsets (taken from the .h file in the PMDG folder), is that correct? Draci
  20. Hi to all, I've been running VRISim-Hardware successfully in FSX and have recently made the transition to P3Dv5. I managed to get the MCPCombo running (driven by latest P3dv5 compatible LINDA-version) and also the CDUIII (driven by the old VrISimSoftware). Everything runs perfectly initially, but about 1 hour into the flight, P3Dv5 crashes with an urctbase.dll error. This happens in every flight, I haven't managed to see any landing runway so far in P3dV5. I exclusively fly PMDG planes (mainly the PMDG747-8i and I have quite a complicated multi-monitor setup witch touch screens even android tablets to display undocked panels using virtual drivers. There are plenty of options for urctbase.dll errors in my setup, but I think I have it nailed down to the VriSim Hardware by now. The reason why I post this here is that VriSim hardware uses FSUIPC for sim communication. So here my questions: 1.Is there a way to get more crash information from FSUIPC than than the windows event viewer, especially to find out which hardware part causes the error? (My FSUIPC.log doesnt show any info except that P3Dv5 has quit.) 2. Does anybod run VrISim hardware successfully in P3Dv5 and can point me into the right direction of what to do? I'm running latest FSUIPC, latest LINDA, latest VriSImSoftware (10 years old!) and latest COM-port drivers.
  21. The autopilot in the PMDG 747 usually initiates sharp turns too late which results in unrealistically high turn rates and bank angles. To counteract this, I usually disengage LNAV mode in the PMDG 747 autopilot a few miles before the turn and use HDG SEL mode to fly the turn "semi-manually" by slowly increasing/decreasing the HDG bug incrementally with the effect that the turns become smoother at a more realistic turn rate and with less unrealistic bank than when I let the autopilot command the turn in LNAV mode. However, if the the winds dynamically change during the turn, especially in gusty conditions, it can happen, that a left turn (heading bug to the left of current heading needed to keep the plane on track) suddenly becomes a right turn (heading bug still at the same position but current heading to keep track suddenly switches to the left of the heading bug in new wind conditions, for example in a strong sudden gust from the left) with the result that the autopilot immediately rolls the plane from a left bank angle to the right at an unrealistically high turn rate and bank angle (S-Turn). So far I haven't found a solution for this issue, but my idea was that if I was able to "freeze" the wind directon and speed dynamically during the turn (for example by pressing a joystick toggle button) this sudden banking to the opposite side would no longer happen. After the turn and after engaging LNAV mode again, pressing the toggle button would "unleash" the winds again such that I could keep getting turbulence effects on the plane in level flight. So here's my question: Is there a way to impement this "wind freeze toggle" in FSUIPC or otherwise? Or did anybody find an alternative solution to the sudden banking when flying a turn in HDG SEL mode subject to sudden changes in wind direction? Any help appreciated. (Btw, I usually use Active Sky as a weather engine and I am aware that in AS settings you can locally and globally freeze the winds, but there is no way to toggle winds on or off dynamically inflight, so I would basically need to bring up the AS settings menu before and after each turn to achieve what I want which I do not consider a solution.) Best regards draci
  22. Thank you John for your quick reply, No I simply plugged the monitors to the new card, no reinstall, no trashing FSX though. I mean, the .ini file is still there (I don't even know whether it has changed!), and yes I do have saved a few copies over the years, but I think they are useless for the new configuration anyway, or am I mistaken? So can it be that FSUIPC recognized the new graphics card and monitor connections when I fired up FSX for the first time after the card change and the .ini file was overwritten with new data?
×
×
  • 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.