Jump to content
The simFlight Network Forums

WarHorse47

Members
  • Posts

    62
  • Joined

  • Last visited

Everything posted by WarHorse47

  1. Mine is registered. I'll post anything more I uncover.Thanks. --WH
  2. Hi, Pete. Thanks for the response. Thought I would provide a little more background. The MAAM TBM has been out since about June 2008. When it was first released some of us reported CTDs related to the MAAM_TBM.gau. I did some minor beta testing with various versions of the gauge and some tweaking on the panel.cfg file to a point where the aircraft loading and model switching was quite stable. At that time I was running an earlier, registered version of FSUIPC. IN the thread you referenced at SOH, I decided to see if I was having similar problems to other users. The bottom line is that any flight I create with any model of the TBM does not want to load unless I remove FSUIPC completely from the module folder. And as I mentioned this occured under FSUIPC version 3.81 and 3.934. So, simply stated, if I wish to fly this payware aircraft I have to disable FSUIPC. I had made an educated guess that there might be a memory conflict as the module loads before the gauge. But I'm no expert and reading the detailed error message. I just know that it points to the gauge. Others have reported a solution with uninstalling various addon scenery, but doesn't lend itself to a final solution. The MAAM Support forum suggests that the vendor is also looking for a common cause or conflict that is causing the problem. With so many users with differing setups, that is like looking for a needle in the haystack. In reviewing the FSUIPC advanced user instructions, the modules appears to have a lot of settings and features. My inquiry was to ask if there might be some setting I could use to better define the conflict and report back to the vendor. Anyways, if I learn anything new I'll pass it on. Thanks --WH
  3. Hi Peter. I'm running FSUIPC 3.934 in FS9. From what I've read in the MAAM Support Forum and tested myself, there seems to be a conflict between the MAAM_TBM.gau file and FSUIPC. Here is what happens. The experiences may be different between users and their setups, but with a normal install with FSUIPC, whenever someone tries to load the aircraft or change models they experience a CTD. The only way the aleviate the problem is to remove FSUIPC.dll from the modules folder and restart FS9. I tested this earlier this evening with FSUIPC version 3.81 and version 3.93 and sure enough the solution works. Are you aware of this problem, and would you have any suggestions on what settings I might change on my FSUIPC.ini that might help me identify the conflict or even eliminate it? Thanks in advance. --WH
  4. Well, I'm happy :D to report that FSUIPC 3.768 works like a charm. The messages are off when the 'hide' feature is engaged, and the messages are on when the 'hide' feature is disengaged. Thanks, Peter. I really appreciate your extra effort on this. I was beginning to worry that there was something weird going on with my reinstall of FS9. I'd invite you over for a pint, but I think it's a long drive for you. :wink: As for those errant e-mails, they never did arrive. I have no idea where they went, or who has them. Something sinister must be going on. Trust me I get a lot of weird e-mails from my friends, so I know the spam blocker and ISP block very little. :mrgreen: Anyways, thanks again. Much appreciated. Great customer service. --WH
  5. Thanks, Peter. I just PM'd you a copy of the FSUIPC.log in case there might be something there that will help. I'm going to give the issue a rest as well, and do some flying tonite. --WH
  6. LOL. Not enough hours in the day nor room on the HD. Thanks. That would help.I was wondering. Is there a way to test to see if FSUIPC is actually running? I've been focusing so much on the messaging issue, I was wondering if the other features are functioning or not. I've checked my background programs and services, and didn't see anything so I'm assuming that FSUIPC only runs from within FS9. --WH
  7. Hi, Pete. Thanks for the response and your patience. I restored my backup copy of windows.dll to the new FS9 module, and added the InitDelay=3 line to the general section of the FSUIPC.ini. The results were the same - the text line will not go away. I will try some additional InitDelay settings and see if there is any improvement. I'm not sure what you mean by this. I don't recall hearing about ATIS messaging. Is that a Windows, FS9 or other function?--WH
  8. Sorry. I wasn't ignoring your request. Lets see if I can clarify this some more.Prior to two weeks ago, FS9 and FSUIPC ran flawlessly. The one feature that worked without a problem was the ability to hide/disable single line messages. On Friday, November 23rd my Windows XP Operating system failed and I was forced to reformat my HD and reinstall Windows XP, FS9 and all my Flight Sim utilities including FSUIPC. Ten days ago everything was up and running, including a fresh install of FS9 and the 9.1 patch. Last week I reinstalled (my backup copy) of FSUIPC and at first it worked fine. As I continued to restore all my aircraft, scenery, etc., I noticed that FSUIPC was no longer supressing the single line messages. The messages I am referring to include the messages indicating that an exit has opened/closed, the tailhook has extended/retracted, and the wings have folded/unfolded. These are the standard messages in red text within a green bar which are displayed across the top of the screen. I have the lower messages [e.g., brakes] disabled through the FS9.CFG settings. Perhaps these will help.. Settings.. Wing fold.. Tailhook.. Exit opening.. Now, as I mentioned I have used FSUIPC for years so I know what to expect. It is a great program, and I am not faulting its design. I liked the ability to turn this feature both on or off. I typically disable the messages during normal flight since I take a lot of screen shots. I typically enable the messages when I do carrier landings with ArrCab, since that utility displays messages of its own. As I have gone through all of the latest Windows XP upgrades from SP1, as well as reinstalled all my firewall and virus programs, I suspect that something is inhibiting FSUIPC from functioning properly. Weird, but that is the only thing I can think of at the moment as everything else is in order. I will do some more testing tonight, and see what happens. Thanks for your input. --WH
  9. Peter, I'm still trying to get FSUIPC to hide the single line messages, and am having no success. As I mentioned previously, I'm now using version 3.766 for FS9. I removed the ini and key files, and re-registered. Still the problem exists. I've even tried version 3.75, but something is preventing the program from impacting the messages displayed by FS9. I might mention that I use FSAutoStart to shut down background programs and services. Might there be a service that is required by FSUIPC, that I might be shuting down? Or might their be some security feature with Windows XP that is preventing the program from properly working? I'm baffled. --WH
  10. Hi Peter. You are right on all accounts. I removed all the FSUIPC files from the module directory, updated to version 3.766, and went through the registry process. (the prior version worked flawlessly since I installed it, BTW,) The problem is that I cannot remove the single line messages regardless of what I set. Your program should remove the green bar with red text messages at the top such as 'Tailhook Extended', etc., but for some reason it is not. Thanks --WH
  11. Hi Peter. I'm in the process of reinstalling FS9 after a system crash, and I've encountered something unusal. I have a registered version of FSUIPC 3.70. In rebuilding FS9, I reinstalled FSUIPC and reregistered the product without a problem. Last night as I was reinstalling my aircraft, textures and other folders, I did something that impacted FSUIPC. When I fly, I cannot 'Hide all single line messages." The box is checked, but I still get the single line message across the top of the screen. My guess is that I will need to reinstall FSUIPC or reset the settings and start from crash. Any advice? Thanks --WH
×
×
  • 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.