shibekora

Thank you John I have tried flight with ver6.2, however I got same CTD at 2700ft. So, my issue is not related to the version. I am sorry for bothering you on my issue. I have to research what is the cause by other way including Pete's topic referred by you. Anyway, thank you again. PS. Now I am trying to find the cause without activesky, so CTD now talking has no relation with activesky. Shibekora FSUIPC6_v62_CTD.log

Hi I have been using FSUIPC very conveniently for log time thank you. Now I have FSUIPC6 for p3dV6.1.11 registered. FSUIPC version is as follows by log file ********* FSUIPC6, Version 6.2.1 (19th July 2024) by Pete & John Dowson ********* Prepar3D.exe version = 6.1.11.31619 Running inside Prepar3D v6 Module base=7FFEB5760000 Windows 10 Home 64 Bit reported as Build 22631, Release ID: 2009 (OS 10.0) Reading options from "C:\Users\shibe\Documents\Prepar3D v6 Add-ons\FSUIPC\FSUIPC6.ini" Checking the Registrations now ... Recently I have a strange issue that CTD happens exactly same indicated altitude at 2700ft with fair weather condition by any type of aircraft and wherever of airport. The altitude is just below 3000ft from the lower altitude of cloud layer. If I set more higher altitude for its layer like 1000ft more, the CTD altitude become higher by exactly same of 1000ft. It is not related to the type of cloud. P3d default altitude for fair weather is 5730ft, CTD happens at 2700ft. So far, I have made clean uninstall and install p3d, and made flight without any add-ons except FSUIPC, Spad.next and chaseplane pro. However I have CTD at the same altitude. Today, finally I have made flight with deleteing FSUIPC6 from P3dv6 add-ons folder, no CTD at 2700ft and above. I have updated FSUIPC6 from 6.2 to 6.2.1 in this summer when I had different issue with activesky. Support from HIFI, FSUIPC might have some unmatch trouble with activesky v6, therefore I should update to new one. It seems CTD at 2700ft have started at that period. To my regret I do not have back up of prior version6.2 and no link for prior version in the Pete & John Dowson's software web site. That is why I made this inquiry. Could you please give me a opportunity to try with prior version? shibekora

Thank you John for your advice. I have tried both ways, however regretfully I could not control virtual buttons in the display. Having seen my macro file thoroughly, I have noticed that pointing address (?) of mouse of No.1 and No.2 are the same (RX27400800) even though they are different place in the display. Other macros (No.2, 3, 5, 6, and 7, I have made more macro after my first inquiry) have their own different address respectively. 1=elec=RX27400800,3 2=baro_standerd=RX40000051,3 3=baro_reset=RX4000004c,3 4=FTCL=RX27400800,3 5=Can_Recal=RX40000063,3 6=TFC=RX40000057,3 7=WXR=RX40000056,3 I wonder if mouse clicking could not distinguish both the places correctly due to the QW's specification. That means, I think, I could not make any mouse macro for the virtual button in the display. Thank you for your kind help again. Moto. Miyawaki

Thank you John for your quick reply and suggestion of QW's forum. Yes, I have reviewed QW's forum and made inquiry on this matter, but no respond. So that I made a question on this forum. Having reviewed the forum you suggested that seems to be on the matter of reading the value of MCP or reading Lvars. Lvars of QW are a little bit weird for me. Sometimes, a name of Lvar is quite different word on the button related, some Lvars appears after several times of mouse click on the button, and some show different response as in their official document for sim builders kits. Anyhow, I could get almost Lvars for my sim utilizing FSUIPC+mobiflight and Spad.next so far. Finally the command unassigned are the virtual buttons in the display as attached gif file. As I said in the first inquiry, this screen could be shown by clicking SYS button in the glairshield (that is OK by Lvar or mouse macro), then I like to push "ELEC" button in the display as shown green color in th attached file. Since I could click this button by real mouse, I like to push this button through my sim panel, so, I have tried to get mouse macro on this click and got macro as attached file. Macro no. of 1 and 4 are those for them, 1 is for ELEC 4 is for FTCL respectively. Macro no of 2 and 3 are for the phiscal buttons in the glairshield that work well isuccessfully. That is story for my inquiry. If mouse macro is not to be applicable for this type of screen button (virtual button?) I will give up to do. I am sorry for bothering you on this matter, It is enough to know whether I could or not. Best regards, MOTO. Miyawaki 787.MCRO

