Mike...

Pete, thanks a lot! I've downloaded the update, hope to test it out later today. :D

One guy asking about it hardly makes it important. Even if it is yours truly. :lol: To answer your question, neither. It's just something that I was confronted with due to several factors coming together and I decided to post about it. Others may not care enough about it to persue the matter, it is a small thing after all, or it may not be an issue for them because of the way they sim. I do not know. I do know that I can not get it to work correctly consistently, which seems to be supported by tdragger's posts, and I would simply like another way to control window size and position. That's all. So thank you for your consideration. :)

Well, in my case, I do go to the main window where I set everything up and then I hit, fly now. So all I'm seeing is "There does appear to be a bug in FS2004 where these are overridden if you load the flight from the main UI" and "Okay, so it affects that as well. So you must re-load the flight to have it take effect. That's a bug". So two bugs. For me to circumvent those, I'd have to change the way I sim radically, increasing FS9's footprint (reloading flights, sceneries, AI) and making it more difficult for addons to establish their presence in the sim, such as ActiveSky, which loads as soon as a flight is ready (so flight is ready, AS loads, I have to reload to get the correct size and position, AS loads again). And that's not even considering Radar Contact, which is supposed to be started last, so after the weather for example. Can FS correctly establish Radar Contact's window size and position, before RC is even present in the sim? It would be so much easier if I could change the default FSUIPC values for the window size and position. Just a simple addition to FSUIPC.ini, something like "DisplayWindowUniCoords=1500, 1200, 5192, 2000", sticking to FS vernacular (and using default ATC values in this specfic example). (I'm not interested in undocked coords, but others might be.) If there are three window uses, perhaps there could be three values DisplayWindow1UniCoords, DisplayWindow2UniCoords, etc... with a little explanation of the different window uses. I do not know how difficult it would be programmatically, but it would definitely be a very welcome addition to the already rich array of features that comprise FSUIPC. :)

Hello again, I just got Radar Contact and I've been looking into the position and size of its in sim window. Ideally I want it to have the same size and position as the default ATC window (I always liked it there). I have done my homework and know its position and size can be saved, but I can not get it to appear correctly consistently. This odd behavior seems to be supported by several posts of one tdragger (formerly of ACES?!) at Avsim (http://forums1.avsim.net/index.php?showtopic=55645). So I was wondering, where does the Radar Contact window, which is the (or a version of the) FSUIPC Display window, get its initial size and position from? And is there any way to change that default size and position? (It now appears about a third down on the left side of the screen as a relatively small window.) Is this something determined by FSUIPC internally or it is done by FS9? Is there any way you could allow the user of FSUIPC to change that initial size and position? That would really be great. :wink:

I can now confirm that the joystick does operate without power as well. Perhaps power is only needed for Force Feedback.

All power saving settings are turned off, including 7's USB Selective Suspend.

Let me put it differently, the usb cable of the joystick is always plugged in. The power isn't always turned on. So I was wondering if without that power, the computer still sees the device? I'm guessing not. Which may have given identification issues. My previous joystick was always connected (to same port) and didn't need power, so as far as the computer was concerned, it was always there, always the same, no likely id problem. I do always turn on the power before starting the sim. As far as this not being the same as Pete's issue, he's probably right. The problem I have is not unique to this joystick however. I didn't put two and two together until last night, but my previous joystick was the MS Sidewinder, it worked with the sidewinder software (4.0) or whatever it was called. It included a "calibration" utility and every time I opened it, the throttle would indicate 100%, so full throttle, despite the lever's position. It wasn't until moving the lever, that the correct value was displayed. Oh well. :wink:

FYI, this is what the thing looks like: http://www.logitech.com/index.cfm/gamin7&cl=us,en Without the Logitech Gaming Software active (though still installed), sensitivity is somewhat different, but the same problem occurs. With or without LGS, I've now been able to consistently avoid the issue by first moving the joystick thoroughly. After that, going into slew, everything behaves normally. As for what causes it precisely, I have no clue and no desire to find out to be honest. I'm already glad I know what to do to avoid it, after all this testing. I'll finetune the calibrations a bit and then I'm gonna do something else, anything else. :lol: Thanks for your patience and help. :) Edit: simultaneous post/edit. As per above, maybe tomorrow. :wink:

