Turbohead

Ahh, I see my suggestions helped. You have refrained from shouting. We can work on the profanity and insults in a later session :D I'm sorry, I forgot you guys don't observe our Thanksgiving. So, have a happy holiday for Christmas. PS, I previously omitted rule # 3. "One should never insult a paying customer". Have a great weekend Peter, and thank you for all of your help. I will enjoy the new button that we have programmed together. Mark

"You can do the same on a button by programming those control. Use a parameter of 1 on the Press and 2 on the Release." Why didn't you say that in plain english in the first place. It would have saved a lot of my time. You kept referring to it as Panel ID, not Paremeter. I saw no where it say "panel ID" in any of my previous post. My god man, you need to learn to read as well. And shouting only shows that you have no patience at all. I read your post, but you persisted to play "Cat and Mouse"! If you knew that answer, a simple (Control = Panel_ID_Toggle and Paremeter of 1) etc etc etc. We could both be eating Turkey by now!!! Granted, you are an expert. You know what you are thinking, but have a hard time understanding and conveying your thoughts. Your problem is, you assume that the user is as smart as you. If I spoke to my flight students in a manner in which you have spoken to me, I wouldn't have very many flight students. I have to tolorate the same as you do. Everyone is not an expert. Maybe you should learn to develope some interpersonal skills. Rule # 1, Never shout at a paying customer. Rule# 2, have patience, no matter what the circumstance. Rule # 3, If you do not understand the above, read rule # 1 and # 2 again. BTW (By the way) The button works now for the landing view. Have a great holiday Mark

I truely appreciat all of your help. You have to remember, I am a novice at this, you are an expert. It is easy for you. I figured as much on the heading. However, it was worth tring to accomplish the task. As for the Landing view, the following was in the panel.cfg file. Window09=Landing View [Window09] file=CJ1_MainLanding.bmp file_1024=CJ1_Main.bmp size_mm=1280,960 window_size_ratio=1.000 position=7 visible=1 ident=2 window_size= 1.000, 1.000 window_pos= 0.000, 0.000 This is what FSUIPC logged: 94422 *** EVENT: Cntrl= 66506 (0x000103ca), Param= 1 (0x00000001) PANEL_ID_TOGGLE 94422 *** EVENT: Cntrl= 66506 (0x000103ca), Param= 2 (0x00000002) PANEL_ID_TOGGLE At this point, you have not specifically said what goes in the parameter boxes. I'm still guessing at it! However, it does not display the proper panel for 09 in the paremeter. I have tried may different setting as you stated. Specifically the ones you mentioned, panel_id_toggle and, using various paremeter settings, for press and release. However, it nevers achieves displaying the landing view panel as the Eagle soft application accomplishes. Hopefully, as you mentioned, someone with better patience will chime in and help. Mark

Okay,,,,I agree...FSUIPC is using the same name that FS uses internally. HOWEVER, in the user interface, (Options, Controls, assignments) they use a "user friendly name" View-(Switch To Top Down) --- in their own words. The "actual" command that is sent from FS or FSUIPC may be worded differently than the FS menu's name. Thus, I have to go log and figuer out what was actually sent. As for the other function that I am trying to accomplish, The panel view command that I am looking for is is from Eagle soft. It is a landing view that is toggled from their panel with a mouse click. Quote from Eagle soft... "The "landing view" is assigned to Window09, which unfortunately isn't accessible via the keyboard...only Window00 through Window08 may be switched with Shift-1 through Shift-9..."" As for the "Center" Heading Bug set, Eagle soft provides a function "mouse click" that will set the heading bug to the current AC heading. I can set this in FSUIPC (heading bug set) and give it a paremeter. However, the result is, it will go to the parameter set. i.e 180, 270 or whatever. It will not go to the current heading the AC is on. Here is what was logged: 2204234 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 311 (0x00000137) HEADING_BUG_SET 2205047 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 311 (0x00000137) HEADING_BUG_SET 2205687 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 311 (0x00000137) HEADING_BUG_SET HEADING_BUG_SET 2791969 READ0 0564, 4 bytes: 2D 55 2F 00 2791969 READ0 056C, 4 bytes: 2F 69 5E C5 2791969 READ0 0580, 4 bytes: 41 1B 14 DC 2791969 READ0 0574, 4 bytes: 03 00 00 00 2791969 READ0 C000, 1024 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 02 Apprently, Eagle soft goes out, polls what the heading is, and then sets a parameter of what the current heading is. In this case, a heading of 311. I will continue to experiment. However, a little help in what I don't understand is helpuful with the frustraion of trial and error. M