Hi, My sim is P3D V5 HF1, FSUIPC is ver6 registerded. I am trying to make mouse macro for QW787, some are successfully great, thank you for FSUIPC. Some are not, I wonder if those are buttons in the display. I have reviewed this forum by key word of mouse macro, display, QW787 etc, but could not find related topic. QW787 has 4 displays, PFD and Navigation display for pilot and FO. Each could be changed with different informations. I would like to push the buttons by mouse macro on system screen mode in the navigation display. They are for electrical condition (check APU ok?),and FTCL (set stab trim). As I could make other mouse macro successfully, I have followed same way to make mouse macro on these button too, and assign them to keys which are not assigned to other commands of sim. I could hear of very small sound of clicking from PC when I bush the assigned key, but nothing changed in screen. My question is "Is it possible to make mouse macro for the button in the display, mouse macro has to be set to physical button?". If not, regrettably, I have to give up. Hoping to have advice. Moto. Miyawaki

Today, I have tried autopilot flight with modified lua file adviced by Pete. Everything was done very well as I wanted. After take off, pushing AP button, then yoke was started to be driven by servo motor as same as in sim. During flight yoke moved according to the yoke motion in sim. Before landing, servo driven was disconnected by disengaging AP by disengage bar. That was fun and the circumstance as I wanted. Simflight has been to be much much motivated. Some modifications of offset value and calibration on mobiflight were necessary for coming to above condition. They were not matter but let me know more about lua and offset. Thank you Pete again. Moto. Miyawaki

Thank you Pete for your so quick and polite advice. I will do try again upon your advice. According to the real value of aileron and elevator of Lvar, I think they should be signed one too as you said. However as fur as reviewing the figures of them in Spad.next, they are changing in between + side proportionally to the full yoke movement. For me, it does not matter, must thing is "proportional to", they could be modified or calibrated in mobiflight. Anyway, thank you again for your kind advice. Moto. Miyawaki

I am very new for scripting lua file. So, I am sorry for my inquiry may be out of question. I have registered version of FSUIPC6 as attached log file (sorry for the allowable size, I have cut same lines in the middle), my sim is P3D V5.1 HF1, and the aircraft is QW787. Since I could got my purpose successfully with PMDG737 on which I could move throttle and yoke by motorized servo in autopilot condition utilizing mobiflight and arduino, I am trying to get same thing with QW787 too. However, there are no information on the related offset as in PMDG. Only things I could get are Lvars that are shown in QW's document. I have checked which Lvars are the ones necessary for getting the information about the condition of autopilot, and real movement of aileron and elevator by utilizing Spad.next. Eventually, I have got the Lvars as follows; QW_MCP_L_AP_Button ; 1 or 0 QW_aileron_left ; numerial with + QW_elevator_left; numerical with + Reviewing this forum, and documents as FSUIPC Lua Library.pdf, FSUIPC Lua Plug-Ins.pdf and so on in the FSUIPC folder. I have tried to make following lua file named ap_qw.lua. function ap_on("L:QW_MCP_L_AP_Button", value) value=ipc.readLvar("L:QW_MCP_L_AP_Button") ipc.writeUW("66C0", value) end function servo_ai("L:QW_aileron_left", value) value=ipc.readLvar("L:QW_aileron_left") ipc.writeUW("66C1", value) end function servo_el ("L:QW_elevator_left", value) value=ipc.readLvar("L:QW_elevator_left") ipc.writeUW("66C2", value) end event.Lvar("L:QW_MCP_L_AP_Button", 100, "ap_on", value) event.Lvar("L:QW_aileron_left", 100, "servo_ai", value) event.Lvar("L:QW_elevator_left", 100, "servo_el", value) I have copied this file into the folder of C:\Users\shibe_fsx\Documents\Prepar3D v5 Add-ons\FSUIPC6. Then, start sim, I have got log file above mentioned and had attached ini file in which I could see the lines [LuaFiles] 1=ap_qw [Auto] 1=ap_qw as stated in the FSUIPC document. Lines of [LuaFiles] were automatically set. Lines of [Auto] were set by myself. During running the sim I made several different options in recording log so as written in the log file. In case of running mobiflight, read command was repeatedly appeared. However, I could not see any figure changes related to Lvars. They are all "0" in offset of 66C1, 66C2 even though those figures are changing according to the real movement of aileron and elevator in the sim. Again, I am very new, so my script should be wrong. Any advice would be very appreciated. Moto Miyawaki FSUIPC6.ini mod_FSUIPC6.log