tohughes76

Craig:What depiction mode are you using-standard, smooth cloud transitions or DWC? Each has their own trade-offs to deal with FSX limitations (wind shifts, etc), but I find standard is most like ASE in its enroute weather coverage.

Dont copy the whole folder, just the files themselves.-Copy the .xml file from the SDK to your appdata/roaming/microsoft/fsx folder (server pc), then edit as described above-Copy the .ini file from the SDK config folder to your Documents/flight simulator x files folder (server pc), then edit as per page 90 of the user guide.-Copy the .msi file from the SDK lib folder directly to your client PC, location of your choice and run it just like you would an executable file-Copy the .cfg file from the SDK folder and place in your My Documents folder on the client PC. Edit the values of the [simConnect] entry with the same values you used in the .xml file.After that, continue with the test as described in page 91 of user guide...you should be good to go.If you run into issues after that, start a new topic in the Hi Fi commercial forum here on AVSIM so the developers can help out as well. Hope that helps-Good luck and have a great holiday!

The 'cheat' HiFly and I described is workable in the advanced settings tab of FSX wx, but won't work if you are using real time AS weather...this would be a static weather conditon.

Just went back and reviewed my saved wx files and remembered that the clouds/winds were saved in different layers but the vis was a single value. Getting the overcast deck appearance in AS2012 worked best at 1/2 mile vis with a ceiling layer bottoming out at 200 agl. I was remembering my testing back and forth with manual wx settings in FSX...my apologies.What you can do manually in the advanced weather tab in FSX that you can't replicate in AS is the overcast layer with 1/16th vis and have the surface layer with unrestricted visibility (or whatever value you prefer). This gives the "popping out' effect descending or climbing out of the layer. Perhaps adding layers of visibilities in the Edit Wx function would be a good additon in a future SP if it is possible...

Let me know if you find the files after installation of SDK SP2.

I already had the SP2 applied to my SDK, so I can't say for sure but I would think that SP1A would have had these files in the same location.As far as sharing, if both your client and server machines are in the same homegroup in Win7, then you should have no problems between the two.

Darryl:The values that you put in for IP and Port in the server's Simmconnect.xml will be the same ones you plug into the client's Simconnect.cfg.As far as the SDK is concerned, on my machine using the SDK SP2 the files are located-SimConnect.cfg - C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator X SDKSDKCore Utilities KitSimConnect SDKconfigSimConnect.msi- C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator X SDKSDKCore Utilities KitSimConnect SDKlibSimConnect.xml- C:UsersTimAppDataRoamingMicrosoftFSXSimConnect.ini- C:UsersTimDocumentsFlight Simulator X FilesIf you can't locate your files in SP1a using these folders, try installing SP2 and looking again...can't hurt. Darryl, are you running Windows XP, Vista, or Win7?

Alain:1. Start FSX on the server, then run AI Traffic on the client PC. You should get a DOS window on the client that says 'Connected to Flight Simulator!' if the configuration is correct.2. Correct!

Craig:I have been using this method for some time. Even though the real time weather in AS doesn't use this technique, you can apply the same idea in AS 2012 by creating situations you described above in the 'Edit Wx' tab and saving them as .AST files for repeated use. For instance, I have a 'Low IFR' situation with a layer of clouds from 200-4000 ft and 1/16th mile vis, then a layer of 1/2 mile vis from 200 ft down to the surface. That gives me a pretty realistic depiction of weather right at most ILS minimums.Once you create and save your weather scenarios, under the 'Map' tab they will be available to you in the Drag and Drop Wx window. Makes it easy to fly where you want with whatever weather you want...much easier than having to manually do it every time in FSX's weather feature.

Darryl:To find the IP address your server is using, open the command propt in Windows (under accessories) and type 'ipconfig' without the quotes. In the first block of information you should see your IP address (for example: IPv4 Address..............: 192.168.1.73).In the Simconnect.xml, you will edit the block beginning with " <!-- Example Global (remote) IPv4 Server Configuration--> ". See mine below:<!-- Example Global (remote) IPv4 Server Configuration--> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <MaxClients>64</MaxClients> <Address>192.168.1.73</Address> <Port>500</Port> </SimConnect.Comm>In the lines highlighted in red, enter the IP address as you have seen in the ipconfig step, then enter the port you assigned for simconnect to use (in my case I went with the suggested 500).As far as the SDK, first install the SDK that came with the FSX Deluxe DVD, the install the service packs for it. You can find SP1A here, and SP2 here.Hope this helps. If you haven't setup networking before it may seem daunting, but is actually not that bad once you have done it once or twice. You'll be happy you did it, though, as the performance benefit is worth the setup.

