Pete Dowson

Ah, well, it doesn't look likely that the Lua facilities can work with the device. I won't pass judgement yet, pending a test result with the "Logging = true" change. But if truly no input is seen then the device definitely needs a specific driver. Pete

Okay, but that seems to conflict with: So no success really? That appears to show that no data is received from the device. Did you actually use the switches during that session? Didn't you say there were 2 HID devices added by that device? Here: Perhaps one is output only, possibly to update its firmware. Try setting the VID and PID to the other connection. Also, instead of using the Lua trace facilty in the FSUIPC Logging options, try changing line 19 in the HidDemo.lua file from Logging = false to Logging = true. That way you'll get a concise report about what is received rather that a line-by-line blow. The FSUIPC trace is used to debug the code rather than to check device data. Pete

I'm afraid I know nothing about converting a string of WAV files into one file. There's no function provided by Lua to do this. I suppose, if you know the format of WAV files (which will be documented on the web somewhere) you could do it be reading the files and putting the wave parts together, changing some stuff in the header to deal with the changes. That's what any function in the Windows system, if one existed, would need to do in any case. Facilities for reading and writing files are available in the FSUIPC Lua implementation 00 see the LuaFileSystem.pdf provided with your FSUIPC documents. Yes, all that is normal and I understand, but you seem to have been saying that you have a separate sound card for each radio (VOR1, VOR2, ADF1, ADF2, DME): I only have separate sound channels for COM (for ATC) -- same channel for COM1 and COM2, and one channel for all the other radios. They come from my networked PC running ATC and SimSounds. My main 5-speaker system is for all the main aircraft and environment sounds from P3D5 and ProSim. I can't see any reason for having another 4-5 sound cards and speakers. The cockpit is that small that I don't think i could differentiate them in any case! 😉 Pete

With all the other documents installed for FSUIPC7 -- in your Documents folder, under "FSUIPC7". Pete

That is an automatic entry which is made when FSUIPC detects your Lua files. It is related to being able to assign buttons or keypresses to it. Please refer to that Lua document I mentioned. No! The [LuaFiles] section is not for you to edit. The [Auto] section is a list of commands, not a list of Lua files. You need to read the section John pointed you to more carefully. See the Example there, reproduced here: [Auto.737] 1=Lua SetMyOffsets 2=737 OHD:Air Allbleeds Whilst that is specifically for a Profile called 737, the lines it contains shows how to start a Lua plug-in and execute a Macro file. Not that when testing plug-ins it is best to assign a keypress to start them, so that you can restart them after any changes. Pete

As well as the section in the FSUIPC document John pointed you to, you should also find the FSUIPC Lua Plugin.pdf useful. Pete

Better to calibrate steps, so that you have simulated detentes for each flap position. See the section CALIBRATING FLAPS WITH SPECIFIC DÉTENTES on pages 41-42 of the User Guide. Pete

Yes, I am sure that can be done and there may already be such programs, but it could also be done with a Lua plug-in to FSUIPC. You'd need the wave files for the morse tones (probably a wave file for for each letter) and send to the relevant opened sound card using the Lua sound library). You'd have to read the offsets for the signal strength and the IDs and act accordingly. Perhaps one plug-in each for VOR1, VOR2, ADF1, ADF2, DME. However, I don't know what sort of aircraft has separate speakers (presumably spaced around the cockpit somewhere) for each type of radio signal. Seems really strange to me. Can you explain why that is so? You say: So all of the radio identity signals come from those? I would expect the same sounds emanate from both -- for clarity to both captain and first officer. So why a separate sound card for each type of radio? In my 738 cockpit I have four speakers and a bass woofer for the main sounds (from the Sim, or in my case, ProSim) engine sounds etc, and speakers in the overhead for ATC and some other sounds. I can switch the ATC sounds to headsets (one each side) with one of the overhead switches. The main sounds are from the sound card in the main Sim PC, whilst the overhead and headsets are connected to a speparate computer which runs the ATC program (Pilot2ATC) and SimSounds. Pete

I don't know how you are going to tell the Sim to send them to different sound cards. How do you do that? But that's what I am asking you. All those sounds are just sounds from the Sim. The switch offsets I listed are for the Sim sounds! The Sim simply doesn't differentiate sound cards -- there's no way to assign them per sound. What is the point of having 4-5 (or more -- engines, ATC/ATIS, weather) different sound cards? How are you using them? Pete

There's really not much point. The TOD depends on your flight plan, your aircraft, the weather -- a large number of factors. And many folks using flight sim seriously use alternative planners and ATC programs to those provided by default in the simulator. There's never been any way to get all of the data relevant to computing TOD from any version of FS or P3D (especially when addon applications are in use). It's always an approximation. The easiest thing to do is program a Lua plug-in to simply pause, reading the current altitude, and activating Pause when it sees a substantial decrease in altitude. But much better would be to use the one of the existing plug-ins already provided by users, to pause at the elapsed time that the TOD is expected - the time which should be provided in your planner. The lua plug-in facility was provided in FSUIPC (and WideFS) so that users could add their own specialised features. It is not difficult and simple things are simple to implement. i recommend you take a look at some of the examples already provided for you, and also those kindly provided by other users. Pete

