Mozzy

I thought you were, that's why I added to the post. Thanks for the update.

Great post. Pretty well summarises the frustrations I have with the program.Work arounds are hit and miss. The only way I can successfully get good depiction is to:Start FSX THEN start ASA (all contrary to what's supposed to be done).If I change location the whole communication thing goes haywire.

Like to add my voice to this. Uninstalling FSUIPC seems to help but then I can't use Radar Contact. aghhh. I have to restart ASA/FSX when ever I change FS location. :(

OK, The new cooler is running nicel. My idle temps (and running prime95 for an hour) are usually around 8 - 10C cooler (no OC). I'm wondering about the difference across cores. Right now it's idling and RealTemp shows core 0 running a good 5C more than the others (9 greater than core2!)- 34 28 25 28. I asume this is because the first core works first before any other. The same seems to apply under load. Has anyone else noticed this? Is it normal?

>The stock operational speed is 0.8 to 1.36V for that>processor from what I see over at Intel's product info page>(double check just in case). It's entirely possible that the>BIOS doesn't observe that.>>Disable stepping in the BIOS as that can make reading values>difficult as the CPU steps down unless under load, which skews>your numbers and heat load.>>What I use on my X38-DQ6 and my QX9650 is a +0.1 voltage on>the FSB, +0.15 on the MCH (the hottest part of the entire>rig), and set the max voltage on the CPU before ratcheting up>the FSB speed. In my case that is 1.45V. There is a very>significant increase in heat produced any value over core max,>even very small (0.05V). Under load, my CPU gets close to 70C>in torture tests on four cores, and usually stays around 67C>after one hour or so. I have my BIOS set to shutdown at 75C>just in case (I think the default is 80C). You may want to>set that lower when doing your o/c test as a safety>precaution.>>You may want to see if there is a new BIOS version as well for>your board, as some of the readings may be improved in a newer>BIOS and the data tables for your CPU may have revised values>to use.>>Since you're getting a new cooler, you should see much>improved results. That will by far make the biggest>difference as the stock coolers isn't bad, but isn't great>either, especially the thermal interface.>>Cheers,>>Etienne>> Thanks Etienne,Very usefull info. My OCZ Vendetta 2 has just arrived...what a monster!! Should JUST fit the case :-eek

>Have a question: do you have the fan control enabled as a>BIOS option? If so, disable that and run it full blast to see>if that makes a difference.I have tried it disabled, yes.>>Second, on my board, the Gigabyte default "Auto" setting>enables what they call "turboboost", a mild overclock.Didn't try that.>>Outside of FSX which can make tweaking hard, I usually run a>torture test such as prime95 multicore or some of the other>diabolical tests out there to see what the board is doing.Yes, I have prime95 - in fact, that's how I discovered the extremely high temps when letting BIOS decide on the VCore. Only ran it for a few minutes. Luckily I was watching the temps!>>Third, the Gigabyte monitoring tools are known to crash the>system and can be inaccurate. Make sure you use the BIOS>settings in the CMOS instead of any software based tool>included on the CD that came with the board.Agree, I never use software Overclocking tools.All taken on board. Thanks.

Thanks for the input,I've downloaded Everest but haven't yet tried it. I'll post here once I get the cooler and try a little O/C.

Here's one for the experts.Just been experimenting with the new rig (see below) and discovered that, when overclocking (3.4ghz) and setting the BIOS to manual control voltage, my core temps go to around 65-67C when using FSX. CPU-Z reports the CPU running full tilt at 3.4.However, when I set BIOS voltage control to Auto the temps skyrocket to 75C with CPU-Z still showing the 3.4GHZ max.Surely 3.4ghz is 3.4ghz? Why is it throwing more at the CPU when on auto voltage control?Needless to say, I've gone back to default BIOS settings until my new cooler arrives. ;)