Looking at the 757 in the product store, there is no 'Pro Pack" available, just a "Base Pack". Can anyone confirm that the fully functional FMS is included in the V. 4.4 base pack?

Those themes were from REX V 1.0 when this thread was originally started about a year ago. In version 2.0, go to the Theme Creation tab where you'll find a drop down box "Select a theme to install". The themes now are different, but they still can match up well with the ASA snapshot categories-for example they now both have "Stormy" as a theme.

What I would love to see as FTX makes its way into the U.S. market is a Yankee division of OZx. The availability of that many freeware airports that enhance FTX perfectly adds so much value to an already wonderful product. Hopefully we can put together enough fledgling freeware airport designers to have a community as strong as OZx.

I own the Majestic Dash 8 and would love it except for the VC. The textures are VERY low res...way behind the times as far as FSX goes. The steam gauges are barely readable. There is talk of issuing a patch to dress up the cockpit, but no projection on its availability.I think they showed the same attention to the systems and sound aspects of the machine that PMDG does. Unfortunately it is a FS9 native airplane that has been patched up to FSX. If I was spending this kind of money right now on a payware bird, I would definitely choose the JS-41. If you're looking for a Dash, wait for either the release of Majestic's new Q-400 version or for someone else to give it the treatment.

Jim,From what I understand, Mushkin used some of the same Elpida hyper modules that are failing at a very high rate. Try booting your computer without the flash drive using only one stick of RAM...do this with all 3 sticks in A1 slot, then B1 slot and finally C1 slot. You will probably find that two of the sticks will let you boot and one will not...if so, you have a bad stick and it is probably one of the suspect Elpida models. I hear that Mushkin has a great return policy where they will ship you replacements immediately without having to wait for the RMA turnaround of your bad RAM (unlike Corsair...I am still waiting for my replacements).

Mike:Do you have a link to the page where you can check your RMA status? I can't seem to find it.Thanks,Tim

You're not the only one Mike. I submitted my RMA request last week for the 1866 version with the Elpida problem, which they said I would receive a reply within 24 hours. After 8 days I called Corsair back and the Customer Service person emailed an RMA number with no instructions or return address. Where did you send yours back to? I assume they didn't give you the option to return them after you received your replacements like JK did from Mushkin...that would be my preference as I can still run my machine on the remaining 4GB of RAM...

After running MEMTEST again, I found one stick that would not POST when it was installed individually. After digging back into the Corsair forums, I found the announcement about the Elpida problem and my particular RAM was one of the models that was pulled. I am awaiting my RMA and hopefully the problem will be solved after replacing the RAM.As far as your 1600 RAM, if you have TW3X4G1600C6GTF, that is also one of the models affected by the Elpida issue. If not, I would say that your BIOS update cured the initial prob and that the current prob is just a result of clocking beyond its rated speed, as you stated.

Bob,I'm pretty sure it's not the clock or the timings...this occurred at the SPD of 1333, 9-9-9-24, DRAM V1.65 and QPI V1.21 (which also were the settings where it was working fine for that stretch). The problem still existed at Corsair's recommended 1866, 7-8-7-20, DRAM V1.65. I tried bumping up the QPI to 1.30 as well as reducing the DRAM to 1.50 (Intel tech support's recommendation) to no avail.Jackcnd,I have reseated the memory a few times, still no luck. I think I shall run Memtest on all of the sticks again just to be sure one didn't go bad on me. Perhaps there was a stick that was intermittently bad and it finally gave up.