Yes, definitely. Okay. Here's what I've found. That appears to stay the same after suqsequent boots and disconnections of the joystick. Good news I believe. I changed Sensitivity to max and Null Zone to min. And added the stick sensitivity line to the cfg file (when FS wasn't running and I made no changes through FS's interface since). Those settings remain after boots and FS starts. I calibrated both slew (in slew flight mode) and non-slew (in regular flight mode), added slopes according to my preferences. Although as I understand it better now, I will (also) have to change the center values (which are currently all +/- 512). But anyway, everything was fine as before, restarted the computer, etc... Back to the sim, slew mode, crazy joystick. I went into FSUIPC and looked at the IN and OUT values. Back/forward and left/right were changing normally as far as I could tell. However, the heading change wasn't. Even with a small twist of the joystick, both IN and OUT went straight to the max/min value. So either 0 or +/- 16000, nothing in between. And that was reflected by the crazy spinning around. Went out of slew, then back to FSUIPC. Most values behaved normally, except for the rudder, from 0 straight to the extreme. However, when twisting the joystick back to center position, the values suddenly came alive and behaved normally. Exit FSUIPC, back into slew, no more crazy spinning around... I think that is happening to me as well. Although with another axis and not exactly the same, but still. The thing is, since I've been fixating on slew, I've always gone straight into slew mode. I'm now gonna test to see if the same thing happens, if I first move the joystick every way possible in normal flight mode. I have a feeling I will see no crazy slew spin after that, but I will check. I may also try with and without the Logitech Gaming Software.

Exactly, but this joystick seems a bit flaky especially when it is centered, more so than my previous joystick. As my hand merely rests on it, it is already slightly moving and for example sending an aircraft to the side when taxiing on a straight taxiway. To counter that, I increased the dead zone, so that I really have to move the joystick in order to get the aircraft moving. Same applies to the slew mode. I want to have to move the joystick significantly, before it moves the aircraft. To be honest, I do not fly by hand much, I have an auto pilot for that. So I'm most interested in getting accurate ground behavior with a firm-ish grip on the joystick. I don't want to be afraid to touch the thing in fear of looking like a drunk pilot. :lol: As to where I should make the necessary changes, that doesn't really matter to me, as long as it's working. So if I have to go to FSUIPC for that in favor of FS itself, so be it. I will check and verify. The confusion on my part remains. On one hand you say max sensitivity and min null, to get the most precise results. In other words, one influences the other. On the other hand you say, FSUIPC calibration has nothing to do with the FS9.cfg file. Sensitivity and Null Zone values are saved in the FS9.cfg file, as the various "AXIS_SCALE" and "AXIS_NULL" entries. I copied the section to illustrate my settings. If one has nothing to do with the other whatsoever, then surely, Sensitivity and Null Zone settings are completely irrelevant?! :? What I did was calibrate, set slopes. OK. Then back to FSUIPC, reset. OK. Then after closing FS, in the FSUIPC.ini file, the slope values (5 in my case) would still be there, I thought that was odd, so I mentioned it. No problem. Well, I'll go and check some things now. I'll be back with my findings.

I didn't say 100% dead zone, I said the option is set to 100% or full right as you put it... Obviously... No, but I never said such a thing... I thought that maybe the joystick was being incorrectly identified after a boot. Now perhaps I misunderstood the User Guide, but I thought that having a letter assigned, either manually or with the auto option, actually decreases the chance of incorrect identification. As in the values I list later in my post? What differences? Between IN and OUT? Yeah, what do joystick settings from the FS9.cfg file have to do with joystick calibration? I did my best to provide as much information as possible from the start, so you wouldn't have to ask me a bunch of questions. If some of that information is of no use to you, fine, but you don't have to rub it in, nor put words in my mouth. I find your tone unnecessarily unpleasant and instead of getting of the bottom of this, I now find myself refuting you, which doesn't help either of us. I quote from the User Guide: "Go to the FS joystick options and make sure you have the sensitivity at maximum and the null zone at minimum. Any other setting will reduce the range of your joystick and make FSUIPC‘s more accurate calibration less effective." "Most certainly should"? "There's no point"? "Operate correctly only"? Or "undermining it somewhat"? "Reduce the range"? "Less effective"? Let me get one thing straight. What is it? Is it absolutely one hundred percent guaranteed only to work with max sensitivy and zero null? Or should it work, merely diminishing the effectiveness somewhat? And how does that relate to it working for me one moment, with those settings, but not the other? I have deleted items from the ini file yes, to make sure everything was reset for another try. It may just have been my imagination, but using the reset buttons at one point, didn't reset the slope values. Calibration was reset, but the slope values were still there. Perhaps those slope values are only active with calibration values? Or they are reset when new calibration starts? Yes, but it seems like overcomplicating things to me. Apart from the axes, I have also considered using FSUIPC to program my buttons, but the Logitech Gaming Software (LGS) is handling that perfectly now and it has a neat export/import tool. And my Force 3D Pro is a Force Feedback joystick to boot, something not supported by FSUIPC. What I'll do after lunch is the following, set sensitivity to max and null to min, and use the STICK_SENSITIVITY_MODE=0 setting. We'll see what happens.

