Luke Kolin

Why? There are offsets that list flap positions in degrees (multiplied by 512) that I use which work for the vast majority of aircraft. The config file doesn't seem very extendible. Cheers! Luke

I think that either you haven't done everything that the manual says, or you don't have a working network configuration for WideFS or you have a firewall blocking something. Almost certainly. Cheers! Luke

It could be. I raised the volume of the source WAV file and didn't notice a difference, but I didn't restart the sim between times. I'll poke around a little more - I'm reasonably confident that I changed the ID that I passed to FSUIPC on the play call each time, but not 100%. Thanks for the information. Cheers! Luke

I am playing sounds in the sim via the offsets at 0x4200 and above, but the volume seems very low compared to the cockpit and engine noise. I have tried adjusting all of the FS sound volumes to see if this can be raised, but it doesn't appear to be. Is there any way via this interface that the volume can be adjusted? Cheers! Luke

FWIW I read around 50 offsets several times a second without any sort of performance issues from C#. Cheers! Luke

Looks like an FTG-ACARS failure. Luke

??? I think Pete just asked that you not start ActiveSky, not to remove it. If you're getting blue screens, you're having hardware issues, or a bad video driver. Most software won't tax a modern PC enough to trigger an issue, but FSX certainly can. Both FSX and FS9 work quite nicely with Win7. I think there's something specific to your PC that's causing your issues. Cheers! Luke

What specifically do you want to do with it? You probably shouldn't have paid for it unless there was a specific feature you wanted to enable. Luke

Huh? It's just compiled code. All executables are like that. Cheers! Luke

ALT-ENTER if I recall correctly. Cheers! Luke

Likely the opposite - something messed up with your ISP. Cheers! Luke

The .NET framework appears to be fine. This looks like a program error. What is IYP Trial? Cheers! Luke

No. Cheers! Luke

I fear that at times my understanding of low-level data exchange is not what it used to be. Dividing the whole 64-bit integer by 65536.0 makes perfect sense to me now, but didn't occur before. Cheers! Luke

That's what I was missing. Thanks! I think you've confused me with someone else. Cheers! Luke

On this topic, assuming I've read the value in 0570 into a 32-bit integer, what factor do I multiple (or divide) it by to get the fractional component, which I will then add to the 32-bit integer I read from 0574? Cheers! Luke

... as am I - might oldest turns eight today. I'll be in touch shortly. Thanks! Cheers! Luke

I am looking to put together a commercial software package that would rely on FSUIPC for an interface to FS. Pete, how would I go about contacting you privately to discuss this? Cheers! Luke

Thanks, that's helpful to know. Is there any way that this error message can be triggered if no registration key is supplied, and the clock is merely set incorrectly? Cheers! Luke

Just to confirm, that's with 3.911? If so, that's great to hear. I loaded the iFLY just now without issues so that's good to hear. Also makes the mystery more interesting to fix. :) Cheers! Luke

I have been receiving reports from users that have installed FSUIPC 3.911 that the PMDG MD-11 for FS9 is reporting this version as "too old", and advising them to use 3.81 or above. I've also heard this about the iFly 747 panel. I don't own the PMDG, but I'm going to test this with the iFly later today. Has anyone else heard about this, or has the latest FSUIPC interim release working with these aircraft? Cheers! Luke

Sorry I have not gotten back to you sooner, Pete. It's been chaotic here. The FS9 implementation certainly works "correctly" in 3.908, and I think the FSX does. My memory is giving out. Cheers! Luke

