ideoplastic

I've bought and used all the weather engines made for the Flight Simulator over the past 10 years or so. Links to a couple of screenies of generated weather by OpusFSX. The Cargoair screenshot if of a complete overcast during a flight UKBB-EDDK - The second was taken yesterday evening on Vatsim on a flightpath taking me over Hurricane Sandy. I leave you guys to be the judges, specially those of you who have been using Rex, AS etc. https://www.dropbox.com/s/jkiu2kwkkbx9qkd/overcast.bmp https://www.dropbox.com/s/urdqruor8k7cdxk/Sandy1.bmp Regards

Hi Jim, could you also send me the link.? Many thanks!

Thanks for the replies, I think I'll just go ahead and buy it! Regards

Has the Network client version come out yet? Thanks

Now winter is almost upon us, it would be great if any of the expert painters could create liveries for any of the 737 models for the airlines below: Air Inuit Canadian North Air North First Air Photos are available at Airliners, so unable to provide links here: Very grateful for anything you can provide. Thanks

Like many other simmers I have had quite a few black screens and crashes while using NGX even after replacing UIAutomationCore.dll and taking possession etc. Had a crash just yesterday while switching from menu back to full screen mode. - Funny thing is that this only happens to me when using the NGX but never when using any other PMDG aircraft or other 3rd party payware aircraft. As regards FSX having a memory leak while in full screen mode, I have certainly never encountered this and I fly in full screen mode all the time and during 8+ hours long hauls. I have had a couple of out of memory errors on FSX but they were due to damaged/badly designed sceneries and which never ocurred again after their removal. My thinking is that if these problems occur only when flying a given aircraft, then there may well be an issue or incompatibility between said aircraft and FSX/Win7 under certain conditions. Has PMDG looked into this matter? - Find it strange that one should need to replace the UIAutomationCore.dll from an older OS to allegedly solve an issue, which in my case at least remains unsolved after carrying out all the instructions given.

Best wishes for all your endeavours! Shalom and hasta la vista!

I also use the remote PC for charts, injecting ASE weather, transferring REX textures to FSX, Topcat FSBuild, Vroute, and all the Vatsim Pilot software. FSX runs beautifully. Another advantage is the ability to use Input Director and control both with a single mouse and keyboard. Thanks for your comments RJ, much appreciated. Regards

Assuming both your computers running on Win7 OS. You need to do some prep work to get it all working. Have identical account names and passwords on both computers, with full admin rights. Go to Control Panel\System and Security\System\Change settings\Computer Name\Change - Give a unique name to each PC but ensuring your Workgroup name is the same on both, example FSNET. Do this on both Computers. You will need to reboot. Go to Control Panel\Network and Internet\Network Connections\Local Area Connection(whichever is active), then right click and select Properties, highlight with mouse Internet Protocol Version 4 (TCP/IPv4 and then select Properties tab in the window. Bullet in Use the following IP address: IP address: can be any in the range of 192.168.0.2 to 192.168.0.255 Subnet mask: 255.255.255.0 Default Gateway: this is your router address, often 192.168.0.1 - login to your router and check it out. Bullet in Use the following DNS server addresses: Enter the IP addresses of the Preferred and Alternate DNS servers. You'll need to ask your ISP or check for the info at their website, most of them make this info available in the support pages. Do the above in both Computers. As an example, my computers have the following unique IP addresses - 192.168.0.10 & 192.168.0.20 Same subnet mask as above and same gateway IP address (your router's IP address). Now you need to share some folders and assign appropriate permissions. Open Windows Explorer Right click on your C:\ drive and select Properties then Sharing tab then click on Advanced Sharing. Place tick in Share this folder - click on Permissions, click on Add then in the window that opens type the common username you have for both computers, then close and you will see this username appearing in the Group or user names, and below under Permissions for (your username) make sure you tick all the boxes. Carry out this process for all disk drives you wish to share in your computers, as well as for any folders you need to share. Reboot. You have now created a simple network, have assigned a unique IP address for each PC and created shares in various drives and folders. Now the last step is for you to be able to access those shared drives and folders. Go to Windows explorer\Tools\Map Network Drive, in the new window select browse and the unique names of your PCs should appear under Network clicking on any of the PC names will show you the contents of all the drives you have shared and you can select one and assign a Network letter to it. Thereafter every time both PCs are on, you will have access to your disks. Now you can install on your client PC any software such as Weather Programs, etc. Be aware that some older programs such as TOPCAT still require WideFS to connect to FSX remotely. Hope this is of help. If you have any other questions, let me know and I'll do my best to help you. Regards

Just reinstalled FSX an carried out the validation without any problem. Thought I would let you all know.

I have followed this post with great interest and wanted to mention another reason for the "Out of memory" error. Over the last few months I've been testing some photoreal sceneries which were originally made for FS9, most of them worked ok, showing good resolution, but others were not so good or unusable. But one specific photoreal scenery was causing this memory error just as FSX was loading the scenery. After looking into it found that the agn files were to blame, once removed the scenery worked fine. I appreciate that this error can also occur for reasons explained in this post by many. Just thought I'd add this information for those who like me, may be trying to use FS9 sceneries.

Did all that and then when it didn't work uninstalled ut2 altogether. Problem persists. Thanks for your replies though.

