Jump to content

SSI01

Registered Users
  • Posts

    73
  • Joined

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SSI01's Achievements

Community Guru

Community Guru (4/7)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

10

Reputation

  1. Hello Wim I hear what you're saying - and I'm glad you posted that image because I made repeated tries to get an image of my problem which was almost exactly what you've posted - my difference is I get the right-side image with a black screen, the left-side image is identical to the left-hand screen you've got except it's only a white screen (same dimensions as the white screen in your right-hand box), but it has the same icon in the upper-left corner and the same print across the top. Just no dialog box as seen in your left half of the image. I DO get a different dialog box about the Red Panda program in my FSX Prop program, though - it's not the standard framing on that dialog box that's in the other programs' Red Panda boxes. I do take the same actions you are taking in that I raise both boxes by hovering the cursor over the double-icons on the taskbar. Although there is no text in the left-hand box - just the white screen as in the right-hand box, with the same title info across the top - I take the same action, just "X" out of it, and at this point the problems seem to be resolved.
  2. Mr. Zippy, I have a screenshot of the lapped icons, still trying to figure out a way of getting a shot of the two miniature screens side by side just above the tool bar. Here are the lapped icons.
  3. I'll get started on that. Hopefully it won't exceed upload limits.
  4. Hello again. Well, Mr. Zippy, nothing has changed from the above description. The sim will start fine from either the shortcut in its desktop folder, or by accessing it directly by going into the sim's base folder and double-clicking the ".exe" file. Things work fine as long as when the "lapped" FSX screens in the task bar appear on the bottom of the screen, the cursor is held directly over the center of the lapped display and left-clicked once. At this point, the two miniatures of the large FSX screen on the desktop are displayed side by side above the bar. One shows a black inner filling; one shows a white inner filling. One shows a small blue "FSX" icon in its upper-left corner; one shows a small green/white control-panel-type icon in its upper-left corner. Click on the screen that shows the blue FSX icon, and the other screen will fade away and the large FSX viewing/dialog box screen will then show in the center of the desktop. Make the aircraft/airport selection from this screen, and there are no problems with any flights from that point on. I don't know how to describe the second FSX screen showing under the first except to say, again, it seems like there is another "ghost" version of the sim running somewhere. Clicking on things as I've described shuts down that ghost and must free up those resources to use in the real thing. This is most unusual although a fix to the hex appears to have been found. Maybe if anyone else runs into this situation this post may help them.
  5. Hello again. I took your suggestion re: FSdav.dll but no soap, sim still will accept an add-on aircraft (Aeroplane Art Bristol F2B) and will not allow it to start at any other airport other than that designated by the sim when first logging on (that is, default flight). However, I have noted something else - when starting the sim, after it goes through the initial start-up screen ("FSX Flight Simuulator" blue screen), and then tells me Red Panda (has to do with the SSW F-104 aircraft) is disabled, I get the sim going black for a moment, after which I get the initial "run" screen (same as start-up screen), but when looking at the bottom bar on the computer screen, I see two small "FSX" icons in that bar, one superimposed on the other, which is just barely sticking out from beneath the right side of the upper icon. Move the cursor over these icons, and they appear side by side above the bottom bar. One has a black screen in it and in the upper corner a small red rectangle with a white "x" in it - standard Windows "exit" symbology for open window in any program; the other has a white screen and a small, square green icon (like you find in the Device Manager window) in the upper corner, also with a red rectangle with the white "x" in the other corner. I clicked on and closed the square with the green icon in it and the FSX "choose aircraft/airport/date-time etc" screen came up. I went ahead and selected the F2B for the flight, and chose another airport I had not been at yet - and the sim started perfectly at the new airport with the add-on aircraft placed exactly where selected, engine running and ready for flight. I may be wrong but it almost seems like the computer is somehow detecting two "fsx prop.exe" files in it somewhere. I have one right in the program, and a shortcut in a desktop folder marked "fsx prop.exe shortcut," created by the Windows program, not me. There seem to be two copies of the sim starting up and it remains that way until I do as I described above, at which time one icon immediately goes away and the other expands to the full-fledged, ready-to-fly screen. Please let me try this with a few different aircraft over the next day or two to see if I've found something significant. I'll let you know progress.
  6. Hello Mr. Zippy. Here's what happens: Default flight (mid-air in WA state)/powered glider (default aircraft) - starts fine. Default flight (same situation)/add-on aircraft (He-219) - starts fine. Flight from runway on ground, in GA/powered glider (default aircraft) - I get sound and view of runway, stays like that for about 10 seconds, then two boxes, re: error found/FSX restarting. Flight from runway on ground, in GA/add-on aircraft (He-219) - same response as w/default aircraft. So, in short, I can fly anything in the hangar from the default flight - mid-air in WA state - but can not start any flight anywhere on the ground with any aircraft, including the default aircraft. Incidentally - after the 4th restart in this series, I got a notice saying FSX had a problem with a gauge file - "FDav.dll" - and recommended the file be deleted. Here's what it says: "Flight Simulator has detected a problem with a third-party software program (add-on) NAME: FSXGauge VERSION: 1.7 COMPANY: FILE: Gauges\FDav.dll" The FSX .cfg file changes every time there is that refusal to fly anything other than the default flight.
  7. Now have a bugbear having to do with scenery - sim will now load only that for the default flight in Washington State - any attempt to move to another scenery, even if I have started a flight using a default aircraft, ends w/the sim showing the two error/restart boxes, at which time I have to shut the thing down. I thought paring down the number of aircraft it would have to load from dozens to maybe two or three would have helped this thing but it's not to be, apparently. I don't have this problem with other iterations of the same sim on this computer. What is the file that tells the sim where to transport the aircraft once you choose a new airport? I'm wondering if the one in the "FSX Prop" installation is just tired or worn out but I don't have any ideas about a fix for this.
  8. Now have a bugbear having to do with scenery - sim will now load only that for the default flight in Washington State - any attempt to move to another scenery, even if I have started a flight using a default aircraft, ends w/the sim showing the two error/restart boxes, at which time I have to shut the thing down. I thought paring down the number of aircraft it would have to load from dozens to maybe two or three would have helped this thing but it's not to be, apparently. I don't have this problem with other iterations of the same sim on this computer. What is the file that tells the sim where to transport the aircraft once you choose a new airport? I'm wondering if the one in the "FSX Prop" installation is just tired or worn out but I don't have any ideas about a fix for this.
  9. Some new issues arising and every time the .cfg file is changed and has a .txt version next to it in the "FSX" folder. Problem is the sim will load the default powered hang glider practically anywhere but any add-on aircraft will cause the old problem to surface again, and we get the error box and then the restart box. I replaced the bad .cfg file with the standby .cfg file you described below and which I keep in a secure location. Worked every time. Just for fun I ran a "properties" check on the FSX folder with all aircraft and helicopters enclosed and set up. Total size is 545GB. The "rotorcraft" folder alone comprises 58.7GB. Based on something I read a few years ago on this site, I just turned the "aircraft" and "rotorcraft" folders into "aircraft hangar" and "rotorcraft hangar"; next stop was to add back empty folders called "aircraft" and "rotorcraft," then put one or two default aircraft/helos in them to act as placeholders. Since the most aircraft you can fly in the sim at one time is 1, I now just copy the complete aircraft file out of the "hangar" folder, paste it into the "aircraft"/"rotorcraft" folder - and so far things seem to be working well. No waiting time prior to flying, and the flying seems to be smooth. When through flying, just delete the aircraft moved over after shutting down the sim. Only other thing I can think of is to subdivide this sim into "FSX prop" and "FSX helo" sims.
  10. I just did what you suggested. Thanks for the education and peace of mind as well.
  11. Hello Johnhinson I did what you suggested and let the .cfg file rewrite itself after I deleted the bad one. That's given me only one bad start since then but I think I have the answer for that - I was doing other stuff on the machine at the same time FSX was starting up (but not yet displaying) and that may have interfered with the process since I was on the internet. What was happening was after selection of the aircraft, the selected aircraft VC (I try to fly from that position as much as possible) showed up; the engine was running (normal starting mode), but the cursor was a small blue revolving arrow on the screen; there was no way to use the hat switch on the top of the joystick to look down onto the panel - the view was frozen. That would last perhaps 10-15 seconds until the screen went black, the sound ended, and the two messages showed up as described. I've done a couple of things that seem to help. First, I replaced the ".exe" file in the sim's base folder, using an .exe file from another iteration of FSX I knew to be working well. So far I haven't had any problems with the sim hanging up at the instrument panel. I also now always start at the default flight, which is a nuisance, but it takes maybe two or three minutes (I have a LOT of aircraft in this sim) to get where I can substitute another airfield. The other thing that seems to help is I have gone into the ".cfg" file for this version of FSX and entered a "0" value in the USERINTERFACE section, after the config entry "ShowAllACPaintSchemes=" This allows the sim to fan rapidly through all the base aircraft installed in this sim (again, I have a LOT of them in the "airplanes" and "rotorcraft" folders). Each aircraft folder has in turn from two or three to over 140 textures installed, depending on the aircraft. The fewer of those the sim has to plow through to just open up to start a flight, the faster it seems to load and the "CTD" (as described) problem now does not exist, knock on wood. So far, from what i have seen, if you open just the base aircraft screen, highlight the base aircraft you are interested in flying, and check "show variations," what happens is all paint variations for that base aircraft will appear, which causes a further slight delay but does not appear to interfere w/the loading of the variation you want to fly. Funny you should mention the "My Documents" .exe/.cfg files; I put them in two separate files just for safekeeping, when I checked on them the next time the OS or the sim - whichever - had moved both of them to just one folder. I didn't do it. Just an example of the screwy things that sometimes happen w/this rig. I'm going to delete them based on what I've seen here, plus what you report. I used to be w/a govt agency and when we received our first computers we were told over and over by IT how terribly fragile the crazy things were, and how very little improper input it took from an operator to totally mess things up. Consequently I've approached them w/a great deal of caution since then. I've been dealing w/FS since 1995. It's becoming easier yet I find things challenging at times as well. So far this seems to have been tamed but I'm going to run a few more sessions before I can report back and state the problem is totally solved. If this works I should be able to report success maybe around 8-8 or 8-9. I have cataract surgery scheduled shortly after that and want to see the results of my labors with clear vision, and not through a fog. I'll let you know.
  12. I'm going to try rounding up everything in that "FSX.exe files" folder, putting them in separate files by category within that folder, and then try activating the sim with just one set of .cfg and .exe files, and see what happens.
  13. Mr. Zippy, I've found one other interesting thing I can't figure out. I have copies of my FSX.cfg files in C:Users\Owner\AppData\Roaming\Microsoft\FSX, and also in C:\Users\Owner\My Documents\Flight Simulator X Files\FSX.exe files. When I discovered this I checked the one .cfg file folder against the other and found the second string I listed did NOT have all the .cfg files I have in my shortcut folder on my desktop. The ".cfg" files for three of the FSX iterations were missing. I filled them in immediately with copies of the .cfg files that were included in the first string I show above, and which always have worked perfectly. I did NOT set these duplications up this way and am still trying to figure out how this happened. Is it your opinion this duplication of .cfg files in two places in the same drive could be causing problems in gameplay with the sim?
  14. No sir, I start with a different flight every time, don't start from a saved flight. I was wondering if there was difficulty occurring with whatever FSX has that reads gauges for the sim. I say this because the general cockpit windscreen of whatever aircraft or helicopter was selected always shows up, without flaws. It's just that the view freezes at that point with the little circling "I'm reading" icon turning around with nothing happening. You can move that icon anywhere on the windscreen you like but it never goes beyond that stage. I can't change the view to external or tower view using the "s" key,l nor will the gauges ever show, ergo, my thoughts on the sim refusing to read the gauges. After that happens, the screen finally goes black, then we get the two dialog boxes re: problem encountered/FSX is restarting right afterward. After that, the sim will run OK. I will try changing the .exe file and see if that has any bearing on things.
  15. Hello, Mr. Zippy. I'm using the "gold" edition of FSX from the disc, not steam edition. The sim is up to date on its MS-published updates as well. I also forgot to include that when this happens, all is not lost, apparently. When the CTD occurs I check "C" drive and the FSX.cfg for this sim always creates a text file of the .cfg file as well. FSX always creates a new .cfg file once it crashes and, using that new .cfg file, it is restarted. That's the case with my problem, however, what's interesting is that once that happens, and we go through the setup process and reset all the keystroke combinations where they should be and reconfigure everything else, and then select the same aircraft, same time and weather, and airport, and start as usual - the sim restarts without a hitch and everything's fine.
×
×
  • Create New...