-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
Strange problem with DynamicFriction.lua
Pete Dowson replied to mrichter's topic in FSUIPC Support Pete Dowson Modules
Not sure why you felt you needed to download the Lua package when it is installed automatically for you in the FSUIPC Documents folder along with all the documentation and examples. Anyway, all FSUIPC is doing is overwriting the values in the ground friction tables with new values. I've really no idea what these do -- I added the facilities when others had already experimented with manually patching SIM1 to do similar things. The facilities in FSUIPC are more flexible as they allow dynamic changes, which facilities are utilised by that DynamicFrictin package written by Bob Scott. As far as I can see, it only changes the frictions for taxi speeds above and below 30 knots GS. There appears nothing specific to whether you apply brakes or not apart from the GS changes. The [LuaFiles] section keeps an index of the first 127 Lua plugins placed into the Modules folder. The index is used when assigning buttons or keypresses to Lua plug-in actions, and the index is needed to provide consistent assignment. As far as I am aware it works as intended as it is. Certainly, once the table is changed it stays changed until it is changed again -- there's nothing in FS which changes it as FS regards it as a fixed, constant table. I don't know how you are verifying that things are reverting when you press brakes, but you'd need to check by writing a Lua plug-in to read the values and log them. Meanwhile, you can also of course enable Lua logging to see when and what the existing plug-in is doing. Since the plug-in is started when you start FS you'd need to enable logging then restart FS. Pete -
Sorry, can you clarify? There's no page 3 in the Axis assignments tab. Do you mean the Calibration tabs? If so then the exclusion options at the bottom, which are normally enabled, merely prevent the calibration of those specific FS controls. Don't forget how FSUIPC calibration works -- it intercepts controls before they arrive in FS's simulation engine and adjust the final values. The excluded controls are often used by add-on aircraft for internal direct control, as with a special autopilot. Those then should not be altered as if they come from a joystick input. The explanation is actually in the manual. It is in step 12 of "THE EASY STEP-BY-STEP WAY TO CALIBRATE YOUR CONTROLS". Pete
-
I see you have specified the Server IP address rather than let things sort themselves out, or by specifying the host name (UTILISATEUR-PC). Why? Have you checked that the IP address is still correct (192.168.1.12)? Because it is not getting through. If it is correct then you have some firewall preventing access completely. There is no sign of a connection at the Server side. Pete
-
FSUIPC.ini does not recognize soundcard
Pete Dowson replied to Mr.V's topic in FSUIPC Support Pete Dowson Modules
So please explain to me, then, why it is referring to WAV files in PC-Seldon. If it is only a shortcut to a "proper" folder elsewhere, the shortcut should include that folder as the place to get its files from. That's the way a normal shortcut works. I think you need to check the shortcut properties because you most certainly have it wrong.. By itself is no good. It needs all the WAV files and the R4.CSV file, probably others. Why don't you just do the simple thing I suggested, delete it all and start again with a clean install from a download, as I just did? Pete -
FSUIPC.ini does not recognize soundcard
Pete Dowson replied to Mr.V's topic in FSUIPC Support Pete Dowson Modules
What Lua plug-in? You mentioned one before. What plug-in are you using? And what security problem? This exchange seems to be taking a weird turn. I don't know where you are going with these extra mentions of other things. But the normal way to unclutter the desktop is to group SHORTCUTS into folders on the desktop, not complete sets of program files! I've never seen that done before, and I honestly think it is a bad idea. And it obviously is a bad idea for FSRAAS as it can't find the files it wants and points to WAV files which evidently aren't there either. Are you REALLY sure you didn't mean to use a shortcut in the PC-Seldon folder on the desktop, but instead incorrectly have the actual EXE there instead? It would explain why the sounds aren't found and why r4.csv isn't found. What's that part about? I don't understand your context. Why is C++ simple, if that's what you mean? Pete -
FSUIPC.ini does not recognize soundcard
Pete Dowson replied to Mr.V's topic in FSUIPC Support Pete Dowson Modules
I've downloaded and installed FSRAAS 2.0, and just tried it taxiing to and onto a runway. I enabled the same logging as you so you can see what you should get. I installed it in E:\FSRAAS, not in my FS folder (E:\FSX) but next door. I do not run either "as administrator". All the sounds played correctly. Here's the relevant part of the log. you can see that I get status 1, meaning it is playing, and I get the relevant messages after each sound showing it completing. 132757 LogOptions changed, now 00000000 00000211 133131 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 141056 Memory in use: 1172Mb, Avail=2924Mb 201241 Memory in use: 1235Mb, Avail=2861Mb 216950 Sound: Ref 37, via IPC: Cmd=1, Wave="E:\FSRAAS\Approaching.wav" 216950 Sound: Id 256, PlayNow("E:\FSRAAS\Approaching.wav") 216950 Sound: Id 256, PlayTheSound("E:\FSRAAS\Approaching.wav") 216950 Sound: EnumDevice=Primary Sound Driver 216950 Sound: EnumDevice=Speakers (5- High Definition Audio Device) 216950 Sound: EnumDevice=Digital Audio (S/PDIF) (5- High Definition Audio Device) 216950 Sound: EnumDevice=Realtek HDMI Output (Realtek High Definition Audio) 217075 Sound: Ref 37, IPC: Status Response=1 218011 Sound: Id 256 DeActivate: sound not playing now ... 218011 Sound: Id 256 EndPlay: releasing buffer 218011 Sound: Id 0 EndPlay: all done! 218074 Sound: Ref 6, via IPC: Cmd=1, Wave="E:\FSRAAS\06.wav" 218074 Sound: Id 256, PlayNow("E:\FSRAAS\06.wav") 218074 Sound: Id 256, PlayTheSound("E:\FSRAAS\06.wav") 218120 Sound: Ref 6, IPC: Status Response=1 219306 Sound: Ref 40, via IPC: Cmd=1, Wave="E:\FSRAAS\Left.wav" 219306 Sound: Id 255, PlayNow("E:\FSRAAS\Left.wav") 219306 Sound: Id 255, PlayTheSound("E:\FSRAAS\Left.wav") 219322 Sound: Ref 40, IPC: Status Response=1 219337 Sound: Id 256 DeActivate: sound not playing now ... 219337 Sound: Id 256 EndPlay: releasing buffer 219337 Sound: Id 0 EndPlay: all done! 219961 Sound: Id 255 DeActivate: sound not playing now ... 219961 Sound: Id 255 EndPlay: releasing buffer 219961 Sound: Id 0 EndPlay: all done! 241240 Sound: Ref 38, via IPC: Cmd=1, Wave="E:\FSRAAS\On Runway.wav" 241240 Sound: Id 256, PlayNow("E:\FSRAAS\On Runway.wav") 241240 Sound: Id 256, PlayTheSound("E:\FSRAAS\On Runway.wav") 241287 Sound: Ref 38, IPC: Status Response=1 242566 Sound: Id 256 DeActivate: sound not playing now ... 242566 Sound: Id 256 EndPlay: releasing buffer 242566 Sound: Id 0 EndPlay: all done! 242644 Sound: Ref 6, via IPC: Cmd=1, Wave="E:\FSRAAS\06.wav" 242644 Sound: Id 256, PlayNow("E:\FSRAAS\06.wav") 242644 Sound: Id 256, PlayTheSound("E:\FSRAAS\06.wav") 242659 Sound: Ref 6, IPC: Status Response=1 243845 Sound: Ref 40, via IPC: Cmd=1, Wave="E:\FSRAAS\Left.wav" 243845 Sound: Id 255, PlayNow("E:\FSRAAS\Left.wav") 243845 Sound: Id 255, PlayTheSound("E:\FSRAAS\Left.wav") 243861 Sound: Ref 40, IPC: Status Response=1 243861 Sound: Id 256 DeActivate: sound not playing now ... 243861 Sound: Id 256 EndPlay: releasing buffer 243861 Sound: Id 0 EndPlay: all done! 244469 Sound: Id 255 DeActivate: sound not playing now ... 244469 Sound: Id 255 EndPlay: releasing buffer 244469 Sound: Id 0 EndPlay: all done! 245311 Sound: Ref 54, via IPC: Cmd=1, Wave="E:\FSRAAS\Flaps.wav" 245311 Sound: Id 256, PlayNow("E:\FSRAAS\Flaps.wav") 245311 Sound: Id 256, PlayTheSound("E:\FSRAAS\Flaps.wav") 245343 Sound: Ref 54, IPC: Status Response=1 246528 Sound: Id 256 DeActivate: sound not playing now ... 246528 Sound: Id 256 EndPlay: releasing buffer 246528 Sound: Id 0 EndPlay: all done! 251021 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 251021 Sim stopped: average frame rate for last 117 secs = 29.7 fps 261816 System time = 04/03/2014 15:54:19, Simulator time = 15:53:01 (15:53Z) 261816 *** FSUIPC log file being closed Average frame rate for running time of 170 secs = 28.2 fps G3D fix: Passes 13920, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 136 Allocs, 136 Freed ********* FSUIPC Log file closed *********** Hope this helps. I really don't think I can do any more. Maybe your two major problems are linked, maybe not. First off, though, I suggest you delete all your FSRAAS stuff, download version 2.0, just place its folder somewhere near FS (not on the desktop), and see how that goes. I would be wary of using the desktop for whole folders of programs. Folders of shortcuts, yes, but not programs and wave files. I do see that your "r4.cvs" file is really "r4.csv", and you should consider replacing that with a freshly generated one if you have any add-on airports. Pete -
FSUIPC.ini does not recognize soundcard
Pete Dowson replied to Mr.V's topic in FSUIPC Support Pete Dowson Modules
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 -
FSUIPC.ini does not recognize soundcard
Pete Dowson replied to Mr.V's topic in FSUIPC Support Pete Dowson Modules
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 -
Throttle configuration with FSUIPC4
Pete Dowson replied to A330Fan's topic in FSUIPC Support Pete Dowson Modules
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 -
Offset 0x11BA (g force) wrong?
Pete Dowson replied to Jens82's topic in FSUIPC Support Pete Dowson Modules
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 -
Throttle configuration with FSUIPC4
Pete Dowson replied to A330Fan's topic in FSUIPC Support Pete Dowson Modules
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 -
Reversers conflicting with Throttles :-(
Pete Dowson replied to Chris Catalano's topic in FSUIPC Support Pete Dowson Modules
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 -
FSUIPC.ini does not recognize soundcard
Pete Dowson replied to Mr.V's topic in FSUIPC Support Pete Dowson Modules
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 -
Detecting mid air refuel
Pete Dowson replied to Joaogl's topic in FSUIPC Support Pete Dowson Modules
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 -
Offset 0x11BA (g force) wrong?
Pete Dowson replied to Jens82's topic in FSUIPC Support Pete Dowson Modules
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 -
MakeRunways Centre Frequencies
Pete Dowson replied to ByteG's topic in FSUIPC Support Pete Dowson Modules
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
-
FSUIPC.ini does not recognize soundcard
Pete Dowson replied to Mr.V's topic in FSUIPC Support Pete Dowson Modules
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
-
I Still Have Dissapearing Controllers
Pete Dowson replied to G Fisher's topic in FSUIPC Support Pete Dowson Modules
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 -
FSUIPC.ini does not recognize soundcard
Pete Dowson replied to Mr.V's topic in FSUIPC Support Pete Dowson Modules
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 -
I Still Have Dissapearing Controllers
Pete Dowson replied to G Fisher's topic in FSUIPC Support Pete Dowson Modules
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 -
FSUIPC.ini does not recognize soundcard
Pete Dowson replied to Mr.V's topic in FSUIPC Support Pete Dowson Modules
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