Recently while flying online in Vatsim, AI aircraft that were not part of Vatsim traffic kept appearing. I had UT2 installed and someone pointed out to me that I needed to disable the AI from within UT2, but what I actually did was uninstall UT2 completely and also disable all AI aircraft within FSX. However this hasn't sorted the issued and they continue to appear. This lead me to believe that there may be some traffic files or configuration files somewhere that control these AI, but have not been able to find any. Does anybody know where I should look for them and what file type they are? Failing that, does anybody know how to stop this from happening? Thanks

Just wanted to let you know that have now understood how to fly the aircraft and have had a few flights with no issues whatsoever. Thanks to all for the great info and help provided.

Thanks Steve that's exactly what I was unsure about and explained it very well.

Thanks Martin

Ok everyone, sorry for the delay. There will be no need for me to make a video. Spent a couple of hours going again through the tutorials, specifically Tutorial No.2 - Realized that my problem had been all along not understanding the way the LNAV/VNAV system works in the NGX which seems to be slightly different from that on the FS9 737. However there are a couple of things I'm still a bit uncertain about and would really appreciate some feedback on them. Let's say I'm on Vatsim flying at 250kts and the controller just wants me to reduce speed to say 220kts - What would be the correct way of doing this while still following the VNAV/LNAV path. I've noticed that pressing the SPEED button on the MCP doesn't seem to control the auto throttle very well and often causes the speed to drop or increase wildly. Also if I'm at the gate and start the flight in the default mode (engines running), the aircraft starts moving forward even though throttle at that point is in Neutral. Any way of stopping this from happening? Thanks once again to al for taking the trouble to follow this thread. I think I'm getting there. Regards

Bored? - Take your 737 and try land in Paro VQPR (Bhutan) Funchal (LPMA) (Madeira Islands) - VOR visual to RWY05 Vagar (EKVG) Faroe Islands -LOC DME My apologies.....something went wrong with the computer. Vagar (EKVG) Faroe Islands LOC DME RWY30 or RWY12 Gibraltar (LXGB) SRA RWY09 either Civil or Military (latter slightly more difficult) Innsbruck (LOWI) Austria any circle to land procedure to either runway. Regards

First of all thanks to everyone for all the replies. I've been flying 737s for a number of years, the PMDG in FS9 and the iFly and later the PMDG in FSX. Autopilot was definitely on. I think the best thing to do is make a video of the whole procedure so that everyone can see what I'm talking about. It is difficult to include everything in a post without turning it into a book. So I'm going to get back to you guys as soon as it's done and uploaded to a site. Regards

First of all let me tell you that I have already read almost if not all posts in this forum concerning throttle issues and have read both tutorials that came with the package, as well as doing 2 clean reinstalls of the software. This is the issue: After preparing the aircraft for flight (start up from cold, FMC configuration, loading fuel calculated by TOPCAT, & setting correct trim), I am on the runway ready to go. initial altitude setting set on MCP which matches the waypoint on the SID in the FMC with corresponding speed restriction. Flaps correctly set, Parking break released, Throttle to 40%, selection of TOGA done. Aircraft rolls down the runway and take-off takes place with LNAV/VNAV selected. After take off aircraft climbs and the continues to the waypoint mentioned above but totally disregards the speed restriction on the FMC and then continues increasing speed to 350+ knots. LNAV/VNAV are still active and N1 throttle setting on MCP still lit and allegedly active. The autothrottle has not been touched at all during this time and the FMC has been set so that autothrottle cannot be manually overridden. I appreciate that many people don't seem to have this problem, so why is the above happening to me? - Is there some hidden setting among the hundreds of pages in the manuals and tutorials that I have missed? - This has happened to me in all flights I have done so far, having to use manual throttle control instead. The speed MCP button doesn't seem to work either when activated, well let's say sometimes it decides to work. Any feedback would be appreciated. Thanks

Thanks for your reply Paul. Unfortunately it is none of those. After months of everything working OK, now suddenly FSX is identifying the gauge of a well known commercial product as creating a conflict. Guess I'll have to reinstall FSX. Regards

Javier Go to the Vatsim website. Register and after receiving your membership confirmation go and download the client software which can be FSInn or Squawkbox . You can then connect to the network as an Observer. Simply place your aircraft somewhere at the airport of your choice (except connecting while on a runway), perhaps best at one of the gates. In FSInn and I believe alsoin SB, there is a box you can tick to inform the Network you are an Observer. Tune to any of the active frequencies for this airport (assuming connected at an airport with active ATC and watch and listen; you can even contact the Controller and say hello and let him/her know you are there and if not too busy he/she will normally answer any questions you may have while observing.

Over the last couple of weeks every time I load FSX a message pops-up telling me that there is a problem with my LVLD.dll gauge causing a conflict and giving me an option whether to load it or not. Have also had FSX crashes relating to a utility called FSXsave. Have removed FSXsave but Level-D conflict continues even after a fresh re-install. The thing is that everything worked wonderfully for months on end. Any ideas what can be causing all this?

Spent quite a it of time this last weekend running this tool through my FSX directory and all other scenery folders outside FSX folder. It found and fixed quite a number of textures. One thing I noticed though, was that when selecting a folder containing photosceneries with a large number of files, the fixing process took a long, long time, when I checked on the task manager it reported that the program was not responding. This happened when checking all large photo sceneries, such as those by Gottfried Razek, Megascenery, etc. However it's possible that there was nothing wrong with them on the first place. One i can confirm is that it didn't mess up my FSX installation in any way. Didn't bother to check framerates, but did notice faster loading and sharper textures.

Thanks Robert for clarifying the matter for me. Regards