>>I think Jim is on to something with FSUIPC and Pete Dowson's>forum, I'd check that out.Could you point me to the relevant thread. I've looked through several posts but can't come up with anything relevant to visisbility.>>One thing I can tell you, (for what it's worth--I know we have>different cards, but both are nvidia 8-series), I am using an>8800GTX with the 169 WHQL driver and there is no white screen>for me. I'm thinking of going back to some earlier drivers to check on what I left behind. ;) Trying 174.74 here.

>And we also know that these are back with FSUIPC installed,>from Al's report at Pete's forum.>>Jim>>http://www.hifisim.com/banners/hifi-community-sigbanner.jpg>http://www.hifisim.com/Can't find anything on this problem over at Pete Dawson's forum. Do you have a link?Regarding bloom: I don't use it. I suspect a video driver failure, here.

>Do you use ASX? What happens if you clear the weather by>selecting the clear skies theme? And did you land on an add-on>airport?>It happened to me on my last flight and i don't think that it>depends on drivers. I'm using ASX and i landed at Zurich>(FSDreamteam) and clearing the weather helped me. >I will make my next flight without ASX.. did you install ASX>SP3?>>EDIT: sorry, read over "for a few seconds.". Then it could be>the driver thing. In my case the whole screen was white and i>only had the 2D instruments.Hmmm.... My screen went totally white in VC after an hour flight (Piper Cheyenne). The external visibility went haywire then the screen went white and was unrecoverable . The only clear view was the external "plan" view. I'm using ASX SP3 and FSX Acceleration. :(

>FSX has the ability to save your settings and then load the>ones you want when setting up a flight. This way you could>save a cfg with Lod-Radius set at 6.5000 and FPS locked at>30fps and save other cfg's with different settings.>As long as you don't try and change any parameter within the>saved cfg the Lod_Rdius setting will not default.>>Rod. Ahh...yes. That sounds a much better idea. Have to check out what parameters are saved within FSX.Thanks Rod

The only way I've managed to work with this is to have separate cfg files for different types of flying. I have folders named GA Rural, LVLD767, GA Urban etc that contain cfg files with the right combination of Autogen tweaks etc (including my prefered LOD of 7.0). Once I decide what type of flight I want I just copy over the current cfg with one from these folders.I've found the ONLY way to get crisp textures far enough out is to use the LOD tweak. It does tend to saturate RAM a bit, and flights take a little longer to load, but it's worth it. From what I've read, those with faster CPU's probably don't suffer this as much and leave there LOD radius at default.

Thanks for your input. Sounds like it should do the trick.

>Depending on the requirements for ASX (does it require>DirectX for its own display, etc), you could also run a>Virtual Machine with XP or Vista within OSX itself, and then>run ASX in the VM.>>You do need the deluxe version of FSX in order to run>SimConnect clients on seperate machines though and then you>need to install the SimConnect.msi file on your other machine>and then install ASX on it. >>If ASX requires direct access to FSX directory structure, then>you probably can't run it on a seperate machine at all.>>Thanks beatle,According to the documentation for Bootcamp, Windows runs "natively" as if it's installed on an intel computer, so I'm guessing installation of simconnect and asx should be painless. We'll see...my partner's new Mac should arrive any day now so I might "borrow" the Leopard discs to try it on my (now old) G4 mac.

As an extension to this thread, I'd like to know if it would be possible to run FSX on my PC and, say ASX, on a Mac running Bootcamp? I'd like to offload some processes to my mac, to free up my main CPU. I assume the main problem would be to do with SimConnect working across both platforms.Has anyone tried this?

I spend a bit of time flying around YSSY. I've found the three biggest FPS killers there (or any large airport)are: Freeway traffic, water and airport vehicles. Just try setting airport vehicles to 0 and see what a difference it makes. Although things look a little emptier you can still have a bit of AI (around 20% is good at Sydney using MTX) and set scenery density to "dense" - still gives you a few jetways.

