GDex

Members
  • Content Count

    43
  • Joined

  • Last visited

Community Reputation

0 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No

Profile Information

  • Gender
    Male
  • Location
    Canada
  1. Thanks Kyle I have found FSX-SE in: RootKey: HKEY_CURRENT_USER Key: \Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Subkey: AppPath When I open AppPath: it reads the correct location where my FSX-SE is installed. There is a backslash at the very end. Yet Kevin was saying that FSX-SE doesn't put a backslash at the end of the registry entry for installation folder, so we need to add one for the PMDG B744 to install. How come it refused to install even though I had the backslash? I don't know if this has anything to do with it, but I noticed there was also an entry in the registry for FSX boxed, even though I had uninstalled it before installing FSX-SE.
  2. Kevin, the registry is a pretty big file. Where exactly should I add this backslash? Gaétan
  3. Hi Andrew If you must have the 744 now, the only way I see is for you to reinstall the boxed FSX, then install the 744. It is feasible to have both FSX box and FSX-SE on the same computer. Just check the Steam site for tips on how to do it. Gaétan
  4. The problem is that I entirely deleted the FSX Box and all related files, including the DLL.xml file, before installing FSX Steam. It would be great if I could get those 3 files from a trustworthy source. Last night I also ran into another problem. After the fix done Registry repair tool, in the process of installing the 747, a box came up stating: "The following VS2008 Redistributable file is required for this PMDG product." Then it offered me a choice between repairing VS2008 or something else (don’t remember what – deleting?). Anyway I just closed this box and the installation carried on to an apparently successful end. However when I tried to load the plane, I got these DLL messages. So I uninstalled the 747 and re-installed it, but this time I chose to repair the VS2008. Not only did I still have the DLL issue, but additionally, with FSX closed and searching on the Internet for a solution, my computer froze and went completely black and dead. I had to manually shut it down (i.e. push the physical button). I then re-opened the computer and a plain black screen with white letters came up stating that Windows had not been shut down properly and offering to repair some file (recommended), which I selected. Once it was finished booting, I ran a full scan with my Avast anti-virus, then another scan with Malwarebytes. Both came up with zero infected file. So I suspect, but not sure, that “repairing” the VS2008 file might have caused this problem with my computer. At this point I decided to follow Kyle’s advice and wait for the next 747 version. Meantime I’ll be happy to play with my 777 and 737NGX. But, it would be nice if it could be solved!
  5. Thanks, Tom. After running this tool, I was able to install the 747-400X. However, now when I try to load the plane in FSX-SE, I get the same dll problems others have reported. From what I have gathered on the internet, this problem has been going on for a while, so I don't think it is related to SE. I saw a solution recommended by PMDG on another post, so I will try it later.
  6. I can't install the 747-400X in FSX Steam either. I now have only the Steam Edition installed, no longer the boxed FSX. When I try to install the 747-400X, I get the following message: "Installation cannot continue. Your registry does not show a valid FSX installation location." Then the only option is an OK button. End of the process. Is there anyway to point to the FSX-SE location?
  7. GDex

    Auto Time Compression Going Wild

    Dan, I finally got around to re-flying LCLK-CYQB. I used the exact same flight plan as the first time. Flight distance: 4774 NM. Flight duration: 11:44 hrs (2nd time). Both times, I flew in real weather as introduced by Opus. Average wind at cruise altitude: 1st flight: 274°, 38 Kts. 2nd flight: 269°, 73 Kts. So the wind was pretty much from the same direction, but much stronger the 2nd time. With such a headwind, the 2nd flight took longer than the 1st. The “Auto Time Compression Going Wild” problem did not occur. There was no case of overshooting in turns. However there were 12 instances of abrupt speed/altitude changes. Each time, I paused the sim and recorded the time and distance from departure. All of these occurred at cruise altitude (FL320 initial, then FL340, then FL360). The first occurrence was at 1:25 hrs into the flight, then at varying intervals, however, there was a stretch of 2 hours where there was an instance every half-hour, +/- 2 minutes. After 8 hours in the flight, I had to pause the sim for about 4 hours. When I resumed the flight, it took about one hour before an instance happened, at 9:04 from departure. This was followed by 2 more instances at 9:33 and 9:46. After that, I was nearing the TOD point, so I went back to x1 and had no further instances; the flight completed without any other hitch. I don’t know if this data can be of any use to PMDG. I could make it available in an Excel spreadsheet if they are interested. My conclusion for the future is I plan to use x8, but if I run into problems, I will scale back to x4.
  8. GDex

    Auto Time Compression Going Wild

    Dan, I had never heard of Gibbs rules (my TV watching is usually limited to news and hockey games). Read up on them and found them interesting. However, when I wrote that sentence, I did not mean it as an apology, but rather as in "I'm sorry I ate too much". You're probably right about x8. Since that first flight I referred to when I started the topic, I did another (SBGR to CYYZ) in x8 and had the same heading/altitude control in LNAV/VNAV mode problem, however no Auto Time Compression Going Wild problem. I will redo LCLK-CYQB in x8, but when it starts going funny, I'll reduce to x4. I'll post the outcome.
  9. GDex

    Auto Time Compression Going Wild

    Robert I have checked the dlls in the dll folder under the PMDG folder, and in all of them, the read-only box was clear. I nevertheless ran again the SP1C update (although it gave me a message to the effect that I was reinstalling the same version). I will find out in my next flight if that worked and let you know one way or the other. Incidentally, my FSX program is located directly in the C drive, not in a program folder. When I install any EXE file, I start by turning off the UAC and my anti-virus. I felt that the first problem that I reported (Auto Time Compression Going Wild) was just a unique anomaly, but I thought I should report it anyways in case it could help someone in the future. Then in the subsequent exchange with Dan (he was very cordial and helpful), I mentioned this other problem (heading/altitude control in LNAV/VNAV mode) because I thought it might be related to the first problem, and it occurs on every flight. It was in the same post that I wrote “Nevertheless, it might be interesting for PMDG to investigate these issues and possibly improve their program in the future.” This statement is very different than “insisting that we "improve our program"”. It was just a suggestion. The fact that the problem kept occurring after the installation of SP1C led me to state “it certainly did not resolve the heading/altitude control in LNAV/VNAV mode issues when in x8”. It was not “delivering a dictum here on what you think we didn't do”. I just made a plain observation of what I saw. You mentioned “it might be more helpful to take a tone of cooperation” – that was my exact intent in making this post in the first place. I certainly did not expect such a blast in return. Now I am really sorry that I made this post. Regards
  10. GDex

    Auto Time Compression Going Wild

    I do have SP1C installed, but it certainly did not resolve the heading/altitude control in LNAV/VNAV mode issues when in x8. I will do some testing during the holidays and let you know the outcome.
  11. GDex

    Auto Time Compression Going Wild

    Hi Dan. Thanks for responding to my issue. Since the incident occurred, I have done only 1 flight on the T7 and this event did not occur. I would not know how to try to reproduce the event, since the aircraft was flying straight and level in cruise at x8 when it occurred; the wind was steady. My rig is described under my name in my posts. I believe it is sufficiently powerful to run the PMDG aircraft without any problem. I normally get FPS rates in the thirties. As I indicated, I am running Opus Software as weather engine, and it has a feature whereby the sim is first slowed back down to a steady x1 rate before the weather is injected, then raises the simulation rate back up to whatever it was before. I am wondering if there could be an interaction between this Opus action and the PMDG Auto Time Compression feature and the FSX Simulation Rate feature. In fact, do you know if the PMDG feature uses the FSX Simulation Rate feature or if it is independent? One thing I did notice on all my long T7 flights is the aircraft behaviour when running at x8. Initially, everything is smooth and normal. But when about ¾ of the way through the flight, I start getting sudden speed and/or altitude changes. It also starts being “sloppy” in turns: normally, it starts turning a bit before a waypoint and merges smoothly into the new direction. But at some point in the flight, again about ¾ of the way through the flight, it starts overshooting the turn, then overreacting the other way, does this a few times, and finally settles down in the desired direction. It looks like the program (FSX and/or the aircraft) is “getting tired” at the end of a long flight! If I fly in x1 those issues do not occur. Such behaviour was going on when the incident occurred. So I think the “going wild” incident might be related to the behaviour described in this paragraph. As you said, the solution is probably running at x4 instead of x8, and I’ll just have to choose shorter trips. Nevertheless, it might be interesting for PMDG to investigate these issues and possibly improve their program in the future.
  12. GDex

    Auto Time Compression Going Wild

    Hi Lasse. Thanks for replying. The last update of my T7 was the SP1c done on 23 October 2014. I bought the original T7 on 20 Dec 2013, and installed SP1 on 22 July 2014. Looking at the development history in the text note that came with SP1c, I notice that I missed SP1b. Can that be an issue? Or does SP1c include SP1b?
  13. GDex

    Auto Time Compression Going Wild

    Hello, someone read this topic please!! Gaétan Dextras
  14. Strange thing happened to me yesterday. I was flying the B777-200LRX from LCLK (Larnaca, Cyprus) to CYQB (Quebec City), a 4,774 NM journey. I used Auto Time Compression at 8X (controlled by the chronometer switch) from the time I reached cruise altitude, and kept using it except for the step climbs. Everything went fine until I had about 550 NM to go. I then noticed several abrupt changes in speed and altitude even though the wind direction and speed were constant (I use Opus for weather interface). I went off and on Auto Time Compression a couple of times to stabilize things. Then, when I was about 450 NM from destination, the Auto Time Compression suddenly shot up to a ridiculous number like 128X or more. I immediately paused the flight, and turned the Auto Time Compression off using the FMC. However in the few seconds it took me to pause the flight, the plane went on right past the next waypoint (where it was supposed to do a 19° turn) and travelled about 200 NM. After I had stabilized the aircraft and got going again (without Auto Time Compression), it behaved as expected, i.e. it started turning back towards the waypoint it had bypassed. At this point, I intervened through the FMC and made it go direct to the next logical waypoint (bypassing 2 waypoints) and from then on, the flight carried on normally and I landed at destination without any further problems. As anyone ever run into that problem? Any ideas as to the cause? Gaétan Dextras
  15. GDex

    B777 Introduction Manual Table of Contents

    Kyle, I had not noticed it was a bookmarked PDF. Thanks for letting me know. On page numbering, I know it is a standard technical document numbering system, which goes back to the days of the typewriter, when you would not wish to retype 275 pages because you inserted a new page after page 2! However in the case of the Introduction Manual, it is standalone so I don't see the need for 0.00 which would imply there might be a 1.00 section further down. I just thought if PMDG decided to insert a ToC, it would be easier to do it without the 0.00 which repeats on every page of the document and is totally redundant. However it's no big deal. Gaetan