There are on/off switches controlled by offsets. All you need to do is search the offsets list for "sound": 02FB for ADF2 3105 for VOR1 3106 for VOR2 3107 for ADF1 plus the group of switches corresponding to the default sound control panel in offset 3122 which also includes Marker and DME, but not ADF2. Pete

Sorry, I don't know a way of doing that. All those sounds will be from the one source, the 767, won't they? Or built into the sim. Why is their a sound card for each radio source? Does the real 767 have different speakers for each? Why not? Is this not supported by the 767? There are separate Sound controls available in the Sim. The Sim itself will sound the morse if that redios sound is enabled and the transmitter is in range. I don't know what your 767 is doing differently. Pete

If you have some WAV files you want to play on an event, yes, you can do that. By "cabin sounds" do you mean some which are not supplied with your LevelD 767? You may find is more satisfying to look at something like SimSounds, an add-on application which provides a multitude of sounds related to aircraft events and surroundings. That's what I use. Pete

Okay, but your question included "I tried to set the "control to repeat" option" which isn't an option for axis assignment (the left part of the Assignments tab), only for other controls selected for specific ranges within the axis movement (the rather more specialised right-hand part). Pete

The sound cards are listed in the INI file only so that Lua plug-ins written to play sounds (from .wav files) can make them go to a selected card. I don't know a way to separate sounds played by P3D itself. Might be worth asking in the P3D forum on AVSIM. Pete

Sorry, but I don't know that aircraft. However, you need to say how you are assigning these to your momentary buttons. And when trying the "Set" variant of the L:Var facility, what are you setting them to? You really do need to be more explicit. You say they Carenado are doing their own thing with the switches. So, have you tried the probably easier method of operating them -- Mouse Macros? Also, when you enable event logging in FSUIPC, do you see anything logged when you operate the switches? Finally, you always need to state the extact version number of FSUIPC. If it isn't 4.976, the currently supported version you really need to update. [LATER] I see you posted again (this time in the correct Forum), and yo already have a very helpful reply. I'll close this thread. Please continue there. Pete

Do those pedals act as AXES, giving variable braking according to how far you press them? If so you should be assigning to the Axis Brakes Left and Right controls in the Axis Assignments, not as Buttons! You should then calibrate them. You may need to select "rev" to reverse them there, depending on how they behave. You want 0 for no braking and 16000+ for full. Calibrate with the minimum set a little way pressed to avoid unwanted braking when using the rudder. If they are recognised as buttons instead then you need to supply more details about what you are assigning to and exactly what you are doing. Pete

No, it says for P3D4 and P3D5, because they were the only 64-bit supported sims at the time. The version for FSX and FS2004 (and P3d1-3) is GFDev.dll. The 64 in the GFDev64.dll name says it is 64-bit, as are FSUIPC5, FSUIPC6 and FSUIPC7. The instruction, which you needed to follow, was to simply download GFDev64.dll and install into the FSUIPC folder. Surely easy enough? Pete

GFdev64.DLL is in the Download Links sub forum in the Useful Additional Programs thread!

The Radar Contact code uses the FSUIPC multiline text display. There's no direct interface to Simconnect in RC - it uses FSUIPC offsets, and FSUIPC didn't provide a Menu facility as such. Pete

Do you know whether the drivers use FSUIPC? If so there's a chance they will still work, though if they are aircraft-dependent, that does sound unlikely. The other thing you could try, just for the inputs (switches and encoders) is the HidDemo.lua plug-in. You need to edit it to make it specific to the device (VID and PID, Vendor and Product IDs, shown either in FSUIPC's log, or certainly in HidScanner. HidDemo is in the Example Lua plugins ZIP in your Documents\FSUIPC7 folder. Pete

1. You don't need a registered copy to use normal FSUIPC client applications. Registration enables assignments for buttons and axes, calibration, and the use of Lua plug-ins. But the application interface is always available. 2. There's no specific things to do in FSUIPC7 for Radar Contact. Just install FSUIPC7, following the instructions. 3. Radar Contact uses facilities in FSUIPC to display menus on screen in the Sim. Unfortunately these are not working properly yet in MSFS -- the facilities provided by MSFS are faulty and we are awaiting a fix from Asobo. The menus may display okay, but they won't remove and may accumulate (lots on top of each other). You can try it, but be warned. Pete

Pardon me for barging in, but I am pretty sure it needs a driver supplied by FDS. I know there are drivers available to make it work with SimAvionics and also for ProSim, but I doubt that there's any generic driver for just any old aircraft. If you are using ProSim on MSFS then check in their forum that it is still supported in ProSim V3 (which you'd need to use for MSFS in any case along with the MSFS version of the ProSim B737). Though it's a USB HID device it will be using its own protocol for sending and receiving data. You could write your own driver but you'd need to get the protocol definition from FDS. Best really to ask FDS themselves about what they can do. i note from their website that they had drivers planned for the PMDG 737, but that seems to have been back in 2015 and that note hasn't been updated yet in their documentation. Pete

Why can’t you download FSUIPC? Which version do you want? Where are you looking? Pete

Two things: 1. Your FSUIPC is out of date. Please download version 4.976 and re-install. No need to re-register, just select 'not now' when it asks. 2. If you now get this problem say YES. If FSX then crashes, please show me the FSUIPC4.LOG file from the FSX Modules folder, and also the Windows crash details from the Event Viewer (Windows logs - Application. The most usual cause of this a corrupted weather file. Please see this thread in the FAQ subforum: Pete