Peter Peter Peter,,,,You must not be reading what I wrote. :D I agreed with everything you said. Eveything you said worked. Please read what I wrote before you start flogging. Besides, its Thanksgiving day :lol: I think I may have not used the exact terminology that you were looking for. Okay, Keystrokes. Yes, I realize that FSUIPC assigns a function for the selected keystroke. My bad was, I had previously assigned a keystroke in FSUIPC, and FS would not let me re-assign the same keystrole. And yes, once FSUIPC has it, FS will not see it. I have resolved that problem. As far as the names of functions, you are technically correct. You guys use the technical name, (coded name). FS uses "user friendly" names. And, I might know that if I were a programmer. However, it would be nice for the end user to to see something familar, without having to "Log" and interperate the meanings. Now that we have that out of the way, (and my learning curve is getting better), from what I gather, it appears that FSUIPC can send a string of just about anything. If the string is known? See, with a little patience, I can learn!!! So lets advance things little. The CJ that I fly has some single mouse click functions that are not keystrokes. For example, they use a mouse click to call up panel 0 (zero). "which is a special landing view with their panel lowered" They also use a mouse click to center the heading bug. Both being functions that FS can not replicate through button push or key stroke. I want to make the above functions available as a button push on my yoke. I did the logging, and it appears they use several parameters with the function. When I click their landing view, I get the following: Landing view clicked on: 150469 *** EVENT: Cntrl= 66506 (0x000103ca), Param= 1 (0x00000001) PANEL_ID_TOGGLE 150469 *** EVENT: Cntrl= 66506 (0x000103ca), Param= 2 (0x00000002) PANEL_ID_TOGGLE Landing view clicked off: 151938 *** EVENT: Cntrl= 66506 (0x000103ca), Param= 1 (0x00000001) PANEL_ID_TOGGLE 151938 *** EVENT: Cntrl= 66506 (0x000103ca), Param= 2 (0x00000002) PANEL_ID_TOGGLE So how, and can, I set that up in FSUIPC to be a button push from my yoke? I set the command to be button 8, then chose panel_id_toggle, but I am not sure how to set the 2 parameters. The panel_id_toggle worked, the scenery changed, but the panel did not relocate itself. So evidently, I am not setting the parameters correctly. Thanks,,,we'll get there eventually. Besides, the more you teach, the less I'l lhave to bug you. Happy Thanksgiving, This beats the hell out of watching American Football :roll: Mark

Okay, I just went and tested this, and the following is factual. If I use FSUIPC to assign a keyboard command, the the same function for FS keyboard commands will not be avilable. For example, I went into FSUIPC / Key Prsses / aircraft specific / and assigned "CTRL >." to be Brakes. At this point, I can not go into FS and assign brakes to be "CTRL >." FS apparently sees that something else already has that function. Apprently FSUIPC. Not that I would purposely try to do that, but that's why some of my keyboard commands were not functioning. I had forgotten that I had tried to program them in FSUIPC. I assume that FSUIPC got first shot at it :) Same with the CTRL S and W Command. I had previously tried to program those in FSUIPC, but could not find the functions I wanted listed in your drop down window. So, when I went to FS to try to program the function, FS would not let me do it. ((I had forgotten about the FSUPIC command that I was playing with previously.)) MY BAD !!! Thus, I eliminated the FSUIPC entries of CTRL S and W, and was able to program them in FS, with approproatiely named commands. That said, if I go to FS2004, Options, Assignments, I get a full list of available functions. One is named (View-Switch To Top Down) and it has CTRL S assigned to it. "CTRL S" shows an overhead view in the form of a zoomable view from high above the Aircraft. The other one in named (Panel on-off) and is asigned W. Basically, it is a wide view of the scenery with no aircraft panel parts. It toggles from to No Panel with instruments, to no panel and no instruments, and then back to panel and instruments. FS2004 exact terminology is: (CTRL S) "View-Switch to top down", (W) "Panel On-Off" These are the actual names listed in the FS2004 assignment lists. The FSUIPC equivillants are apparently: "View Type" "Panel Hud Toggle" If I try to find the FS2004 functions listed in the FSUIPC pull down lists, they are not there, or named something else. They are not listed as FS lists them. Thus, you can see the confusion! The FS functions and the FSUIPC Functions are apparently named differently. Unless I know what FSUIPC does for the FS names, I have to waste a lot of time experimenting. Granted, you are right about looking at the log etc., grabbing what happened, or using the numbers, and interpolate what happened. Then use the FSUIPC equivillant of the FS command. However, I don't think that is a very "user friendly" way of going about it. Why not just use the exact names as in FS? I guess I understand that you have offered more possibilites than FS, but it's seems like the long way around. I ran into that progamming the HAT switch on my CH Yoke. I had to go to FSUIPC, find out what the same FS sunction would be, and then program each of the eight positions individually, to do what FS does automatically. Anyway, I think I have everything back as it was, but I would like to know why the FS names and the FSUIPC Names are so differnt in the lists. Get some sleep M

