Pete Dowson

You are using version 2, though, normally, surely? Why "as administrator"? Are you also running FS "as administrator"? If not they shouldn't be able to talk to each other. I've never found any need to run anything but Installers "as administrator". So how come it is trying to play all the waves from PC-Seldon? We saw from earlier that none of them are found -- the status return 3 I already mentioned. What is this "r4.cvs". Do you really mean the "r4.csv" file generated by my MakeRunways program, in the main FS folder? Yes, exactly as before -- it cannot get the sound files from PC-Seldon. The only time it got to play anything was from the FS subfolder. We've been through all that already. Because you only get that when using the FS folder. See above. I don't understand why you send another log just showing exactly the same. Note that you are always getting the 81589 **** No SimConnect events or states being received! Re-connecting now ... **** problem. You should never get that except through overloading. Something is seriously wrong. Pete

So, no crash now? What Lua plug-in? What do you mean by "sound address"? I can't figure out what you are talking about here. Sorry. Can't see any relevance there. So, not overloaded. But something most certainly is preventing things running correctly. I think you need to find out what is stopping Simconnect occasionally. It should never happen. I wouldn't be surprised it is wasn't related to the sound problem. Ah, sorry, yes. PC-Seldon is a folder on the desktop. It's still on the desktop though. I've never tried running programs that way. Pete

