Jump to content

Paul Deemer

Frozen-Inactivity
  • Content Count

    1,397
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by Paul Deemer

  1. No you can't dock it. I just did that to show off the weather at the time I was passing through. It works well with the 2d-Panel but not with the Virtual Cockpit.
  2. MROC to MWCR after completing the Central America Tour. United and Continental have merged into one Airline. That is why you see a blend of both Airlines in the new Livery.
  3. Passed over some crazy weather down in Central America with Thunderheards Galore. http://img88.imageshack.us/img88/9728/thunderhead001.jpg http://img502.imageshack.us/img502/7176/thunderhead002.jpg http://img198.imageshack.us/img198/627/thunderhead003.jpg http://img836.imageshack.us/img836/6822/thunderhead004.jpg
  4. I flew into Miami when they had 50 knot winds and you can sure stop in a hurry with a 50 knot header on Final. I only used about 1/3 of the Runway. Probably didn't even need the Reversers. :dry:
  5. I had the X52 Pro for about 3 years but one of the flaws of this stick is that the ps/2 port is the most crappy part on the controls. The cables barely stay seated and if they come lose at all the stick will reset in your flight and youll end up with off axis. Mine finally bit the dust and I went and got the Saitek Pro Flight, An additional Quadrant and I already had the Saitek Pedals. The Saitek Yoke springs toally suck and the Yoke has a very unrealistic feel to it. However I performed the Mod that is avaiable on the web where you replace the springs in the Yoke and it feels like a much high quality Yoke now. Very smooth and fluid and definately worth the time. The springs only cost about 4 bucks at home depot and it takes about 30 min to complete the MOD. The MOD for the Pedals removes the Ident. I also noticed I have better control over the place with a yoke and my landings are much smoother than when I had the X52 Pro.
  6. I finally got it to work by not clicking on SEAVU2 at all. I just selected the runway ILS 25L and Trans and then it put KRAIN TAROC FUELR etc all way to the runway. After that I had to put in all the nav pionts manually from TNP to SEAVU. http://155.178.201.1.../00237SEAVU.PDF Seems this is only way I can get it to work. Might have something to do with FS Commander and Exporting it to the NGX FMC. All the other STARS work fine. Maybe I should try Exporting without the STAR as the NGX removes it anyway and it has to be entered through the FMC.
  7. Anyone else have this problem? It only happens with the NGX. (Not the 747-400 or MD-11). It also does not happen for any of the other LAX STARS. Sitting at the ground at KDFW I enter all the info into the FMC. Then I enter the KDFW SID no problem. When I try to Enter the SEAVU2 STAR I will hit SEAVU2 then ILS 25L then Trans, etc. The Execute button will Light up but it won't execute. If you continue fiddling with it like pressing SEAVU2 again then FSX crashes. Normally if this was working right when you hit SEAVU2 from the list it will show up at the top and then you select the runway, trans etc. I have flown all over the world to at least 200 different airports in the NGX and this is the only STAR that gives me issues. I remember the same thing happening with different AIRACs versions so I doubt it is that. This was the flight plan if anyone wants to try and see if they can reproduce this problem. CYOTE5.ABI J65 CME J166 TCS J65 KOFFA J169 BLH J65 DECAS TNP.SEAVU2 (Using FSDT KLAX and latest AIRAC)
  8. Or you could just be patient and wait for the extended range version of the NGX.
  9. Yes PMDG will tell you the NGX doesn't like FSUIPC and it's true to a point. However the way I have it setup has not caused me a single issue with the NGX. I have ALL of my AXIS assigned through FSUIPC. There is a little trick I do before every flight that prevents any FSUIPC problems from occuring. First let me explain my setup. I have the Saitek Yoke, Pedals, and 2 throttle Quadrants so I can have Speed Brakes, 4 Engines and Flaps. Like others I have noticed when you start up FSX and then start a new flight that the wrong Axis is sometimes assigned in FSUIPC and this causes problems. Example: Engine 4 lever moves over to Engine 3 Lever. Now here is the solution. Before you push back from the gate do the following. (Do this for every Flight) Go into FSUIPC click on the Axis Assignment TAB. Click on RESCAN and then move one of your levers and if the correct assignment shows up hit rescan and go to the next lever. If one of the levers doesn't show the correct assignment hit rescan and move it again until the correct one shows up. Do this for all the levers on your throttle and then exit. It takes less than 30 seconds to do this before every flight and if you do this you know all your controllers are configured correctly. I have no problems using the NGX with this setup, and I fly the MD11 and 747-400 as well. All work Flawlessly. If your not a believer then try what I said above and then come back and let me know.
  10. Also turn off Night Lighting that is the biggest FPS killer.
  11. Forget everything you read above and use the link below. That was what finally fixed it. I thought I had the issue fixed awhile ago but it was not until I switched back to Ethernet that I actually got the problem solved. Sorry for the Confusion. If I could delete this thread I would have but I can't so thats why I posted a link to a new thread. http://forum.avsim.n...finally-solved/
  12. Guys, before this turns into an Ethernet vs Wireless debate. There are many things that can cause a freeze. In my case I tried many suggestions to resolve the problem but none worked. :help: The Wireless USB adapter was the last thing that would have occured to me as the culprit. That is why it took me so long to track this issue down. The reason I posted this was so if anyone else had a similar problem like mine they could save themselves some time and test to see if their adapter was causing the problem. :Cowboy:
  13. Your Right Ryan sorry about that. I just had a very bad experience with the only 2 Wireless adapters I have used. Both were used on Cisco Cable Modem Routers provided by Charter Communications. The first one was a Wireless G and was a piece of crap that only got like 2 bars even when close to the router. The Amped had the best range and always had 5 bars. Was reliable enough for internet use. But when your flying with ACARS and need maximum reliability I don't think ethernet can be beat. Like you say though that doesn't mean all Wireless adapters are bad. I do not think the router was the issue though because the other 2 people using Wireless USB adapters on the Network have not had any problems. I also saw this reported on the web by another Amped Owner that had the same model as me. He said he averaged about 1 freeze or BSOD per day which is what was happening to me. So I'm fairly confident it was the Amped USB adapter causing the problem and not the Router. I will rephrase #4 to avoid any confusion or misinformation. 4) Since Ethernet provides the best Connection possible I suggest using this whenever practical. Or as Ryan said a good quality Wireless Card with it's own dedicated Chip. :hi:
  14. Problem has been solved you can find the solution at the link below. http://forum.avsim.net/topic/380619-my-freeze-in-middle-of-flight-finally-solved/
  15. While there are many reasons for your computer to lock up, mine was a weird issue that took me months to track down. Up until then I had a rock solid stable FSX and was able to do up to 18.5 hour long hauls without a problem. Back then I was using nhancer and older video drivers because it worked flawless and I did not want to do anything to jinx it. But a few months ago a friend of mine talked me into using Nvidia Inspector and the latest drivers. About this time I started having a freeze problem where the computer would lock up in the middle of a long haul. This was so aggravating because I lost over a 200 hours in aborted flights. Originally I suspected Nvidia Inspector was to blame and possibly the FPS limiter. When I confirmed that was not the problem I thought well maybe it's hardware. But after a new video card and same issue was able to rule that out. I did tests on the memory and checked the temps on the CPU but nothing was wrong with any of that either. I then deleted and rebuilt my FSX.cfg and did the Bojotes Tweaks but still had the Freeze. By this time I am pulling my hair out and thinking it's just not worth it and about to Format my hard drive and Retire. But being the dedicated Flight Sim Ethusiast I am I kept looking for solutions by process of elimination and I finally found the culprit! Before when my system was stable I was on a Charter Communications Cable Router with Ethernet connection. When I moved a couple months ago to live with some friends they were using a Wireless N Network and the Cable Router was in a different room than my computer. I recently did some rewiring and now have the Router in my Room and the computer connected via Ethernet again. Yep it was the Amped Wireless 150N Compact USB adapter I was using causing the problem. It can only go maybe 4 - 6 hours before it either causes a BSOD or total system freeze. Since I have been back on Ethernet everything has been flawless. I recommend the following 4 things for a rock solid and stable Sim. 1) Download and Install Nvidia Inspector and use the recommended PMDG Settings. 2) I highly Recommend the Bojotes tweaks. This smoothed my system out considerably. 3) Make sure you have the UIAutomationcore.dll Fix. 4) Use Ethernet instead of Wireless.
  16. I was not sure but I found this link below that should answer your question on the Font. http://www.airlinereporter.com/2010/08/new-united-continental-font-to-be-used/
  17. I know it's a Fantasy Livery but I am surprised nobody has done it yet. Talking about the New Merger Livery that United uses now. Basically the paint is all White with United Text and a Globe on the tail. Should be a very easy Livery to do compared to some other airlines. Anyone up to the Task? Here is a video of the current livery on a 747-400
  18. Are you using FSINN? If so that could be your problem. Right now at FL380 with DWC its -17c outside. Don't forget its summer time and with some of these record breaking heat days its not uncommon to be taking off from an airport where its 40c which is 104F. When I am in this kinda heat I dont hit the - side of the scale until I hit the higher end of FL200s. As for Dynamic rate of change the recommended setting is 0.
  19. Still not working for me with AS 2012. If this was only a few hours I could see that but 2 days and no word from anyone at Hi-Fi? Being a long time supporter of Activesky I dissapointed that nobody from Hi-Fi took the time to post in the forums about the problem.
  20. Why even bother to fly then? I never understood why someone would takeoff and go to sleep then wake up to land? This is what seperates the Men from the Boys. :Devil:
  21. The ILS approaches to all the big airports I have flown into are there but I did notice TJSJ is not showing any ILS. Obviously there were some issues with this AIRACs. However it should not prevent you from doing an ILS landing. Just look up the chart for the correct ILS frequency. When you have that info select the Runway even if it doesn't show an ILS. Tune your Radios and put in the Course and all will still work.
  22. You can save the downloaded installer and reinstall whenever you need to with the Activation code you recieve when you purchase the product. However if you install it on your computer and later upgrade your hardware it will not allow you to in most cases. The reason being it senses different hardware and will think your trying to install it on multiple computers. In this case you contact PMDG and ask for a new code and the old one becomes invalid. This is to prevent software piracy. You can run the NGX on 2 computers but only 1 copy of the NGX can be running at any given time and you must get permission from PMDG first.
  23. Marc you might be onto something there. I did bump up the Vcore a bit and so far so good. I also had another problem with the computer today where it wouldnt boot up into windows. Since I had this problem before I went inside the case and checked the sata cables and sure enough the one for the Windows drive was just barely sitting in the socket. Finally took the computer outside and re-routed my sata cables and tied them down really good so they can not pop out again. Im willing to bet the freeze was either Vcore related like you said or possibly the sata cable plugs being loose. If I dont freeze in the next 10 flights I will know its fixed.
  24. I had another freeze with the MD-11. So now I have had it happen to all 3 of my PMDG planes. I am starting to think it's related to my DVD drives and a lose SATA cable. I disabled my 2 DVD drives in Vista yesterday and did the same flight and had no problems. Reason I think its the DVD drives is because a couple months ago I couldn't boot up the computer. Or had computer on and it froze up on the desktop. When I went to check the BIOS I saw one of the DVD models was showing some weird text in the Bios description for the Drive. After reseating the cables and making sure the connections were good the problem went away. I now think that when I am flying sometims the vibration from all the fans in my case is causing a loose connection with the sata cable and when that happens windows has a hiccup and freezes. Will let you know the result of my test after I complete a few Long Hauls.
×
×
  • Create New...