Jump to content
The simFlight Network Forums

Zangdaarr

Members
  • Posts

    9
  • Joined

  • Last visited

Zangdaarr's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. My FSUIPC version is 4.60 date march 2010 downloaded on a website last updated January 26, 2011 13:30 W. Europe Standard Time called Schiratti.com wich I hope is up to date. Alsmost 12 months old but up to date I assume. Ok the question is simple: what could make the macro editor not reccording even with the simpliest Microsoft Cessna. On this video: at 0:42 you have what I called the "green box". This never show up on my system.Since I made a lot of macros using Fs9 and some using FsX in the past, and since the log is updated, I can consider this situation as abnormal and not caused because I am totally stupid. And that's why I'm trying to get some help on what seems to me the best place to do it. Thanks.
  2. I know it works with MD11 cos there a lot of videos demonstrating it. Maybe it don'Mt work for the whole thing but at least you can define macros. I'm using latest version of FSX and latest version of FSUIPC :)
  3. Ok, tried with the md11, same thing happened, should work, so, I have a problem
  4. Hi, this is an microsoft bases aircraft, so I assumed it was supposed to be working. I'll try with PMDG, i remember the macro wasn't working on the 747, but at least, I could record them. I also so a video with the MD11 so i'll try with him
  5. Hi, I got trouble trying to record mouse macros When i click on the panel, the green box do not appears and i can't record the macro. The event is well reccorded as this is shown inside the log: 759725 Aircraft="Airbus A321 Paint5" 759725 System time = 23/01/2011 19:03:16, Simulator time = 20:50:42 (02:50Z) 762237 Advanced Weather Interface Enabled 969422 Sim stopped: average frame rate for last 210 secs = 68.3 fps 1015707 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1016300 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1016503 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1017532 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1017860 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1018094 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1018281 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1019373 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1019716 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1021245 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1021432 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1021619 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1022321 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1022524 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1022711 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1022930 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1023117 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1023320 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1023523 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1023710 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1023913 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1024100 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1024318 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1024505 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1024693 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1024895 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1025098 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1025270 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1025473 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1025675 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1126577 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1126827 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1127263 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll" 1128262 Mouse Event=65879 1128527 Mouse Event=65879 1128730 Mouse Event=65879 1128917 Mouse Event=65879 1129073 Mouse Event=65879 1129260 Mouse Event=65879 1136639 Mouse Event=65662 1137965 Mouse Event=65662 Could you help me with that?
  6. Hi ! In facts I was using classic actions to test my joy, like "open ATC". I resolved the issue by removing every fsuipc files and starting from 0, and now it's working perfectly ! I don't now why but it appeared to have a melting with my old 3.85 settings and my new ones. Thanks a lot for this programm, I've been an user of FSUIPC unregistered version for years, and now that someone told me "with such a lot of buttons, you should programm your joy with FSUIPC", I'm just understanding how it is powerful and useful!
  7. Thanks for the precisions, It's now working well during the macro creation, the tab test show me the right switch moving. But when I try to assign the macro to a button, then it doesn't work again :( In fact, it works with the first button, for the first switch, not for the others. [EDIT]Ok, here is the matter, the macros are working well. However, if I assign via FSUIPC an action to the buttons 16 - 17 - 18, FSUIPC see them well, but there is no effect in Fs. If I assign an action to theses buttons via Fs, it works well.
  8. Thanks for answering so quickly, In fact, the version problem disapeared since I re-entered my key, my version was not registered after updating. It was due to PMDG only. I now have the 3.90 version. The first solution I found for the Fuel Control Cutoff Switches is this one: However, it doesn't work with me, even with the default 737, maybe I'm doing something wrong ? Here is what I do: http://img5.imageshack.us/img5/9331/offsetbyte.jpg The second solution is what you describe in this topic. However, when I press TAB, it's always the first fuel cutoff wich is switched. I hope you may help me.
  9. Hi everybody, I am at this very moment trying to assign the fuel cutoff switches of the 747-400 PMDG Fs9 to my joystick. The first solution decribed here doesn't work for me. My version of FSUIPC is 3.85 and I can't update my version, I don't know why, Fs tells me: "FSUIPC is too old and flight simulator will now close". The second solution, found in another topic, is to use Offset Bytes, 3590,3594,3598,359C but it still doesn't work :( Could you help me to solve this problem? Thanks a lot
×
×
  • 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.