Hello there, Something's not quite right. For some reason, calibration is not being applied properly (after starting my computer anew). I have a Logitech Force 3D Pro since a couple of weeks, it needs power in addition to a USB connection. I do not always have its power on and so the joystick is not "connected" to my computer all the time, I think. I also have the Logitech Gaming Software (LGS) installed and it's working fine as far as I can tell. There's one option I'm not sure about, "Switch selected device to ID 1", though my problem seems to happen with and without the option enabled. It goes kinda like this. I start my computer, log on, turn on the power of the joystick and start the LGS. Everything fine so far. Then I start FS9. Its sensitivity and dead zone options are set to simplified (I think it's called, so same setting for all axes), former set to about 50%, the latter to 100%. I am aware of the user guide recommendations, but these settings seem to work best for this joystick. In other words, this gives a pretty good result in the sim already. I use FSUIPC (3.966, though my problem is not unique to this version) to then finetune it all. When FS9 is running, I switch to slew mode and calibrate on the slew tab of the calibration section. (I make a lot of precise slew movements when I'm editing Afcads, so slew needs to be calibrated properly.) Calibration works fine (I do not calibrate altitude change), add a slope of 5 to the other three, click on OK, everything works exactly as I like it! I then close FS9 (end flight, then exit) and shut down my computer. Then I start it up again and check both FS9 and FSUIPC config file to verify the settings, they are all there and correct as per my actions above. I don't make any changes. I repeat the same steps to get the sim running, switch to slew mode and then the problems start, If I as much as point or blow at my joystick, the default Cessna starts moving. If I twist it either way, the Cessna starts spinning like crazy. Same with the other movements, it moves great distances with only gentle movements of the joystick. Why is this happening? Everything was fine when I left FS, the settings/numbers are there in the config files, yet the joystick is out of control... I've read through the user guide about calibration, I thought that maybe setting AutoAssignLetters to Yes would help, no luck. There are no other game devices on this PC. I'm currently using Windows 7, 32-bit and it was a clean install, about three weeks ago. Still "clean" today, no other issues, in fact, it has been a positive experience coming from XP. Now, when I close FS9 and then restart it without shutting down my computer, calibration seems to stick. If I close FS9, disconnect the power of the joystick, then reconnect and start FS, calibration seems to remain. But again, shut down my computer, start it up again, FS9, crazy joystick... Below are relevant settings from FS9.cfg: [JOYSTICK_MAIN {9FC5FA50-0906-11DF-8001-444553540000}] AXIS_EVENT_00=AXIS_AILERONS_SET AXIS_SCALE_00=63 AXIS_NULL_00=127 AXIS_EVENT_01=AXIS_ELEVATOR_SET AXIS_SCALE_01=63 AXIS_NULL_01=127 AXIS_EVENT_05=AXIS_RUDDER_SET AXIS_SCALE_05=63 AXIS_NULL_05=127 AXIS_EVENT_06=AXIS_THROTTLE_SET AXIS_SCALE_06=63 AXIS_NULL_06=127 BUTTON_DOWN_EVENT_00=BRAKES BUTTON_DOWN_REPEAT_00=1 BUTTON_DOWN_EVENT_01=VIEW_MODE BUTTON_DOWN_EVENT_02=ELEV_TRIM_DN BUTTON_DOWN_REPEAT_02=1 BUTTON_DOWN_EVENT_03=ELEV_TRIM_UP BUTTON_DOWN_REPEAT_03=1 BUTTON_DOWN_EVENT_04=FLAPS_INCR BUTTON_DOWN_EVENT_05=FLAPS_DECR BUTTON_DOWN_EVENT_06=KNEEBOARD_VIEW BUTTON_DOWN_EVENT_07=GEAR_TOGGLE BUTTON_DOWN_EVENT_08=VIEW_MODE BUTTON_DOWN_EVENT_09=GEAR_TOGGLE POV_MOVE_EVENT_00=PAN_VIEW POV_MOVE_REPEAT_00=1 [JOYSTICK_SLEW {9FC5FA50-0906-11DF-8001-444553540000}] AXIS_EVENT_00=AXIS_SLEW_SIDEWAYS_SET AXIS_SCALE_00=63 AXIS_NULL_00=127 AXIS_EVENT_01=AXIS_SLEW_AHEAD_SET AXIS_SCALE_01=63 AXIS_NULL_01=127 AXIS_EVENT_05=AXIS_SLEW_HEADING_SET AXIS_SCALE_05=63 AXIS_NULL_05=127 BUTTON_DOWN_EVENT_00=SLEW_RESET BUTTON_DOWN_EVENT_01=VIEW_MODE BUTTON_DOWN_EVENT_02=SLEW_ALTIT_PLUS BUTTON_DOWN_EVENT_03=SLEW_ALTIT_MINUS BUTTON_DOWN_EVENT_04=SLEW_PITCH_PLUS BUTTON_DOWN_EVENT_05=SLEW_PITCH_MINUS BUTTON_DOWN_EVENT_06=SLEW_BANK_MINUS BUTTON_DOWN_EVENT_07=SLEW_BANK_PLUS BUTTON_DOWN_EVENT_08=SLEW_FREEZE BUTTON_DOWN_EVENT_09=SLEW_RESET POV_MOVE_EVENT_00=PAN_VIEW POV_MOVE_REPEAT_00=1 And from and FSUIPC.ini: [JoyNames] AutoAssignLetters=Yes 0=Logitech Force 3D Pro USB A=Logitech Force 3D Pro USB [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 SlewSide=-4064,-512,512,4063 SlewAhead=-4064,-512,512,4063 SlewHeading=-4064,-512,512,4063 SlopeSlewSide=5 SlopeSlewAhead=5 SlopeSlewHeading=5 Would setting STICK_SENSITIVITY_MODE to 0 help? Not sure what the unwanted behavior is that the user guide mentions. I've also tried calibrating regular flight mode and that seems to work, but I've not tested it fully, I'm trying to concentrate on slew first. Values for regular calibration go from about -16000 to +16000, except for the throttle, which goes from about -4000 to +4000, like the slew values, not sure if those values are normal. Finally, I'd like to mention ActiveCamera 2004, specifically a problem I had with this joystick initially, the following is taken from the AC site's FAQ (http://www.anticyclone.be/faq.htm) Q: when I turn off the computer I get the closing program for FS9. In other words it has not closed when I exit Flight Sim some hours before. R: Due to a conflict with DirectInput on some computers the FS9.exe process is still running after FS 2004 is shut down. Therefore it was not possible to save the Active Camera settings in the setup menu. Download the fix (see the Download page at http://www.anticyclone.be). This dll fixes the issue. Note that you will no longer be able to assign Active Camera events to any joystick button. My FS9.exe did get stuck, I applied the update, problem gone. But perhaps some issue still remains?! Who knows anymore... Sorry for the long post and perhaps I'm missing something, but I'm all out of ideas, big headache though. :lol: You can say a lot about Microsoft, but my previous Microsoft SideWinder Precision 2 joystick never gave me any trouble!

Very odd, knowing me, I copied that entry from the PDF, so I'm not sure where the typo is coming from. :D I've changed it and will test it on my next flight.

I'm using 3.90 and it seems as though the Cylinder Zapper doesn't work anymore. Regular Zapper is functioning. I'm not sure what is happening, I did find a discrepancy between the Advanced Users Guide (ZapCylinderAltDiff=n) and the value in the FSUIPC.ini file, which is ZapCylinderAlDiff for some reason. I will change it to Alt and see what happens. Not sure if it has anything to do with it. :?

And thank you!

3.8232 works fine also and you weren't kidding about the machine gun, I had a bit too much fun with that one. LOL! :oops:

Just finished a flight with 3.3831 to Heathrow, I was on final to 27R and there was an aircraft that was slightly behind and below me. He got clearance to land a couple of seconds after me. Before, I would've landed, tried to get off the runway as quick as possible and he would've been told to go around anyway. Now, I zapped him, landed safely, exited the runway at my own speed and I didn't hear the dreaded 'go around'. I'm sure it's all psychological, but it makes a world of difference! :lol: I'll try out the new build now.

Most of the time it's just one aircraft getting in the way, but recently I was sandwiched in between two aircraft and we were all heading to runway 4R at KJFK. So at that time, a ZapAll could've come in handy. Although it's hardly any trouble to just Zap twice and get the same result. I have to agree with you, it'd be best if that were a different control. Gotta say Pete, Mr. Downson, I have heard the stories, but now from personal experience I can say your continuing efforts on FSUIPC (for FS9) are most appreciated. Your commitment is truly unparalleled. Enough with the brown-nosing, I'll go set up a flight now and see how it works. :wink:

I use FS9. And I know I can use the Traffic Toolbox SDK to delete, but then I would have to pause the sim, open up the explorer, delete and resume. And deleting the right aircraft isn't all that straightforward or maybe I'm doing it wrong.

LOL! Realistic excitement, I'm all for it, but these AI pilots... :lol: By the way, I use this TCAS in all my aircraft. And I fly with 100% fully customized AI, Ultimate Traffic as a base, with updated models and flightplans, then all Ultimate GA and Military AI Works packages. That makes for really busy skies.

Well, you can see it, on TCAS. And hear it on ATC. And you know how AI behaves, so why not preemptively zap what is with pretty great certainty gonna mess up your (short) final. To me it seems pretty useful functionality. Pete, do you fly a lot with 100% AI to busy airports? No matter how good the Afcad is, no matter how well you've got AI Smooth running or AI Separation, there will always be conflicts and those conflicts aren't always going to be right in front of you. Anyway, thanks for listening. If only MS would've addressed these issues. Hopefully they will in FSXI, but I'm not all that optimistic.

LOL! I know. But anyway, the cylinder would be vertical. And the user aircraft would be at the very center of the cylinder. So simplifying, how much of a distance is there between AI and user two-dimensionally, so just looking at coordinates. But instead of directly in front, it's 360 degrees around the user aircraft, with the user in the middle of that circle. But then not only zap those aircraft that are within that circle, but also the AI up to an equal distance above and below the user altitude. With the radius and height of the cylinder defined by the user. It doesn't need to be huge, say the radius is 1 NM, the height 1000ft. That's means there is a zappable area of 1NM in any direction of the user and 500ft below and 500ft above. The real issue is, AI annoys at the most inconvenient times. And most of the time, you can predict this behavior with the help of TCAS, by listening to ATC and also by looking at Traffic View Board for example (I have it installed as a gauge in all my aircraft). My suggestion would allow me to zap with a little more freedom and not when I'm on short final and have enough to do already. I understand if this is beyond the scope of FSUIPC, it was just an idea I had. :wink:

I use the default settings and I haven't tried changing them. Don't think it'll make a huge difference though. "Note that you cannot change the acceptance angle explicitly. It is adjusted automatically, in linear inverse proportion to the change in the range—so with a larger range you would need to point the aircraft nose more accurately." It's already unforgiving, in my opinion. If I would increase the range, it would become more so if I understand the quote correctly, if I would decrease it, same thing, because I don't want to zap only what is right in front of me, but also AI say two or three miles in front of me when I know they won't make it off the runway in time. So I rather liked my suggestion. No worries about angles, nose pointing and whatnot, if it's in the cylinder, it's gone. I can see some people preferring the current system, so perhaps you can give users the option, old style, new style. But I definitely see the potential of my approach as well.

Like the feature, but it's a bit on the strict side. It took ages for me to get an aircraft out of the way that was right in front of me on final. Would it be possible to change the zapper in such a way that it would delete any AI aircraft within a user defined cylinder, where the user aircraft is in the precise middle of that cylinder? Two changeable values, diameter and height of the cylinder. That's what I call a real traffic zapper. :lol: You see, often I'd like to get rid of an aircraft directly behind me on final as well. And well, sometimes AI can be on top of or below you. So quite hard to zap with the current system. This is for FS9 by the way.