All:I have recently built a new i7 975 system (Asus Rampage 2 Extreme, 6GB Corsair Dominator 1866, Nvidia 285GTX). Currently, both the BIOS and OS (XP64) only recognize 4GB of RAM.When I first built the system in late June, the BIOS would recognize all 6GB of the RAM about 25% of the time, all other boots would only show 4GB. In CPU-Z, however, it would always see all 6GB of RAM. I then tested all sticks individually with Memtest and they all tested good. I also tested a single stick in each slot...I found it would not POST with only one stick in A1 (B1 and C1 were fine). Asus tech support told me I had a bad slot and I RMA'd the motherboard to NewEgg.When I installed the new MOBO, all 6GB showed up fine. I checked both the BIOS and OS properties for at least the first 100 or so boots with the new MOBO, and every time they both saw all 6GB. I assumed it was indeed a bad slot...A few days ago, I decided to check back on the RAM. I was amazed to see the system was showing only 4GB again...I had made zero changes to the installation or the BIOS, nor have I overclocked yet since installing the new MOBO. For the life of me I cannot figure out what could have changed. In fact now, it is 4GB every time, and of course CPU-Z still sees all 6GB.From what I gather on both the ASUS and Corsair forums, this problem exists for a lot of people...but I have yet to see a soution. I am leaning towards a bad memory controller on the CPU, but the Intel tech support guy tells me that either it would be bad or not...it wouldn't have worked sometimes and not others.Have any of you other system builders seen this problem? And if you have, what was the fix? I am officially confounded, and I don't want to send the CPU back until I can better determine that is actually the problem...Thanks,Tim

FSX did perform better for me...not necessarily just because of XP, but a combination of that and having an OS with nothing at all running in the background. When I was running FSX in Vista, I did try to strip it down but since it was my primary OS it also had AV and other necessary every day applications installed that seemed to leave a memory footprint even after a manual shut-down. Running the OS barebones, Vista is still more resource hungry than XP so it would be logical to assume that it is a better platform for FSX.As far as the install, I only did one FSX install in XP. If you wanted to run it in both OS's, it would require two separate installs. So what I did was install Vista as my primary OS, then install XP and configure the dual boot. Once I had XP running and all of the XP updates/SPs/drivers installed I then installed FSX...simple as that.

Alan:I am one of those guys that likes Vista for day to day computing. I was running FSX in Vista until I got the Dreamfleet Dakota...wonderful airplane but absolutely refused to work properly in Vista for me. So on a whim and after scouring the tech sites I decided that I would give dual boot a try and start using XP for FSX.I bought an 80GB WD hard drive that was to be the dedicated XP drive and a VRap for FSX. My original RAID setup remained my Vista installation. I read about the way to partition drives and felt that it would be easier and better performance if I just went ahead and got separate drives for FSX.My XP installation was very clean...nothing but the barebones as far as overhead (no office, no anti-virus, no web plug-ins, etc...). The difference is amazing when you don't have all that bloat in your OS. And the real difference came in FSX performance-very noticable on my humble E6700 duo core. So with the dual boot you can have your cake and eat it too.It is not hard to do at all...take a look at these links:NeosmartAPCI followed these guides and used EasyBCD as my boot manager. You can either partition your existing drive or add new drives like I did. The only thing to be careful of is to remember that each OS sees itself as the C drive, so you have to keep straight the drive letter assignments in each OS. Just give each volume a unique name (the same in both OS) and you won't mix them up.I am in the process of deciding on components for a new build i7, and I plan on going dual boot again except with Vista64/XP64.Good luck and let me know if you have any questions.

Luis:Is there a way for the non-developer to create his own custom autogen layer to go with a photo scenery product? I have looked through the SDK and not found my answer yet...also looked at the description of Instant Scenery and didn't see anything that could accomplish this task.Regards,Tim

That's more like it!I have to believe that there was something off in the initial ASA installation that caused the original issue. Glad to see you are now seeing what I am with ASA and REX.Regards,Tim

Richard:Have you made any changes to the cloud options? If so, I would recommend setting them to their default values...it almost looks as though your "stratus cloud occurence" slider might be set to zero. Just set the sliders to the same settings shown in the Options section of the user manual.I have extensively tested REX textures with ASA and have yet to see anything like your screenshots posted above. See my attached screenshot below using REX Cumulus 14.One other thing you might try is to install a different, softer looking set of REX clouds, maybe even changing the install resolution back to 1024 and see if that doesn't affect your look...can't hurt and your performance will be better.Regards, TimBTW: Key settings for me in ASA are DWC enabled, Enhanced Route Coverage enabled, Fog Layer Generation enabled, Haze Layer disabled, Visibility smoothing enabled, max surface vis 50 mi, max upper vis 100 mi