Jump to content
The simFlight Network Forums

lancairmiller

Members
  • Posts

    9
  • Joined

  • Last visited

lancairmiller's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Does one have to have the registered vers. of FSUIPC. to use lua plugins? I developed a routine for the club I'm in but not everyone has the registered ver.
  2. Does one have to have the registered vers. of FSUIPC. to use lua plugins? I developed a routine for the club I'm in but not everyone has the registered ver. Mark
  3. Pete, Super idea, Thanks again for your help. Mark
  4. Pete, Thank you for the quick response. I come from a VB background and it looks like Lua is a bit different. See if I understand this correctly. If I put this code in file Ipcready.lua, it will process the code when the flight sim is ready to fly. Once it code is processed the function is created and the event is created and is ready to use. Once the event is created I don't have to create a loop to rescan it at given intervals. Thanks again, Mark
  5. The problem is that the section shown stops the program ever exiting. It loops forever continually adding the function "fnident" as a routine to be called whenever keypress 122,0 occurs. It would be eating up your memory at the rate of something like 16 bytes per 20 mSecs until it crashed FS, eventually (it might take a long long time, though). Nothing will ever call "fnident" because when the event occurs (i.e. you press the key), the Lua program is already running and the "fnident" function is not directly accessible. It seems that you are mixing up two different ways of programming Lua for FSUIPC. One is to have the program looping, testing something at intervals, as in: while 1 do if then end ipc.sleep(20) end This loops, never ending, and checks on some condition at intervals. That is not the best way for many things, especially if the thing you are waiting for is a rare occurrence. Better by far is the Event system, in which your program merely tells FSUIPC what it wants it to monitor and what to call if it occurs, then ends. In your case, simply this: event.key(122,0,"fnident") In other words, just replace your entire while loop with the event.key call only. Regards Pete
  6. No. In general there aren't offsets for many controls -- even where there are, in most cases they simply cause FSUIPC to send the control for you. However, you can send any control you like, using its numerical equivalent (see the controls list in your FSX Modules folder), via offset 3110. Regards Pete Pete, Worked great. Thanks for your help.
  7. If it is assignable in FSX you could assign your buttons to it in FSX! If is it so assignable, it will be one of those FS controls I mentioned. If you enable Event logging in FSUIPC's Logging tab, then operate those actions, you should find the correct FS control name logged in FSUIPC's Log. then you can assign them directly in FSUIPC. But I would have thought the names would be obviouslike, perhaps, MP voice capture start and MP voice capture stop or maybe the other pair listed, MP broadcast voice capture start and MP broadcast voice capture stop? Why not just try them? Regards Pete I'm writing a VB6 program and connecting to FSX via fsuipc. Is there an offset assigned to "MP voice capture start" and "MP broadcast voice capture stop" I did not see one in the offset list I have. I may have overlooked it. Thanks again Mark
  8. Thanks for the quick response. In the FSX Setting- controls it is listed as Transmit voice start and transmit voice stop. The chat window make active is also listed under the multiplayer catergory.
  9. Pete, Great program, I've created a few programs now with VB6 with much success. I've been given a project that will require my app to use a key press to key the mic in FSX. When my app has focus(window active) the key strokes are not sent to FSX. If the user has assigned a button on a joystick or yoke is works OK. Is there anyway to send the transmit command to FSX via fsuipc? Thanks, Mark
×
×
  • 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.