I downloaded the guides and example LUA plugins and was able to get something basic cobbled together in around 30 minutes. You deserve a hearty "thank you" for making things so easy to delve into from this perspective. So thank you! Here's the data I logged. I had a 23ms sleep interval, and I'll give you the second I took off, as well as my landing. It's a VistaLiners 727 out of JFK 4L to LGA 31, my standard test flight. The landing is more interesting (but I figured I'd include the takeoff as well if anyone was interested). What's interesting is in both cases (I bounced my landing) the peak Gs don't seem to occur until about 50-75ms after FS detects we're on the ground. I'll try an FSX run, assuming I can do this with an unregistered FSUIPC4. (I only have FSUIPC3 registered). If you want/need any other data, feel free to let me know. Cheers! Luke msecs,timeL,ias,onGround,takenOff,G 45563,17:48:27,154,1,0,0.976 45578,17:48:27,154,1,0,0.976 45610,17:48:27,154,1,0,0.976 45641,17:48:27,154,1,0,0.974 45656,17:48:27,154,1,0,0.974 45688,17:48:27,154,1,0,0.974 45703,17:48:27,154,1,0,0.974 45735,17:48:27,154,1,0,0.973 45750,17:48:27,154,1,0,0.973 45781,17:48:27,154,0,0,0.854 45797,17:48:27,154,0,1,0.854 45828,17:48:27,154,0,1,0.741 45844,17:48:27,154,1,1,0.762 45875,17:48:27,154,1,1,1.091 45891,17:48:27,154,1,1,1.091 45922,17:48:27,155,1,1,1.411 45938,17:48:27,155,1,1,1.235 45969,17:48:27,155,1,1,1.008 45985,17:48:27,155,1,1,1.008 46016,17:48:27,155,0,1,0.922 46031,17:48:27,155,0,1,0.870 46063,17:48:27,155,0,1,0.858 46078,17:48:27,155,0,1,0.858 46110,17:48:27,155,0,1,0.877 46125,17:48:27,155,0,1,0.896 46156,17:48:27,155,0,1,0.915 46172,17:48:27,155,0,1,0.915 46203,17:48:27,155,0,1,0.931 46219,17:48:27,155,0,1,0.947 46250,17:48:27,155,0,1,0.963 46266,17:48:27,155,0,1,0.963 46297,17:48:27,156,0,1,0.979 46313,17:48:27,156,0,1,0.994 46344,17:48:27,156,0,1,1.006 46360,17:48:27,156,0,1,1.006 46391,17:48:27,156,0,1,1.019 46406,17:48:27,156,0,1,1.032 46438,17:48:27,156,1,1,1.045 46453,17:48:27,156,1,1,1.045 46485,17:48:27,156,1,1,1.123 46500,17:48:27,156,1,1,1.123 46531,17:48:27,156,1,1,1.125 46547,17:48:27,156,1,1,1.125 297766,17:52:38,125,0,1,1.046 297797,17:52:38,125,0,1,1.046 297813,17:52:38,125,0,1,1.046 297844,17:52:38,125,0,1,1.046 297860,17:52:38,125,0,1,1.046 297891,17:52:38,125,0,1,1.046 297906,17:52:38,125,0,1,1.045 297938,17:52:38,125,0,1,1.045 297953,17:52:38,125,0,1,1.045 297985,17:52:38,124,0,1,1.045 298000,17:52:38,124,0,1,1.045 298031,17:52:38,124,0,1,1.045 298047,17:52:38,124,0,1,1.045 298078,17:52:38,124,0,1,1.045 298094,17:52:38,124,0,1,1.043 298125,17:52:38,124,0,1,1.043 298141,17:52:38,124,0,1,1.043 298172,17:52:38,124,0,1,1.043 298188,17:52:38,124,0,1,1.043 298219,17:52:38,124,0,1,1.043 298235,17:52:38,124,0,1,1.043 298266,17:52:38,124,0,1,1.043 298281,17:52:38,124,0,1,1.042 298313,17:52:38,124,0,1,1.042 298328,17:52:38,124,0,1,1.042 298360,17:52:38,124,0,1,1.042 298375,17:52:38,124,0,1,1.040 298406,17:52:38,124,0,1,1.040 298422,17:52:38,124,0,1,1.040 298453,17:52:38,124,0,1,1.038 298469,17:52:38,124,0,1,1.038 298500,17:52:38,124,1,1,1.037 298516,17:52:38,124,1,1,1.037 298547,17:52:38,124,1,1,2.224 298563,17:52:38,124,1,1,2.224 298594,17:52:38,124,1,1,3.259 298610,17:52:38,124,1,1,2.266 298641,17:52:38,124,1,1,1.037 298656,17:52:38,124,1,1,1.037 298688,17:52:38,124,1,1,0.878 298703,17:52:38,124,1,1,0.878 298735,17:52:38,124,1,1,0.880 298750,17:52:38,124,1,1,0.880 298781,17:52:39,124,0,1,0.880 298797,17:52:39,124,0,1,0.878 298828,17:52:39,124,0,1,0.877 298844,17:52:39,124,0,1,0.877 298875,17:52:39,124,0,1,0.875 298891,17:52:39,124,0,1,0.875 298922,17:52:39,124,0,1,0.874 298938,17:52:39,124,0,1,0.874 298969,17:52:39,123,0,1,0.874 298985,17:52:39,123,0,1,0.872 299016,17:52:39,123,0,1,0.872 299031,17:52:39,123,0,1,0.872 299063,17:52:39,123,0,1,0.872 299078,17:52:39,123,0,1,0.874 299110,17:52:39,123,0,1,0.874 299125,17:52:39,123,0,1,0.874 299156,17:52:39,123,0,1,0.874 299172,17:52:39,123,0,1,0.875 299203,17:52:39,123,0,1,0.877 299219,17:52:39,123,0,1,0.877 299250,17:52:39,123,0,1,0.877 299266,17:52:39,123,1,1,0.877 299297,17:52:39,123,1,1,0.875 299313,17:52:39,123,1,1,1.586 299344,17:52:39,123,1,1,1.510 299360,17:52:39,123,1,1,1.189 299391,17:52:39,123,1,1,1.189 299406,17:52:39,123,1,1,0.973 299438,17:52:39,123,1,1,0.955 299453,17:52:39,123,1,1,0.955 299485,17:52:39,123,1,1,0.992 299500,17:52:39,123,1,1,1.003 299531,17:52:39,123,1,1,0.992 299547,17:52:39,123,1,1,0.986 299578,17:52:39,123,1,1,0.986 299594,17:52:39,123,1,1,0.992 299625,17:52:39,123,1,1,1.002 299641,17:52:39,123,1,1,1.008 299672,17:52:39,123,1,1,1.008 299688,17:52:39,123,1,1,1.010 299719,17:52:39,122,1,1,1.008 299735,17:52:39,122,1,1,1.008 299766,17:52:39,122,1,1,1.008

That might be true. I think we each have the same doubts, just on different sides of impact. :) I suspect I'm getting a normal, rather than impact-related, value. Ah, dragging me into Lua kicking and screaming! :) I've suspected that I need to learn how to do this for a bit. I'll dig into it later tonight. Apologies in advance if I come back with a few silly questions. Cheers! Luke

Thanks for adding this into 3.907 so quickly. I did a brief test this evening and it seems to work accurately. I'm wondering, however, if it might be better to get the value at the first frame *after* the aircraft is on the ground, rather than updating while in the air. The latter value (and FSUIPC's current behavior) seems to work well for vertical speed, but I seem to get a sub-one value for G forces, whereas one would expect this value to be >1 on touchdown. Does this make sense? I recognize that the latter behavior is also significantly more complicated to implement, and I apologize. Cheers! Luke