Jump to content
The simFlight Network Forums

vgbaron

Members
  • Posts

    210
  • Joined

  • Last visited

Posts posted by vgbaron

  1. Ah. I got it from the Sim Samurai Tutorial in your download links:

    Restoring Default FS Control

    To restore your default flight simulator control assignments for any device simply unplug the device from its

    current USB port, wait a moment, and then re-plug the device in (while computer is on) into the same USB

    port. Then start your simulator. If your controls are dead also look at the FS Options\ Controls\ Joystick

    option and make sure you have your joystick enabled. If this doesn’t work then unplug/ re-plug the device

    in again while the sim is running. Either method will most certainly get the USB device back to its default

    I read that to imply that the FSUIPC settings are negated.

    Regarding the GUID 'reset' - in the past, when I've unplugged a device and plugged it back in, possibly to another port, the GUID has changed and all the settings in the standard.xml do not work unless I manually edit the GUID.

    So my logic was that in the above from Sim Samurai - the action would change the GUID and I would lose them but if you say they are not "lost" that's what I need to know.

    I almost NEVER unplug my USB controls but in the few times I have, it's been a pain in the arse ( not relating to FSUIPC).

    Think I misunderstood something. :)

    Thanx!

    device assignments provided by the simulator.

  2. A little more clarification please, Pete - in reading the documentation, it states that to reset to fsx defaults, unplug and replug controller into USB port. I'm assuming this resets the GUID and mucks up the standard.xml file. What I cannot determine is how you get the FSUIPC setings back if you have to unplug and do not want to reset. possibly haven't gotten that far into the documentation yet. I see reference to ID'ing the controllers in the INI file. If I understand that correctly - assuming I've assigned an ID to the controller and the GUID gets reset, I just have to link the new GUID in the INI file with the "old" ID and FSUIPC will take care of the rest?

    Sorry to be so dense...

    Vic

  3. Can't determine if this is possible from th documentation but - I want to disable joysticks in FSX and handle all programming thru FSUIPC. I know how to set up the axis, buttons, etc. I've been reading up on profiles so that is clear.

    However - there are many switches and axis that are common to all aircraft. So if I program those items with profile unchecked and then program remaining controls to a specific profile - will FSUIPC combine the "generic" with the specific or do I need to program ALL buttons, etc in a specific profile?

    Hope this question makes sense - I'll continue to browse the forum and docs.

    Thanx,

    Vic

  4. Thanx Pete - profiles look like the way to go. I have a few a/c that I like to fly of varoius types -A2A P-51, Flight1 Mustang, Kodiak, etc - almost all different. Some with using a joystick and some using a yoke.

    that brings up a different question - Assuming I have a CH yoke and rudders and Throttle quadrant and an X52 stick connected to FSX system - I create profile for the P-51 using the x52 and for the Kodiak I create one using the yoke. Will there be conflicts doing this or would FSUIPC essentially "disable" the unused controller depending on profile chosen?

    Thanx again,

    Vic

  5. I am NOT near my flight computer or I could try this and find out myself but - when programming buttons and switches to individual a/c joysticks - after I program the functions and assign them to aircraft A - I now want to assign the same ones to aircraft B without repeating all the actions - what is the best approach?

    If it's as simple as just change the name of the a/c, I shall proceed to get a big towel and wipe the egg off my face - but I did say I am not near my flight system!

    :oops:

    Thanx!

    edit ; forgot I could RTFM online - found my aswer re profiles!

    Vic

  6. As I understand it, the 200nm limit is hard coded into Simconnect and deals with AI & MP. Been browsing some posts in various programming forums and no one has been able to bypass it. Was thinking that Simconnect must read the raw data from somewhere and cap it. Wondered if FSUIPC knew and could access that 'somewhere'. :)

    I'm guessing that Simconnect reads the raw data from the local machine but what it sends to the remote machines is capped at 200nm so the raw data is only available locally.

    Thanx,

    Vic

  7. WHen I first tried the calibration, a slight movement of the control would cause the aileron to fully deflect, sort of an on/off rather than a range. Tried the filter and problem resolved so I left it that way. Must have been something else because I turned off the filter for my last tests and everything worked as expected. I did change one thing, did not use max ranges for calibration. All in all, I've been trying all sorts of things and a/c and everything is working. I did reseat all the USB connectors so it's quite possible it might have been that also.

    In any case, for now, the problem seems resolved.

    Appreciate your time!

    have a good day.

    Vic

  8. Sorry about that - it's easy to forget that you're not looking at my screen.

    I am mainly interested in the Ailerons - in the calibration screen 1 of 11. With the yoke centered the REset in/out values are 0,0. After calibration the reset values are 0,0 and the SET values for MIN, Centre & MAX are -16193,0 +16065. Filter is checked. After flying a bit I notice sluggish controls and go back into the FSUIPC Calibration screen one

    Now, with the yoke centered the RESET in/out values are 5100,5122 if I move the yoke full left the values are 14287,14511 and full right -14257,14296 rather tyhan the +-16000 during the initial calibration. Now if I rapidly turn the yoke left/right a few times the RESET in/out will return to 0,0 and the max deflections will return to +- 16000 and the controls get crisp again. My first thought is sticky or dirty pots in the yoke but wonder if, in your experience, there might be other factors that could produce this type of change.

    Just to clarify, I do NOT have FSUIPC doing the Axis assignment, I am merely using it for calibration and the reading of values in this case.

    I hope that is a tad clearer.

    Thanx!

    Vic

  9. Hi Pete - I'm getting some data from FSUIPC that I don't understand. Using registered version, latest downloaded from the link in your message above. Using CH Yoke, I calibrated - SET boxes showed 0,0 and after calibration of the ailerons the deflection was +- 16something. All was well. During a flight I noticed that the controls were sluggish so I went back into FSUIPC calibration - in the aileron set, instead of a 0,0 it was about 5100,5100 and the deflections would range from 11000 to -13000. I'm pretty positive that there is no issue with the pots in the yoke so what else could have the 0,0 setting change to 5100,5100.

    fwiw, I moved the yoke left/right rapidly a few times and the set jumped to 0,0 and I recalibrated.

    I realize this is not a FSUIPC issue but hoping you can point me in the right direction to determine what caused the change.

    This behavior has repeated itself.

    Puzzled.

    Thanx,

    Vic Baron

  10. Hi Pete -

    Don't know if this is important or not so wil let you decide. Purchased FSCommander X from Aerosoft and the installer tries to install the 4.28 version of FSUIPC. It recoginized that I was running a newer version and said so and did not overwrite. Then I got a message to check that you were a "Trusted Publisher" because something could not be verified. Clicked OK then got a message 'Unable to register" and install ended normally.

    Fired up FSX and my version of FSUIPC is still registered and there seems to be no problems other than the strange messages.

    Thanx,

    Vic

  11. Hi Pete -

    In the FWIW department, I have been unable to manually generate the 'fog layer' so far. Setting visibility to 1/16 in FSX produces a nice soupy view but it's "not" the fog layer. WHen I slew above it and look down, it looks 'different'. Wish I could be more specific. I'll keep trying.

    Also, I'm not at my flight system right now but the version of FSUIPC that I'm using was downloaded three days ago from Schiratti's site.

    Vic

  12. http://forums.avsim.net/dcboard.php?az=c_id=38906

    Hi Pete -

    I started this thread at Avsim because I was searching for an answer to what I thought was a weather problem. There is another related thread, that seems to also indicate that the problem started after installing 4.25.

    Unfortunately, until I can find a way to manually generate the 'super fog' layer I can't really test it.

    Are you aware of any interaction of 4.25 that would cause this 'super fog' layer which causes all panels to disappear when descending into it?

    Thanx,

    Vic

  13. Ray,

    Truly what is inexplicable is Helge dropping off the face of the planet . This whole saga is very odd. No one really knows for sure. Why then is it so unresonable to question a so called post from him? Where is this post? And how do we know it is from him? The truth of the matter is we don't.

    Vid

    Simply put - who cares? FSNAV has been dead for quite a while and except for the grass roots support would have died long ago. Frankly, who*EVER posted the request has done the community a service. Let the darn thing die. It had it's day and was an exceptional product. Now, it's gone - stop beating a dead horse.

    FSNAV - R.I.P.

    Vic

  14. And you have misunderstood my post. I know that Helge is the only person working on FSNav. I've used it for the past 7 - 8 years and have known it since then. The 'they' I am referring to are the reviewers in Computer Pilot magazine. It is 'they' who are putting themselves out on the line in saying that development is ongoing. There is only one place they would have heard that from, isn't there?

    BL.

    Hmmmm.... I recall someone saynigf last year that if Dan Rather ( *former* CBS news Senior reporter) reported it, it must be true......just before they foiund out it wasn't.

    Please, do not believe everything you read. There are many ways CP could have come up with that story beyond the *one place*.

    Considering the overwhelming groundswell of negative publicity surrounding FSNAV, I would suggest that Helge would have enough intelligence to at very *least* respond to one of the many emails he's received or make an appearance here.

    Unless CP actually cites that they got the word from Helge, it is just a supposition and an unfounded one at that.

    Of course, since it was stated by the developer that the FSX version would be released late 2007, we still have a few days to go. Maybe we'll all get a Christmas present!

    Vic

  15. Can anyone put me in touch with the development team from FS Navigator? The contact on the website doesn't work.

    JC 8)

    ROFLMAO! - Sorry - but if you read the hundreds of posts in this forum you'll find that no one has heard a peep from him (it's a one man band) in over a year.

    I wouldn't hold your breath BUT, if by some remote chance you *do* make contact, please let us all know how!!

    Vic

  16. Joe -

    I think the problem is that there is almost NOTHING in the old program that would transfer to the FSX version. FSNav uses DirectPlay interface and FSX uses SimConnect - these are two different animals. He could sell the rights to the name but that would be about it. And, FWIW, I brought this subject up with him quite a while ago (when he still responded to emails) and the answer was no. As far as further development for FS9..... might be a waste of money.

    Just MHO,

    Vic

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.