September 30, 200916 yr Last night on a flight in the PMDG 747-400 in FS9.1 I had a recurrence of a problem which involves both ASA and Radar Contact and which has been blamed on ASA. This is when RC stops working and a message pops up saying "FSUIPC_WAIT cannot change D008 from (then follows a 6 or 7 figure number). It is always (the number is repeated)". The 6 or 7 figure number is not always the same.I am using ASA B435 but it has occurred with earlier builds. I have version 3.9 of FSUIPC but it has occurred with earlier versions too.After this happens I have to close RC and continue without ATC.I do not ever recall this happening with ASv6.5.I know others have experienced this. Is it being looked at please?Iain Smith
September 30, 200916 yr Last night on a flight in the PMDG 747-400 in FS9.1 I had a recurrence of a problem which involves both ASA and Radar Contact and which has been blamed on ASA. This is when RC stops working and a message pops up saying "FSUIPC_WAIT cannot change D008 from (then follows a 6 or 7 figure number). It is always (the number is repeated)". The 6 or 7 figure number is not always the same.I am using ASA B435 but it has occurred with earlier builds. I have version 3.9 of FSUIPC but it has occurred with earlier versions too.After this happens I have to close RC and continue without ATC.I do not ever recall this happening with ASv6.5.I know others have experienced this. Is it being looked at please?Iain SmithFSUIPC version 3.93 is current, with a minor update to version 3.936This is an error related to FSUIPC's handling of AI data. Offset D008 is a timestamp that changes whenever certain AI data is updated in FSUIPC. The error is telling you that FSUIPC's AI updates have stalled.This is probably a question for Pete Dowson on his FSUIPC forum.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
September 30, 200916 yr Author FSUIPC version 3.93 is current, with a minor update to version 3.936This is an error related to FSUIPC's handling of AI data. Offset D008 is a timestamp that changes whenever certain AI data is updated in FSUIPC. The error is telling you that FSUIPC's AI updates have stalled.This is probably a question for Pete Dowson on his FSUIPC forum.Thanks Bob but this doesn't explain why this only happens with ASA and not with ASv6.5.Iain Smith
October 1, 200916 yr Thanks Bob but this doesn't explain why this only happens with ASA and not with ASv6.5.Iain SmithMaybe not, but Pete has some good logging and debugging features built into FSUIPC, and he might be able to instruct you how to log details of what's happening through the FSUIPC interface--details that could help somebody solve the problem.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
October 2, 200916 yr After this happens I have to close RC and continue without ATC.A problem I'm familiar with. Although one doesn't has to close RC. Just click on the error message that pops up and then RC is working again, although it is still looking for your aircraft where it was when the error occured. Which means that you have to ask for a direct to the currently active waypoint.
October 2, 200916 yr Author A problem I'm familiar with. Although one doesn't has to close RC. Just click on the error message that pops up and then RC is working again, although it is still looking for your aircraft where it was when the error occured. Which means that you have to ask for a direct to the currently active waypoint.That doesn't work for me Farlis. I get the message repeating after I click ok and RC has completely locked up.Iain Smith
Create an account or sign in to comment