FSUIPC 3.75 is woefully out of date and completely unsupportable. You need to update. I still cannot understand what "little window" you are talking about, now what these 50+0 or 77+0 values refer to. Why aren't you simple assigning the throttle in the axis assignments page. What actual Tab in FSUIPC are you using and what are these "little windows"? What has the FS9.CFG file got to do with it? Why are you using the FULL INCR CUT controls? They are for keyboard control, normally assigned to F2,F3,F4 and F5. To change the keyboard assignments you don't need to edit the CFG file, you just go into FS9's control assignments and assign your key presses there. What has any of this to do with a throttle lever? I'm now even more thoroughly confused than I was after your first message! :-( FSX's keyboard assignments are not in the FSX.CFG file but in an XML file. They are keycodes for keypresses. The first number is a keycode, the second the shift codes. I provide a list in the FSUIPC Advanced User's guide, but generally there's no need to understand them -- just use the assignments dialogue in FS to assign keypresses to controls. So why are you using key presses. Where does the lever come into it? Normally, with most aircraft, you can assign in FSUIPC to throttles then calibrate in the multiple throttles tab. You get a reverse zone below the idle position. Doesn't this work for you? In FSUIPC you can also assign a separate reverser. If the aircraft doesn't respond to the normal controls for reverse thrust, then the normal thing to use is the THROTTLE_DECR control, repeating maybe to get full reverse. You can assign this control directly, you don't need keypresses (F2 is the default FS assignment for this control). I think you are confusing yourself (and me) by thinking in terms of key presses. Pete

In the case of a really big bounce I don't see that you can -- more like a touch and go, repeated! ;-). I suppose I could ignore any further changes from off-ground to on-ground for a few seconds. I've no idea what sort of time to allow though ... have you? It would be an easy change to make (FSUIPC4 only, I'm not changing FSUIPC3). Pete

Sorry, I don't understand. Are you trying to use a button for reverse thrust, not a reverser lever? Where does "key press" come into it? Where are you looking? Key presses don't have parameters, they are just presses of keys like on the keyboard. What are you trying to achieve? Pete

This is all because the throttles MUST be at idle before you can use the reversers. The symptoms you describe are EXACTLY what you'd see if the throttles were not at idle. Use FSUIPC's Axis logging to see what is going on. It still sounds like you have not actually set true idle zones which are 100% consistently set when you have the throttles full back and the reversers full forward. If you (temporarily) use FS in Windowed mode and enable the FSUIPC console logging you'll be able to see that actual numbers in real time on screen as you move these levers. [EDIT] I see Stephen has said it's a PMDG problem. I didn't know that, so sorry if I appeared to be bullying you about the idle zone. I was unaware of any PMDG bug like this. I should have suggested testing with a default aircraft first to eliminate such bugs in add-ons. Pete

The first part shows several sounds being sent to DirectSound. Interestingly, though, now I've looked it up, IPC: Status Response=3 means "sound has ended or reference not listed". But this occurs in the same millisecond as the sound request itself, which does suggest that the wave file can't be accessed by DirectSound, so the only time it crashes is when you use the sound files in the FS subfolder, so that's the only time it manages to access the file. You say it does actually play it before crashing, which is interesting. The sound facilities in FSUIPC being used here date back right to FS2000 days or maybe even before, and have never been changed. They are also the ones used by the Lua plug-in sound library, and many folks are using that for assorted things. I was using FSRAAS for some time before the payware FS2Crew RAAS Pro came out -- I find that a lot better in any case, and worth the money. I'll reinstall FSRAAS and see if I get any errors, but it is looking very like some sort of DirectSound problem. Did you try uninstalling and reinstalling your sound device so that the drivers get reinstalled? Or even trying different drivers? Sorry, is that the answer to my question "what sort of frame rates are you getting"? I don't understand. "Desktop" isn't really a directory, it's your desktop. It holds all the things you can see on screen. If you installed all of the wave files, and so on, on the screen you'd see them all, and it might then work, but i suspect you were trying to run the EXE on the screen with none of its supporting files. Maybe you meant to make a shortcut but instead dragged the EXE itself? Pete

I've no idea, sorry. You'll need to ask in an aircraft designer's forum. I don't even know if FS has any way to do "attachments". You might be better off with Prepar3D where they seem to be working on such things, mainly for munitions though, I think. Pete

I repeat, once the "on ground" flag is set the value will only change it if increases. This will only occur during the few milliseconds after touchdown, or more if it's a big bounce. Not sure. Ask me again tomorrow and I'll look at the code. There's an offset providing vertical speed at touchdown, and you know the one for G-Force. That's as close as I know how to get. How would you suggest? Pete

I've no idea. If FS's own ATC uses specific centre frequencies they presumably must be there somewhere. I use RC and as far as I know it generates centre frequencies pretty much randomly. It is only specific for airport related ones and ATIS. Pete

The "LockheedMartin" subfolder "Prepar3D" is for version 1. It seems you didn't really delete it, because installing version 2 or 2.1 will not add back in entries for Version 1. It won't do any real harm as far as I know, it will just cause spurious error messages and double installs like you saw. There's no where else I know of the entries might be. Pete

But the first log shows waves from both C:\Users\MABE\Desktop\PC-Seldom and from C:\MS_Games\FsRaas20 Are you saying you closed FSRAAS down and started it again, and that is the reason? The same wave played okay when you used the Desktop folder, so there's something bad happening when you run it from the FS folder. I'm afraid I've no idea what is going wrong with your sound system -- the crash is occurring in Directsound somewhere. Can't the author of FSRAAS help at all? Maybe reinstalling your sound drivers night help? No. The only way I know for SimConnect messages to stop arriving is because FSX is not getting enough processor time -- in other words it is overloaded or being prevented from executing for more than a second -- the timeoutr for data which FSUIPC uses by default.. What sort of frame rates are you getting? Pete

The registration system hasn't been changed at all since it was introduced with the release of FSUIPC3 and FS2004, with just one exception -- the facility to have a different email address for FSUIPC and WideFS. But the name filed must be identical. I am certain you must be making an error because the keys are automatically generated, and, as I say, the checking in FSUIPC hasn't changed either. There's no way they can be wrong that I know. You can't show me the details here so send everything to my email, petedowson@btconnect.com -- the data you are supposed to be entering and, if generated, the FSUIPC4.KEY file (ZIPPed please, or it won't get through) from the FSX Modules folder. Pete

Just make the change I showed above where I swapped the numbers over.. That may just save you editing every line or reassigning everything individually. Pete

All three parts must be exactly correct, not just the Key. You must be using the current version. You say "latest", but what number is that? It should be 4.929. Check the date on your PC. If that is before your purchase date the keys will be invalid. Pete

Just assign your controllers in the Axes tab. To start with, to avoid having to actually read too much of the manual, just assign to the FS controls beginning with the word "Axis" They are the same as those you'd get if you assigned in FS itself and so should work with pretty much everything. You don't need to calibrate then, if you can't be bothered or don't understand that part. But before doing any such things, disable controllers in FS. Pete

Same comments as for previous log. Did you check that wave file? This log is less informative in that it only shows that one bad wave file, not the others which were okay. Why are you getting SimConnect disconnections? Why is this "a more to the point" setup? Pete

Well, that's a great oversimplification. FSUIPC takes over nothing. You have to tell it what you want it to do. It is completely unaware of whether you disabled controllers in FSX or not. I've no idea where you get such an idea from! Well I never said FSUIPC could fix bugs in Win8.1. Other folks may have said that, never I. But when you assign controllers in FSUIPC you must not also assign them in FS. They will certainly conflict. If you are assigning them in FSUIPC then, depending on the add-on aircraft, you may need to choose the method of assignment carefully, and if you assign direct to FSUIPC calibration you MUST calibrate of the values won't get through. Pete

The problem being that some program trying to use FSUIPC for sound makes no sound? I see in the log you supplied that an error occurred on one of the Sound requests. But the earlier ones are okay: 145907 Sound: Ref 37, via IPC: Cmd=1, Wave="C:\Users\MABE\Desktop\PC-Seldom\Approaching.wav" 145907 Sound: Id 256, PlayNow("C:\Users\MABE\Desktop\PC-Seldom\Approaching.wav") 145907 Sound: Id 256, PlayTheSound("C:\Users\MABE\Desktop\PC-Seldom\Approaching.wav") 145907 Sound: Ref 37, IPC: Status Response=3 147109 Sound: Ref 3, via IPC: Cmd=1, Wave="C:\Users\MABE\Desktop\PC-Seldom\03.wav" 147109 Sound: Id 256, PlayNow("C:\Users\MABE\Desktop\PC-Seldom\03.wav") 147109 Sound: Id 256, PlayTheSound("C:\Users\MABE\Desktop\PC-Seldom\03.wav") 147109 Sound: Ref 3, IPC: Status Response=3 148310 Sound: Ref 41, via IPC: Cmd=1, Wave="C:\Users\MABE\Desktop\PC-Seldom\Right.wav" 148310 Sound: Id 256, PlayNow("C:\Users\MABE\Desktop\PC-Seldom\Right.wav") 148310 Sound: Id 256, PlayTheSound("C:\Users\MABE\Desktop\PC-Seldom\Right.wav") 148310 Sound: Ref 41, IPC: Status Response=3 But there was a serious problem with Simconnect stopping sending data to FSUIPC: 153505 **** No SimConnect events or states being received! Re-connecting now ... **** 153598 SimConnect_Open succeeded: waiting to check version okay 153614 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 153614 Initialising SimConnect data requests now 153614 FSUIPC Menu entry added 153630 C:\Users\MABE\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 154222 System time = 03/03/2014 08:15:07, Simulator time = 11:21:20 (15:21Z) That's rather worrying. What sort of performance are you getting? Is FS struggling? Nevertheless, further sound requests are serviced okay: 198059 Sound: Ref 38, via IPC: Cmd=1, Wave="C:\Users\MABE\Desktop\PC-Seldom\On Runway.wav" 198059 Sound: Id 256, PlayNow("C:\Users\MABE\Desktop\PC-Seldom\On Runway.wav") 198059 Sound: Id 256, PlayTheSound("C:\Users\MABE\Desktop\PC-Seldom\On Runway.wav") 198059 Sound: Ref 38, IPC: Status Response=3 199431 Sound: Ref 21, via IPC: Cmd=1, Wave="C:\Users\MABE\Desktop\PC-Seldom\21.wav" 199431 Sound: Id 256, PlayNow("C:\Users\MABE\Desktop\PC-Seldom\21.wav") 199431 Sound: Id 256, PlayTheSound("C:\Users\MABE\Desktop\PC-Seldom\21.wav") 199431 Sound: Ref 21, IPC: Status Response=3 200633 Sound: Ref 40, via IPC: Cmd=1, Wave="C:\Users\MABE\Desktop\PC-Seldom\Left.wav" 200633 Sound: Id 256, PlayNow("C:\Users\MABE\Desktop\PC-Seldom\Left.wav") 200633 Sound: Id 256, PlayTheSound("C:\Users\MABE\Desktop\PC-Seldom\Left.wav") 200633 Sound: Ref 40, IPC: Status Response=3 202099 Sound: Ref 54, via IPC: Cmd=1, Wave="C:\Users\MABE\Desktop\PC-Seldom\Flaps.wav" 202099 Sound: Id 256, PlayNow("C:\Users\MABE\Desktop\PC-Seldom\Flaps.wav") 202099 Sound: Id 256, PlayTheSound("C:\Users\MABE\Desktop\PC-Seldom\Flaps.wav") 202099 Sound: Ref 54, IPC: Status Response=3 Until again, the serious disconnection from SimConnect! And more persistent this time it seems: 355089 **** No SimConnect events or states being received! Re-connecting now ... **** 355198 SimConnect_Open succeeded: waiting to check version okay 355198 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 355198 Initialising SimConnect data requests now 355198 FSUIPC Menu entry added 356181 System time = 03/03/2014 08:18:29, Simulator time = 11:22:15 (15:22Z) 366040 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 367210 Weather Mode now = Custom 367210 Exception 3 "UNRECOGNIZED_ID", Ref 2387, Index param -1 on Weather request type 1 367210 Exception 3 "UNRECOGNIZED_ID", Ref 2388, Index param -1 on Weather request type 5 367210 Exception 3 "UNRECOGNIZED_ID", Ref 2397, Index param -1 on Weather request type 5 368349 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 368521 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 380611 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 385291 Memory in use: 1141Mb, Avail=2955Mb 404401 **** No SimConnect events or states being received! Re-connecting now ... **** 404510 SimConnect_Open succeeded: waiting to check version okay 404510 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 404510 Initialising SimConnect data requests now 404510 FSUIPC Menu entry added 404682 System time = 03/03/2014 08:19:18, Simulator time = 11:20:45 (15:20Z) And soon after that, a further sound request crashes: 445476 Memory in use: 1160Mb, Avail=2935Mb 445975 Sound: Ref 37, via IPC: Cmd=1, Wave="C:\MS_Games\FsRaas20\Approaching.wav" 445975 Sound: Id 256, PlayNow("C:\MS_Games\FsRaas20\Approaching.wav") 445975 Sound: Id 256, PlayTheSound("C:\MS_Games\FsRaas20\Approaching.wav") 445991 ***ERROR C0000005 at 76ED8E19 ProcessRequest 445991 *** Access violation trying to write address 00000014 445991 *** EAX 00000000 EBX FFFFFFFC ECX 00000000 EDX 00000004 EDI 5DE05D6C ESI 5DE05D68 Unfortunately that crash is deep inside DirectSound, so there's really no way I'm going to fathom it. A similarly named WAV file was played earlier, but from a different folder: "C:\Users\MABE\Desktop\PC-Seldom\Approaching.wav". In fact ALL of the previous WAV files which played okay were in the "C:\Users\MABE\Desktop\PC-Seldom" folder, so why is this now from "C:\MS_Games\FsRaas20"? The most likely cause of this crash in DirectSound is a corrupt wave file. Perhaps you could try playing it directly, in Windows Media player? Maybe that was when it got corrupted? Have you tried reinstalling FSRAAS? Personally I'd be more concerned over those Simconnect stalls. Something is causing that. Too late now., though the problem adding to this one is that the title " FSUIPC.ini does not recognize soundcard"does not apply in your case, obviously, And his exact reported problem was "In the FSUIPC .ini there is no [sound] section existing.". Pete

Okay. I confirm that in the outside spot view (at least -- not tried the others), Pan Left and Pan Right do nothing, whilst Pan Up and Pan Down swap ends -- nose or tail. However, Pan View, the normal axis assignment most folks use for views on hats, works okay, same as in FSX. I have to wonder why you don't use that? It is still worth reporting to LM, though I can see why no one would have noticed. Pete

Fist, check the box saying "NRZ" or "No reverse zone" (though from what you say I assume you've done that). . Then follow the numbered steps for calibration, making sure you have a good stable idle zone -- an area, not just one position, which is giving zero for the output value. When done correctly there is no possible way to get reverse from the throttle levers themselves -- it will then only be the reversers .... so: It's the same thing. You need a null zone, NOT just a single position, which is giving 0 as output for a small range of the reverser. The problem is that the same position, even at the end stops, is not always giving the same input to the sim. Variations occur due to minor variations in temperature, humidity, voltages, etc. You ALWAYS need max and min areas, not points, same with hands off positions on yokes and pedals. Again, it's exactly the same reason Pete

Definitely file a bug report -- not about a hat, but about the controls which should work but don't. I'll try to corroborate that when I've had a chance to try them. There are probably many little problems in P3D which are still to come to light. The only way to get them fixed is to get them on LM's list. Regards Pete

It wouldn't be the com library, for sure. that is so wrapped up in the standard Windows i/o functions it would be a nightmare to mix into that. Looking at the existing server/client examples, I don't really see a lot wrong with using the socket options as they are. The serial stuff is done using a separate thread from the Lua threads to monitor the devices in real time, accumulating stuff in buffers and so one before initiating the event. The sockets stuff is different -- the thread is held suspended automatically by the accept and receive calls. So they have to be executed in the Lua thread in any case. No events are needed to awaken a thread which is merely waiting for something to occur. The loops in those aren't bad loops because the requests I mention do the suspension and the event is their return. Honestly, I don't think there's a lot to be gained in changing things. Putting another layer on top of the sockets system calls just seems to make things less efficient and less flexible. However, I've kept your suggestions on file and may look again when I find myself with less to do than usual. Regards Pete

No, I have NEVER provided anyone with a patched SIM1.DLL. It is actually not legal to post Microsoft files for all to download. That is because with the previous version it was not being logged, but the check was still there. I added the log entry to make it clear to me and others when using the assorted P3D versions and patches whether something needed changes. Pete

The reason it's WideClient only is that it is for the ButtonScreen, which is a WideClient facility. If there is no WideClient there is no ButtonScreen! Why not just use a user offset, such as 66C0, and the assignable offset controls to set values there which can be easily read by your client-run Lua program? WideClient automatically runs any Lua script it finds in its folder. Use events to determnine when those scripts should actually do somethnig. Pete