gojozoom

Are those water drops on the prop? That's neat! Nice pics man!

Hi there, These issues are not related to weather engines, it's an FSX thing, here is the fix (worked like a charm for me): This fix is courtesy of Mike (haldir) over at AVSIM. It gets rid of the issue of cloulds popping in and out of scenes... Here are the instructions from him and my notes below ================================================= Quote: The ultimate culprit lies in the material handling of the cloud shader. Go to this folder: FSX\ShadersHLSL\misc There you will find a file called SwarmCloud.fx. Make a backup copy of this file somewhere. (as always no crying if you don't do this step) Open the original SwarmCloud.fx in notepad or wordpad and then look down about 20 lines down from the top. You will see this entry: bool NewMaterialUsage = true; Change its value from true to false. Make sure to keep the semi-colon. then add the following below the entry bool NewMaterialUsage = false; > = true; The entire section should look like this const bool EffectDeclaration < string Name = "SwarmCloud"; string Class = "Basic"; bool NewMaterialUsage = false; > = true; Save and close the file. Now, go to C:\documents & settings\<your username>\Local Settings\Application Data\Microsoft\FSX\ (If you can't get to this folder make sure that "show hidden & system files/folders" is turned on in your windows folder options.) (This is the XP path by the way, Vista users will have to hunt for their equivlalent in the users folder.) You will see a folder there called: Shaders. Either move that folder out of there or delete it. Don't worry, FSX will build a new one the next time you run it. It contains a cache of the compiled shaders. This folder must be removed to ensure that the change you made to the cloud shader file above will be compiled and used on FSX's next run. ============================================== Note: This fix can be undone by simply editing TRUE into the line as noted above. Also, I suggest you not delete the entire SHADER folder from C:\documents & settings\<your username>\Local Settings\Application Data\Microsoft\FSX\ as suggested and instead simply empty the contents of: C:\documents & settings\<your username>\Local Settings\Application Data\Microsoft\FSX\Shaders\Misc Of course be sure to backup the MISC folder I noted above before trying this so it can be restored -and- backup the original SwarmCloud.fx file in the Flight Simulator X\ShadersHLSL\misc directory. Dan

I've been using the cursed Logitech Xtreme for a long time. Then, I got bored with the need of re-calibrating all the time and bought the Saitek AV8R-02...man, it's night and day - so precise, I can finally do greaser landings... I have Saitek rudder pedals and throttle quadrant to accompany it.

With all due respect, both of the previous answers are wrong. 1.) It's actually doable fairly easily 2.) He's looking for Windowed mode not Full screen mode (I guess he's got a good reason) I'm running FSX in windowed mode with a hidden title bar too (also for good reasons) . Follow these fairly simple steps: 1.) Download and install AutoHotKey from here: http://ahkscript.org/download/ 2.) Create a text file with notepad with the following content LWin & LButton:: WinGet Style, Style, A if(Style & 0xC40000) { WinSet, Style, -0xC40000, A WinMaximize, A } else { WinSet, Style, +0xC40000, A WinRestore, A } return 3.) Save it as "titlebar.ahk" (not .txt) into C:\Users\xxx\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup (Win 7) 4.) Restart your computer 5.) Now you can hide the title bar for any program (including FSX) by pressing the Windows button and the Left Mouse button in the same time Tataaaaa!

With all due respect I wouldn't us the word "Bose" and "budget" in the same thread I'm not questioning the quality though...

+1

Let's have a look at the numbers: An SSD is capable of reading 6 gigabits per second If you install it internally the SATA III bandwidth is the same 6 gigabits per second If you use it externally with a USB 3.0 your maximum bandwidth is 5 gigabits per second (not guaranteed though) So -in theory- using an SSD through USB 3.0 would introduce a 17% performance loss (compared to SATA III) which is no THAT bad. However, please remember this: that deep gap between practice and theory is full of "We're sorry"s.

Hmmm, I've been testing this for a couple of days. My specs/settings: GTX750 SC, i7 CPU, 6GB RAM, DX10 with 4X SGSS at 1650pp and a stable FPS around 35-45. It doesn't seem to do anything spectacular for me... I start seeing FPS impact at 2.0 DSR factor but that's it. In terms of scenery/object clarity, it seems identical to my original setup.

Yup, I've been using that for 4+ years now without a hitch. The only problem is the vinyl layer on the foam that pretty much disappeared, but I don't mind.

GA: A2A Cub Tundra, Farichild 24 on floats Jets: BAE146, Albatros Military: A2A P-47, Aircraft Factory Albatros DIII

I've got the same problem... Tried playing around with Steve's fixer, FSWC, and REX, but nothing seems to change my inland water either....

Ok, be honest now, these are photos right? :o

Hi Adam, I'm interested. Could you put in a link to the post/screenshot you're referring to? Cheers Dan

Wow, thank you very much for this fantastic package.This is my all-time fav aircraft but wasn't flying much due to the overly "tricky" FDE, and lack of consequences when the engine was over-stressed. Now we just need a good whistling sound-set Thanks again, I'm looking forward to trying it this afternoon! Dan

let's

passengers

windscreen

Same thing here, IR leds, USB power, and WiiMote. 3 years going without a problem, smooth as.

Beautiful paint job there Ron, thank you very much for your efforts!

And my other issue -clearly visible on the latest animation- is that they came in way too low, so of course the speeds fell down when they were descending -100FPM instead of -700 FPM....

I don't understand...: "Hersman (National Transportation Safety Board chief) said analysis of the cockpit voice recorder indicated that until only shortly before impact, the pilots were unaware that the jet was flying far below the target speed and altitude for a safe landing. She added that there was no malfunction of the autopilot, auto-throttle or flight director systems." Also: "The National Transportation Safety Board has said pilots told investigators they realized the approach speed was low and set the auto-throttle to correct it, but realized too late that the aircraft speed never increased." So WHEN exactly did they realize the speed being low? And WHEN exactly did they realize that the change didn't help? Last second changes don't work with jet engines... It still seems like pilot error to me.....

I have similar experiences to Gabriel's. I've been using it for 2 years now, no crash at all... Same with the OOMs and other CTDs. I've haven't come across any of those so far....I guess I'm just lucky...

I'd like to add another aircraft tot he Awesome Freeware List: The Basler BT-67 from Manfred Jahn and his team (basler_bt67_v2.zip). It's one of the best turboprop simulations I've come across. Not many turboprop add-ons have a proper startup sequence animation out there... The VC is outstanding and it has a very nicely balanced FDE with a "heavy feel". I use it daily with AirHauler and I can't get bored with it.... Dan

I'd like to join the others in saying that your professional attitude is greatly appreciated! Thank you AVSIM team!

And you're right about it, all I'm saying is that we don't have to put so much emphasis on this while the other segments of the new product seem to be outstanding. Dan