piotre

YES

>where do you get it from?>http://secure.simmarket.com/product_info.p...roducts_id=2140Cheers,Pietro.

Yes there's an error in Francesco's install instructions, he admitted to it and apologized in his blog (http://aliditalia.blogspot.com/ in Italian only).Basically you should first create manually a folder called "Italyregionspack", either in your FSX folder (as Fabrizio suggests) or in the Addonscenery folder as Patrick says, or wherever it is you keep your third party sceneries.Unzip "italy_regionspack_for_fsx.zip" in the folder you've just created and activate the scenery as usual from the scenery library.@Patrick Sardinia, together with Sicily and Puglia (Italy's "heel") are still arid because they're the aridest regions in Italy and Francesco decided not to change the textures for those areas.Have a look at the picture "regions.jpg" included in his install to see which parts of the country were modified (the green parts have been changed, the yellow ones are still default).Cheers,Pietro.

>What line are you adding?>I do not remember how it was in FS9.Add the line MipBias=6, so it looks like this (substitute square brackets where appropriate): MipBias=6Mode=1024x768x326 is the setting the OP suggested, I've tried 5 and 4 with no real diference. No shimmering here unless I set filtering to anisotropic, so I use bilinear with works well for me.No real FPS increase here after the tweak, but certainly sharper textures and less blurries.Anyway, FSX is a strange beast tweaking-wise, what works for someone may have opposite effects for someone else. I have a hard time getting consistent result from session to session on my rig ;)Pietro.

>Be careful though, some badly calibrated joysticks will>'shimmer', meaning that even though it's at idle, it's not>fully at idle and small vibrations on your desk causes it to>appear as if it is vibrating (in the VC.>>If this happens, hold F2 so that the throttle action on your>joystick doesn't accidentally disengage the reverser's. Yep. I also had this in FS9 with my controls (CH Products Pro throttle, pedals and Fighterstick, the OLD gameport kind, not USB), but it got much worse in FSX where I was simply unable to set my throttle at idle. That meant no engine reverse and no chance of stopping the seaplanes in the water unless I killed the engine. No amount of calibration cured it, I finally solved it by getting FSUIPC4 and using its calibration utilities. F2 works like a charm now.Pietro.

Ron, apparently there has been a spate of new ATI Cat driver releases in the last few weeks as I had upgraded to 6.09 the day I installed FSX :)However, the latest I see are Cat 6.11 released on Nov 15, 2006. Where did you get the 6.14?Pietro.

I do have an ATI X800XT 256Mb (Catalyst 6.09) and it happens to me too, but only with some payware planes, always in bad weather.Pietro

I think Carlos hit it right on the head here.I too am one of those disappointed by FSX's performance, especially as MS own Windows XP Game Advisor tells me my PC is among the top 20% on the market, yet I can't get it to run satisfactorily with mid range settings.BUT, in all fairness it must be said that those tests were run at very high resolutions and - more importantly - without knowing how the sliders were set, not only the tests don't tell it all, they actually don't tell very much.Pietro.

>PS: I have found no disernable difference in fps with>reflections on or off on my system.I don't think there should be any difference in terms of FPS.I believe the window reflections are not "real", that is they don't change with the angle of the sun, there are no computations involved, no extra GPU processes; it's simply a fixed texture, whose size we didn't change.As long as the reflection.dds texture is loaded, nothing should change in terms of performance. I don't know what would happen if the reflection.dds file were to be deleted.Your tweak is much welcome however as I too thought reflections were a bit overdone in FSX.Pietro.

>It happens in all FS9 compiled aircraft that I tested and it>doesn't happen in FSX compiled aircraft. I think you may be on to something here.It also happened to me with the Realair Sf260, never happened with default FSX planes, and it only appears with reduced visibility. And the problem comes and goes, sometimes it goes away by itself, sometimes it sticks.On the other hand I'm wondering, may this have something to do with the fact that the ATC window goes blank now and then (the lower part where you can select your options), and only in bad weather?I have an ATI X800XT with catalyst drivers v6.9. Pietro.

I didn't really like this mission all that much, and I can tell you I passed by saving a lot.Running out of time has never been a problem of mine here, breaking the plane was :D You do need some extreme maneouvering here, try to keep your speed between 180/240kts and you shouldn't overstress it. Use the speedbrake if you're too fast and need to pull some G's.I went through all the targets in the same sequence that was presented to me by the sim, and found I had time to spare (at times even 3-4 mins). I did take adwanteage of a few extra bonus targets that were close by - and you should too - but I did't fly around looking for them.There are a few tricky spots where the targets are placed close to buildings or hidden by them. If I couldn't see the next target I paused, switched to outside view, panned around and studied a strategy. Then I saved and tried it.Hope this helps,Pietro.

>I don't get the blurries with an old 128m 9800pro.>I wonder what the AGP aperature is set at in the BIOS.>Something is irregular somewhere. Yes but what is the right answer here?I've read many times on these forums that your AGP aperture should match your video RAM (the higher the RAM, the HIGHER the AGP aperture should be). But I have an ATI X800XT with 256MB and with aperture set at 256 I get a lot of blurries too.Yet again, if you do a search on sites such as 3Dguru.com or tweak.com they tell you that the higher your video card RAM, the LOWER you should set your AGP aperture.So which is which?Yours puzzled,Pietro.

I've only had that happening to me in missions, so I thought it was beacuse of some mission-specific scenery being activated.I have 2GB of RAM too.Cheers,Pietro.

Same here, it happened to me with the RealAir SF260: I thought it was because it needed a specific upgrade to FSX. It never seemed to happen with default panels.And yes, it only appeared to happen in heavy weather/low clouds/low visibility conditions. Pietro.

>Er... anyone read my tip to Alt-Enter to windowed mode (and back)? That worked for me...Nope, tried that but it didn't work for me...Still scratching my head on this one,Pietro.

The above two fixes both work, but searching for the original post (linked on P-12C Pilot's blog) brings up this message:"The page you requested cannot be displayed. Missing Topic"Pietro.

>looks like I'm off to Peru. I'll have to>put my Paddington Bear duffle coat on :-)You'll also get a patch (mission reward) for landing at SPRF (highest airport).Other patches are awarded for landing at LLMZ (lowest airport), NZPG (southernmost), CYLT (northernmost), SCIP (most remote).Pietro.

>I agree... FSBuild is tops in my book. Ernie's has done a>magnificant job!Does it have moving map capability (

>Try this for throttle:>>When you calibrate the program tells you to place the throttle>all the way back towards you (minimum). Do not do that.>Instead place the throttle ALMOST to the back stop and click.>This works on my CH Pilot Pro yoke.>>Dick near 5G8>Thanks Dick, I've already tried that: it helped but not enough.I will try the CH Control Manager though I don't think it will work with my old controls.Pietro.

>Yes, I am in agreement with you. It's the same on mine but, I>believe it is down to the default FDE.Agreed, I was able to break (overstress) the A321 in flight during the INITIAL CLIMB (!), by simply flying straight up with take off power and at 15

I'm experiencing the very same problem, and it does happen in free flight.And no, pressing the 1 key, or the any other key for that matters, doesn't solve the problem.This has already been reported on the forum, but no definitive solution seems to have been found, though somebody said that clickng with the mouse on the ATC instruction (or on the blank part of the ATC window, I can't remember) cured the problem.It only seems to happen on IFR flight plans, and it takes a while to show. Sometimes, the problem cures by itself if ATC gives you another instruction (as may happen during final approach when ATC issues a series of instrucitons). But if you're in cruise, your out of luck: radar service terminated.Certainly something to report to MS.Pietro.EDIT: OK I've found the link to the previous thread, scroll down 'cause the first posts are about taxi lights.http://forums.avsim.net/dcboard.php?az=sho...ing_type=search

> No. Whats Australia?? ;)Naughty! :-hah Pietro.

I think the most important parameter as far as stutters go is the poolsize number.Yours is set at 1000000 (1 million), but I believe the recommended value was actually 5000000 (5 millions). I've also seen users setting it at 10mln and I personally use 2500000 (2,5 millions) with good results.Another anomaly is the "texture max load= 512". I may be wrong but I thought that specific tweak was for FS9 only, and anyway the recommended values were 8 or 10, much different from what you have.Cheers,Pietro.

All I can say is I changed my drivers and didn't have to reactivate.Pietro.

ATI radeon X800XT with latest Catalyst 6.9 here.Must check this evening, I had FPS capped at 25, maybe that's why I'm not seeing that big a difference. Agreed it looks better than the FSX FPS counter shows though.Pietro.