goround
-
Posts
26 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by goround
-
-
I thought about the Disk's being corrupt but it just seems hard to believe that a data error on one of the disk's would just change the default FS9 text behavior to something else...and not cause some other problem, like crashes?
I am going to try installing to the "E" drive...just because it's never seen FS9 before. What have I got to lose?? :wink:
Thanks Pete!
Vic
-
Well...this is incredible. I deleted all partitions on both "C" & "F" HD's, made new partitions and completely reformatted all of them. Installed XP Pro on "C" and FS9 on "F"...and it's STILL behaving incorrectly. I haven't even installed the FS9.1 patch yet. This is starting to feel like a Twilight Zone episode.
I just can't figure out what is happening. Doesn't a format delete every single bit of info on a HD (not in a "security" sense...I realize data can still be recovered)? What could possibly remain to change FS9's default behavior...from the "git go"?
These are, of course, rhetorical questions as this is certainly not an FSUIPC issue...just an update, of sorts (and a hope that someone might have a suggestion).
I figured this was an even more drastic remedy than Pete's last suggestion...but that suggestion is the only thing I haven't tried and will now do. If the FS9 behavior DOES return to normal when I install it on a HD ( "E") which has never had FS9 on it...what does that mean??
I'm glad I had the wife change the combination on the gun safe!! :P
-
Obviously I've got something else in there, somewhere.
This could be a long hunt as I just can't bring myself to start all over again...again! :lol:
Since I did a "clean" FS9 install, including manually removing everything, even registry entries, according to the MS instructions:
http://support.microsoft.com/kb/888846/en-us
something else is still left in the registry as I can't think of anywhere else it could be hiding and still affect a "clean" FS9 install.
Thanks Pete.
-
OK, Pete...let me back up...AND apologize to you. I'm getting a bit "frazzled" by this whole issue but it's no reason for me to be so impolite.
I must have misunderstood...I thought FSUIPC WAS the dll which changed the text to "white". You are saying it is not? Let's start with that issue...what changes the scrolling ATIS text to white?
Again, sorry for being such an a%#_ole, Pete. I think I need a Valium! :wink:
Vic
-
I have a clean install of FS9, that I have worked on for 2 weeks to get back all my addons. Why would I need a new FS9.CFG when it was just created? This problem started before my clean install. The whole idea behind the clean install was to get rid of this problem. That being said...yes, I have deleted my FS9.cfg and allowed FS9 to create a new one...to no avail.
I can not get FS9 to act like it did before FSUIPC 3.6. I, like you Pete, do not understand it. But the white text remains and I know of no other program, add-on or utility which changes the ATIS scrolling text to white...except FSUIPC.
All that being said...I'm going to re-install my entire system. After 10 years of FS...I get a little cranky when some part...any small part...of FS does something unexpected. Slow FPS is expected, at times. Unwilling addons are expected at times. I can't live with a "system wide" unexpected, however. This is not a "weird texture" or strange CTD...this is a corruption of the basic FS9 process...and I won't live with it.
I can also say that, unless you start making previous versions of FSUIPC available...it will also no longer reside on my system.
I am EXTREMELY sorry to have to make that statement...but you have NO idea what I've been through, in the last month...no idea whatsoever. I will not put myself through it again, ever. I haven't flown an aircraft in 7 weeks!!! Trying to figure this out and several clean FS9 re-installs.
Yes...FSUIPC was one of the greatest additions to my MSFS experience...but after this 3.6 experience...I think I'll do without it, in the future.
Thanks, Pete, for your help. It is appreciated!
Vic
-
Pete,
If I understand correctly from your reply...it is FSUIPC which changes the text to white...correct? Because I have fsuipc.dll and .ini completely deleted from my system and still get the white text, as shown in the screenshot below. This leads me to believe something from FSUIPC is still "hanging around". I've never installed AdvDisplay...or even downloaded it...but I read at the site about it and that DLL is also nowhere on my system.
I would like to make clear that if it was ONLY the white text as the problem...I would not care...I could live with it. The REAL problem is that, at the same time as this text color change occured (installation of 3.6) I also lost the ability to see the ATIS text without having the "Show ATC Text" setting checked. This is an annoyance in that, with that setting checked, I must see EVERY atc message in a text window, to anybody, instead of those just meant for me (using the "Auto-open ATC Text" setting).
I have asked at several forums and everyone agrees that a new, clean, install of FS9 should have red ATIS text, at the top...and it should show up without having to have the "Show ATC Text" setting checked. This is exactly how it used to work but this is not happening now. The fact that this all started with my installing FSUIPC 3.6 and that I'm still getting the white text (as you can see) with no FSUIPC.DLL anywhere to be found on my system is why I suspect FSUIPC.
I don't understand it either, Pete. In the past the removal of the FSUIPC.DLL from the "modules" folder was all that was necessary. But, as you can see...the removal of the 3.6 DLL has not removed the white text...and I believe that it's a bit more than a coincidence? I even checked the FSUIPC.INI, before removing it, and the line for the white text was "0".
All of this is a problem for me as I have several programs which relay info in the scrolling ATIS text bar...so I can't just "live without it"...but I can't live with every ATC message, to anybody, opening a text window in the middle of my screen, either.
Would you happen to have an older version of FSUIPC laying around...one which did not have the ability to change the text color (3.4x)? I'd be interested to see what effect on the problem using it would have?
If you can think of ANYTHING else that would both change my scrolling text color and cause this same text to not appear unless the "Show ATC Text" setting was selected...I'm open to any suggestion because, at this point, I'm starting to consider a complete format of all my HD's and a complete reinstall of everything (OS, FS9, addons etc.)...something I would certainly like to avoid! :cry:
Vic
-
Ever since I upgraded to FSUIPC 3.6 I have been unable to see the scrolling ATIS text (in the green bar) without having "Show ATC Text" checked in the FS9 settings. This is annoying as I DON'T want to see every ATC message open a text window...only those meant for me (via the "Auto-open ATC window" in FS9 settings). It worked exactly that way before 3.6 (registered, BTW).
I also now have white text scrolling on a green background...which points to FSUIPC even more as this is something that FSUIPC 3.6 changes from the default "red on green" scrolling text.
Does FSUIPC do anything to the registry? I can't explain why removal of the DLL and a complete removal and reinstallation of FS9 hasn't fixed the problem.
Any help is appreciated. BTW...this is still one of the best addons for FS9 and worth every penny of the cost of the registered version!
-
I've reduced my setting to "16" from "32" and take half a breath before hitting the trim buttons again :wink: ...this seems to work great and I can actually get my MAAM-SIM DC3 to level out in steady conditions. I don't think I'll need the "2 different controls alternately" "fix" as this seems to be working about how I want it.
Thanks for a great utility Pete!!
Vic
-
Thanks Pete. That answers my questions nicely!
Vic
-
I have deleted my joystick's trim buttons (FS# 3 &4 / FSUIPC # 2/3), in CONTROLS | ASSIGNMENTS in FS9. I then followed the User's Guide instructions for setting "Offset Increment/Decrement Controls" (which just happens to have, as an example, the Elevator Trim 8) ).
A screenshot of the "trim down" setting is here:
My questions are:
1. Did I err by removing these 2 button "assignments" in FS9 CONTROLS settings?
2. I am looking for very "fine" control of the elevator trim (note the "32" entry in "parameter" box). What I am getting, with the above, is very fine trim movement until the 3rd (or so) button press, at which time the control "accelerates" just as if I was "holding" on a trim wheel (or any other on screen adjustment) with my mouse button. Is there any way to stop the accelerated control for the elevator trim ONLY? In other words, no matter how long I "hold" on joystick "trim down" button or how many times in a row I press it, I only want it to move the default amount, without any acceleration.
I hope I made my request clear. If not, please ask for any clarification on what I'm trying to do.
Thanks gang.
Vic
-
Im not going to go through my whole ini just to see if I have something different. I'd be glad to post the whole shebang and everyone can pick and choose as needed?
Vic
-
I have 2 installs of FS9...one is standard and one is for the Golden Wings3 addon (this removes modern scenery and aircraft and allows you to fly with pre-WWII scenery, AI and such).
There are 2 methods of installing this addon and I chose to copy my complete "FS9" folder to a second drive. This, of course, included my "Modules" folder, with FSNav in it.
My question is this...is there a way to point an FSNav DBC run to a different FS9 install? I want to form a new DB based on the new info in the Golden Wings version of FS9, without touching my original DB for FS9.
Any ideas?
Vic
-
This may not be the best place to post this question but everyone here is so knowledgeable on this issue I figured to give it a shot.
Is there a way to add, delete or edit the "Procedures" which show up in the default FS9 GPS's??
Thanks.
Vic
-
Doesn't FSNav do that already? I fly mostly VFR but I was under the impression that FSNav would add SID's/STAR's to you flightplan? I've used SID's/STAR's for a couple of jetliner commercial flights (albeit many moons ago) and I seem to recall it all being integrated?
Or not. :wink:
Vic
-
As will I...thanks for the heads up, Bob!!
Vic
-
I'll second Vulcan's post in that Airport Chart Viewer is a great little addon. I always hated having to follow those ugly pink lines at airfields I was unfamiliar with. Now I have some idea where I'm supposed to go...without the FS9 "hand-holding" :wink:
Vic
-
I was referring to FSNav's habit of not recognizing, or butchering parking spaces of AFCAD2 altered airfields. I went ahead and installed 4.7 and it does seem to resolve 99% of the issues with AFCAD2 altered airports. I had to do some renumbering of parking at "Bremerton 2005" (courtesy of MSScenery and Mark Smith) but FSNav 4.7 did not stumble over a "reserved" parking space for my VA, as it used to.
All in all 4.7 is a great improvement, from what I've seen. Thanks!
Vic
-
I quote:
Parking positions in addon scenery are now correctly interpretated.
Alastair
Does this include parking changes made with AFCAD2??
-
This is the single biggest problem with FSNav that I've found. Sometimes I can make it work with instructions given earlier...but it's a real pain and very time consuming.
Will FSNav 4.7 FSnavDBC now correctly read AFCAD2 modified airports?
Thanks.
-
Thanks, Rob! Although it is a pretty "hairy" solution...I'm guessing nothing better is going to come along?
I already have about 20 AF2 files loaded...I may just have to live with them and FSNav's behavior. Performing the suggested...for all 20...would be a little more than I would be willing to do. I may, however, try removing my VA's parking designation from the added parking areas...just to see?
Heck, I may end up trying the "fix" for all 20...sometimes I get bored. :wink:
Thanks Rob!!
Vic
-
I've asked about this before and no one seemed to understand the question...so let's try again with pictures :wink: .
No AFCAD2 files (AF2_xxx.BGL) are correctly recognized by FSNavigator.
I give you 2 examples.
The first is KPWT with added concrete under 3 existing, default parking areas (yes...I removed the areas, then added the concrete, THEN replaced the 3 areas). I then changed the parking area type and added an airline code. All my changes show up in FS9 (concrete, parking taxiways, etc.) but FSNav goes mental. Yes...I first started FS9 to "add" the new scenery created in AFCAD2 (stored, as required, in "Addon Scenery / Scenery" folder). Yes...I then shut down FS9 and started the FSNav Database Creator program and let it run to completion.
Here's what KPWT in AFCAD2 looks like:
Notice: 3 parking areas, on concrete (was grass). They are numbered 18, 19 and 20. Here's what I get when looking at it in FSNav:
Only 1 parking. And even stranger...here's what FSNav lists as parking areas, when trying to export a flightplan to FS9 starting at KPWT:
OK...so you think the added concrete, change of parking type, etc. is a problem (if it IS a problem, I'm still going to be looking for an FSNav replacement). Here's an example of a very simple change to an airport...and the resultant FSNav "brain fart". My VA makes a FedEx pickup from a truck at KAST. The truck scenery was added in an out of the way place. I added a simple parking area near the truck. Here's what it looks like in AFCAD2:
And here's the result in FSNav:
I don't know why FSNav refuses to understand changes to airports. Those changes are higher priority than the default .BGL's and when the FSNav Database Creator is run, it should "know" that. Apparently the Database Creator needs some serious work.
Hey, Gilles...is what I'm seeing anything like you had problems with??
Tell me how to fix it, gang.
Vic[/img]
-
As far as I know, Gilles, the default FS9 .BGL's (they are not "AFCAD2" files!) for airports are grouped together by area in one .BGL and you cannot delete a single airport. If you delete the .BGL for the area the default airport is in...you lose many surrounding airports also. I know...I've tried!
You "SHOULDN'T" have to delete the default, anyway, as your modified, AF2_XXX.BGL that you create should be saved in the FS9 "Addon Scenery/Scenery folder and will take precedence over any default.
All that being said...it doesn't work in FSNavigator. FSNav refuses to recognize AFCAD2 "modified" airports correctly (is this happening to you?). Changed or added parking areas are my main complaint...they never show up with a correct "parking number" or may not show up at all in FSNavigator.
I have asked here before without getting an answer...people don't seem to understand the question??
I'm going to post my question again, with screen shots from both AFCAD2 and FSNav...maybe pictures will help explain the problem??
Look for my new thread and see if my problem in any way resembles the problem you are having, Gilles.
Vic
-
Hmmm... let me restate the problem. I am doing all those things, Alastair, as I've always done. The problem is that FSNav will only show the default MS .bgl for the airport, not the Afcad .bgl (which should take priority, as it does in FS9). I have the Afcad .bgl in the Addon scenery/scenery folder where it's supposed to be. For some reason FSNav is not using it instead of the MS default for the airport in question (KPWT). This happens even though FS9 is showing the new Afcad modified airport.
The only way I managed to get it to show in FSNav was to remove the MS default for that airport from the main Scenery folder, Start FS9 to add the changes and run the DBC program, again.
I have several Afcad files for other airports and I will check to see, tonight, if they show correctly in FSNav or if the defaults are showing instead.
I hope that explains the problem better.
-
Is there a way to force FSNavigator to use Modified Afcad2 BGL's instead of it always using the default. So far the only luck I've had is actually removing the default BGL from the main "Scenery" folder (and storing it somewhere). Then I can get the Modified airport to show in FSNav. It's not as simple as that, of course...you have to start FS9 after the moves then close and use the FSNavDBC program.
Seems like there should be an easier way?
Thanks.
ATIS text problem.
in FSUIPC Support Pete Dowson Modules
Posted
Small update. Installing to "E" didn't work. Did a "zero fill" format on "F" and re-installed...giving up, at this point.
Installed the latest FSUIPC and touched nothing on the first FSUIPC window. Still don't have my ATIS text BUT...I've got my ACARS and other messages...in the normal red text...without having "Show ATC Text" selected...so I'm very happy!!
No clue what brought back my ACARS text...and I don't care. I refuse to "poke a stick" at THAT gremlin, anymore!! :D :wink:
Vic