What is JS ??? I uses the words "Joy Stick" in the same sentence, so I thought the abbreviation "JS" would be evident!!! :):):) I am using FS2004 and FSUIPC 3.93 Windows XP Pro. No corrupt files. The problem turned out to be, "CTRL S" was being used in FSUIPC while I was trying to find a comparative view for the FS function. Thus, I guess FS will not assign a duplicate entry. I deleted the FSUPIC entry and was able to assign the function in FS. CTRL W, Same. I had previously entered "CTRL W" in FSUIPC, and FS would not duplicate it. Thus I Deleted "CTRL W" from the FSUIPC, and was able to assign CTRL W in FS. BTW,,(By the way), the default FS command for "CTRL S" is "View -Switch To Top Down" I do not see an equivillent FSUIPC command for that. The default FS Command for "CTRL W" is "Panel On-Off" . I do not see an FSUIPC equillivent for that either. As a note, I think the keyboard functions were all working before I updated to FSUIPC 3.93, but I can't say that for sure. Thanks Mark

For some reason, I seem to have lost a lot of my keyboard commands. However, a few are still functioning. I noticed this when I set FS to not use it's joystick commands, and let the FSUIPC do the work. In fact, FSUIPC does a much better job of things as far as the JS functions I program all of my JS commands through the FSUIPC, and I have been able to program what I need without issue. I.E. heading bug, autopilot on off, brakes, flaps, throttle etc etc etc. Anyway, as mentioned, some of my KB commands are not working. I can not program them in FS, nor can I find a way to program them in FSUIPC. Actually, I see "how" to program them, but can't find the exact same function that FS does. It may simply be a naming issue equilivent. 1...KB command CTRL-S (top down view) doesn't work. 2...KB command W (front view with no panel) doesn't work 3...KB command . (brakes) dosent work ((However, . does work as a JS command)) Interestingly, functions like P for pause, S for cycle views doee work. Mainly, it's the ones listed above that I would like to have. Thus, I may be missing something, or do not know what FSUIPC functions produce the equivillent FS functions. But I still don't understand why FS won't let me change the above listed functions. Can anyone shed some light on this for me ? Thanks Mark

Thanks Pete.......I guess I'm just getting to old. Funny how something only a few years old is now so outdated :) Pretty soon, I'll have to start replacing mr refrigerator every six months :):):) Mark

Glitch is actually an old broadcaster's term. Flash may be more approproiate. Just as AS6.5 finishes it's update, and says "Compete" I get a quick screen flash. Almost if the monitor blinked for a milisecond. Maybe "quick refresh" is even a better term. Obviously, it is the "screen scenery change" to what weather was updated to be, but the flash happens on the entire screen, and not in the graphic out of the window. And, only on the monitor where the main AC panal is. The second monitor, (which is where I keep radios, throttles, ets) does not flash. I haven't checked to see if the flash happens in the 3D Cockpit or not. I mainly run in 2D Cockpit. Again, I would assume a smooth weather transition out the cockpit window. But it looks like the weather "snaps" to the updated data. It in fact happens precisely at the update, and it is almost as if the monitor can't handle the refresh. Briefly, as far as FS weather options, AS6.5 "suggests : 60 miles on the sight distance (Left on the fader) 30 miles on the cloud draw (mid fader) 100% on 3D clouds (Right) I may try full quality and see what that yields. However, claims are the performance will suffer as you mentioned. Thanks M