>I hope you two guys have not purchased ASX in the last few>months after there has been so much written and verified>within these forums about the poor overcast rendering of ASX.>>>SteveBought ASX when it was first released.

I started a thread similar to this weeks ago. I've since been trying the Sp3 beta and still having the same issues. I've tried using FSUIPC's visibility and turning of ASX visibility smoothing (as suggested). Still have problems.* Weather is redrawn every few minutes* ASX takes about 10 minutes to parse the current weather (why?)Needless to say I'm an unhappy camper and I'm sick of trying to get it to work.Byemitchell

See for yourselfhttp://orbxsystems.com/forums/index.php?board=30.0

>Hi Emile,>>Can you please post or attach your ASX.cfg file?>>Thanks,>Jim>>http://www.hifisim.com/banners/hifi-community-sigbanner.jpg>http://www.hifisim.com/Hi Jim,Here you go. http://forums.avsim.net/user_files/183078.txt

>Hello,>On my system it happens at beginning of the flight (on the>taxi way pre-flight) , after take off, during flight.>I have the feeling it happens each time that ASX is changing>to the "nearest" airport.>Hope it helps>FSX SP2 NO ACCThose are my symptoms, exactly. Usually on takeoff. METAR: YWOL 092230Z 05010KT 10SM FEW024 SCT045 26/18 A3009ScreenshotsAt takeoffhttp://forums.avsim.net/user_files/183058.jpgAt 800fthttp://forums.avsim.net/user_files/183061.jpgAt 2500http://forums.avsim.net/user_files/183062.jpgAt 2700http://forums.avsim.net/user_files/183063.jpgIt appears as though it's affecting cumulus clouds?

Sorry to have brought this up again but I've been doing some experimentation with ASX and am still having the same issues. I've updated FSX to ACCeleration/SP2 and repaired SinConnec and reinstalled ASX.I also downloaded the latest FSUIPC and still got the problem - uninstalled FSUIPC - same: Still have clouds dissapperaing and reappearing, sometimes every 2 minutes.I'm at a loss here, and would like to hear from anyone else having this issue. It's driving me &^%$%# crazy.

More info.Flying around Melbourne (Australia YMML)METAR YMML 190630Z 29514KT 10SM RA SCT111 31/09 A2977Terrific climb out into a realistic grey sky with low visibility (see first 3 pics) http://forums.avsim.net/user_files/182127.jpghttp://forums.avsim.net/user_files/182128.jpghttp://forums.avsim.net/user_files/182129.jpg...then suddenly (pic 4).http://forums.avsim.net/user_files/182130.jpgI've also attached the log file.http://forums.avsim.net/user_files/182131.txt

OK,I did a short test.Here are the route METARDeparture (YSSY):YSSY 190300Z 07013KT 9999 FEW038 SCT058 23/13 Q1017 NOSIG RMK INTERPOLATEDYSSY 182227Z 190024 06015KT 9999 -SHRA SCT030 SCT045 FM12 36010KT 9999 -SHRA SCT025 BKN035Enroute:MQD:YCNK 190300Z AUTO 14005KT 9999NDV // SCT032 25/17 Q1016 RMK INTERPOLATEDYSRI 182223Z 190018 07010KT 9999 SCT025 SCT040 FM12 VRB05KT 9999 SCT020 RMKDestination (YSCO):YSCO 190300Z AUTO 33007KT 9999NDV // SCT039 SCT100 BKN115 24/15 Q1016 RMK INTERPOLATEDThe weather was consistent, with no abrupt changes, until about 20nm out of YSCO. Up until then there was a blanket of cloud below me at around 3000ft (My flight at 6000ft). I could see a cloud bank ahead of me (on the horizon and getting closer) but, all of a sudden, large clouds popped up in front of me.I had all default ASX setting except "Force Priority Processes" which I had checked and Downloads set to 30min.I'm wondering whether "Dynamic rate of change" is causing problems? If I set my route with appropriate METAR, surely the rate of change would be determined by onroute weather and nothing else?