Okay, I am now up to FSUIPC 3.93 and updated AS6 to B552. I didn't see much differnce in 3.93 from the previous version. Or at least I didn't see any additional settings. I am assuming that most of the changes are under the hood :) So, here's the question, I am a bit confused in which setting would be approproaite with FSUIPC and AS6.5. Specifically in visablity control, and wind control. Both vendors recommend some settings that coud possibly conflict. After some experimentation, I had to end up using FSUIPC to control the taxi winds. It in fact does reduce the wind effect on taxi and take off. However, it only seems to get it down to about 2 knots. I can't seem to get it down to "no wind" result. As far as visabiltiy smoothing, I'm out to lunch on that one. I still seem to be getting some "pop up" weather, rather than a transition from one scene to another. I was under the assumption that the changes would be smoother. I've tried smoothing in both applications, but I still get the occasional pop up clouds. And finally, I do still have that quick screen glitch when the AS weather completes. It's just enougt to be an anoyance. I have posted in the AS forum, but no one has responded as to what may be causing the issue. If anyone has a particular set up that they think is really good, I am willing to try it. Thanks again M

Before I download and install 3.93, will my current settings (joy stick etc) transfer over to the newer version? After the 3.93 install, Is there anything special I need to do before moving forward with 3.947? Or can I just perform the installs back to back? Thanks again Mark

Would this be a free upgrade since I already have an earlier version? I didn't know 3.7 was not being supported. What does the newer "supported" version allow /add/fix/ etc? I don't like tinkering with things that aren't broken :) Finally, which version would be approproaite for FS2004 and XP Pro? M

I run FS2004 and Active Sky 6 on Windows XP Pro. A new Pentium Dual Core 2.5 gig and 2 gig of ram. I additionally run FSUIPC ver 3.70 I recently loaded FS, AS6, and FSUIPC after purchasing the new machine. I eventually got everything set up as close to what I previously had on an older machine. (Or as best as I can remember) I seem to be having a few small issues that I can’t seem to resolve between FS, AS6, and FSUIPC. I am not sure which may be causing the issue, or which product may be able to resolve the issue. Concerning Clouds and visibility, I am seeing the clouds “write on) in the distance, rather than a smooth transition that I previously had on the older machine. Additionally, when AS6 completes it’s refresh, I get a quick “screen glitch”. The glitch happens precisely after the refresh completes. I have the refresh set to 5 minutes. The glitch affects the entire FS screen, not just the weather out the window. Current FS settings: Sight Dis =60 miles Cloud Draw=50 miles 3D %= 100% Detailed Clouds –Coverage Density Maximum Current FSUIPC Settings: Clouds: Add Light Cirrus Occasionally Apply Icing=0 Visibility: Smooth Vis Change 10% every 30 sec Set Grad Vis from 5 up to 25,000 Upper limit 25,000 Misl: Allow Change to own FS weather= Checked Prevent Ext opt ctl=Un-checked Smooth Pressure =checked = 1 MB over 30 sec Smooth IAS = checked Current AS6 Settings: Online Update=Checked 5 minute Intervals Disable Vis graduation = unchecked Visibility Smoothing=Checked Enforce Vis Limits= min=0 max=59 FSUIPC Wind Smoothing=checked Limit Surface Wind=checked I have varied several of the above parameters, but can’t seem to eliminate the cloud draw issue , unless I set the cloud draw less than around 30 miles. However, that is a bit unrealistic visually to have the clouds limited in the distance. As far as the “Screen glitch” I can’t seem to make that issue go away. Unless, I do not run AS6. (FS weather does not cause any glitching either with a theme, user weather, or RW weather) I am wordering if there is a combination of setting amongst the products that may be causing a possible conflict. I admit I am a bit lost in understanding some of the terminology, and exactly what some of the functions actually do. I don’t remember seeing this "screen glitch" with my previous installation, but with the newer/better machine, I am running things in FS pretty much at max as far as scenery etc. Anyone have any suggestions? Mark

I agree about the lessons, besides, I usually get paid pretty good money for that :) I would assume that most of the FS team were RW pilots. The software is quite complex, and modeled very well to the RW. Additionally, I would assume that there are some limitation on what FS can accomplish. I have never flown FSX. So there may be a differnence in the two formats. I wish I knew enough about the guts of FS to play around. I totally don't understand the friction points, or contact points as I think you guys call it, and I am sure there is much more to it than the CG pivotal axies. But it would be interesting to investigate why the weather vane phenomenon behaves as it does. For grins, I did the same test at altitude. It appears that the same issues exist in flight. It's just not as noticable because there are no direct visual references such as a runway etc. But if you watch the track in cruise closely, you will pick up on the corrections. The next student I use the FS Sim with, I'm going to turn off the X wind correction, and see if they detect the effect. I think it will be intersting to see the results. Anyway, sorry to get off track from the original thread. However, if anyone following this thread has FS2004, I would love to have some feedback. Thanks again for your help. Mark