igorbischi

Do you have vista?

Did anybody test citation x on fsx + vista? I'm not able to start left engine (the right one is ok). I followed the chek-list step by step, but nothing happend...igor

Thank you. I dont' understand why fsd didn't give to me the same answer. They said no fsx vista + navajo owner reported such problems. I hope the service pack will be out soon.

Does anybody have this aircraft in fsx? I have problems I wasn't able to solve with fsd tech support. In virtual cockpit:- I'm not able to activate battery switch, neather auxiliary fuel pumps.When I press one of these button they immediatly return to off position (in 2d cockpit they operate correctly).- it is not possible to activate most of lower switches/buttons:transponder, adf, nav/com audio panel. I tried to change views (A key), to move view position inside views, but no effect.I installed it on fsx+vista (a clean fsx, no other addon) and on fsd+xp: same behaviourAm I the only one in this situation?Igormy spec:Intel Core 2 Duo E6400ABIT MB AB9SAPPHIRE X1900GT 256MB2X1GB DDR2 Corsair PC5400Hard Disk Hitachi 250GB S-ATA2

We know, fsx is young... but how much time do you spend to configure, tweak, improve performance, etc. instead of flying? For me it is about fifty-fifty. Too many hours...And you? What is your score? I would be interesting to have a little survey.Igor

You are right. For me both solutions are good. Setting aircraft_reflections=0 without disabling shader has the same effect: no reboot. Maybe there is some difference between x1800 and x1900.Thank you.Igor

Problem solved!:By Attray, a radeon vga tweak utility, I set pixel shader ovveride option to version 2.0. No more CDT in fog/rain condition.It really works!

Search my post, in CDT forum. I have a similar problem with my x1900 ati vga. Other people have reboot problems with X199X ati cards; no solution at the moment, I hope new catalyst will solve it.Igor.

I have 6.11, same behaviour with 6.10.As I supposed you have an ATI card, X1900 like mine. I hope there'll be a patch, either from microsoft or ati. This i a very disappointing bug!Igor

I have a similar problem. My pc reboot in dense fog weather, or rain+overcast, expecially with SR22 eaglesoft. I think it is something related to ATI card/drivers. What are y spec?mine:Intel Core 2 Duo E6400MB ABIT AB9SAPPHIRE ATI X1900GT 256MB2X1GB DDR2 Corsair PC5400Hard Disk Hitachi 250GB S-ATA2Igor

>I think it's a video card driver problem but have you checked>your RAM and/or your system performance settings. If your>pagefile isn't set to "System Managed", you may not be>allocating enough with your own setting. A lot of people>(including me) like to tweak performance settings based on>"expert" advice in XP books/blogs on the Internet but I've>seen more CTD's happening when this setting is changed to>anything other than "System Managed".>>Since the CTD only occurs when running the Eaglesoft SR22, it>could be a bad install or corrupted texture file. Have you>tried uninstalling/reinstalling the SR22?>>Best regards,>JimThank you Jim,Pagefile is system managed.I did disintalled/reisntalled not only sr22, but FSX as well. Same problem. But in the meanwhile I have discovered something interesting: the only way the PC doesn't crash in the three situations is if I disable dxt3 texture from catalyst control center. As result I have a very very bad (unable to fly) video output. If I remember well SR22 has dxt3 texture, maybe this is not accidental!Igor

The following three conditions makes my pc to reboot:1) eaglesoft cirrus sr22 in VC2) bad weather, overcast and rain3) any shift1-shift9 to open 2d-subwindowsWhen I press shift-1...9, any of them, the pc freeze for about 5 second then reboot.I tried everything: direct X update, all possible video card and fsx settings, direct x settings (sound acceleration, ecc.), latest catalyst drivers, omega drivers, etc. etc.Anyone with this problem? Any idea?Igor----My spec:Intel Core 2 Duo E6400MB ABIT AB9SAPPHIRE X1900GT 256MB2X1GB DDR2 Corsair PC5400Hard Disk Hitachi 250GB S-ATA2

Still stuttering... after:- disk defrag- direct x last update (october 2006)- a lot of video card different settings- several experiments with .cfg (poolsize, fiber frame, texture... etc, etc: best result - little less stuttering - with PoolSize=200000, FIBER_FRAME_TIME_FRACTION=1 and TEXTURE_BANDWIDTH_MULT=10)- texture replacemente (www.fox-fam.com)- process priority & cpu affinitynote: Autogen off, ever.spec:Intel Core 2 Duo E6400ABIT MB AB9SAPPHIRE X1900GT 256MB2X1GB DDR2 Corsair PC5400Hard Disk Hitachi 250GB S-ATA2Windows XP-SP2... halloween nightmare ...

On the contrary, on my system I have a little better FPS result with no limit frame rate setting.Stuttering: have you tried to change FSX priority/process affinity? I read some post in another thread, but I have'nt tested it yet.Igor

For me 5m textures o whatever else makes no difference. sigh :(Igor

We have different systems but same problems. It is hard to understand why we have stuttering. Do y have stuttering whith demo 2? I don't. I had worse frame rate but no stuttering.Igor

I tried EVERY possible tweak (fsx.cfg, textures, ecc) to solve stuttering problem, but nothing happened. Then I virtually dismount my pc di find out any possible problem (firewall, antivirus, other cpu related issues), but still stuttering, even with sliders all to the left.My spec:Intel Core 2 Duo E6400ABIT MB AB9SAPPHIRE X1900GT 256MB2X1GB DDR2 Corsair PC5400Hard Disk Hitachi 250GB S-ATA2How many we are?Post your spec, please.Igor

In the 2nd mission, after landing, I saw a 747 taking of from 09, but the flight lasted a few seconds, because of the mountain ... did y notice it?Igor

Ok, I think it's better to hope in FSX ...igor

Ok, thanks.Maybe someone has an answer ...igor

Is it possible using afcad2 to inhibit, on a single runway airport (lirq, 05-23), landing on rwy 23 and take-off from rwy 05?I open afcad, list the runway, select 5/23 and click properties. On reciprocal end sub-menu, designator 23, I check closed for landing. On base end, designator 05, I check closed for take-off. I save the file. When fs9 start, it generates news file... but on lirq nothing happens, my ultimate traffic ai (when I force proper wind conditions) lands on rwy 23 and take-off from rwy 05. I need some help. Where is my mistake?Igor

In my case it was 5/10 :)Next time i'll try a very fast turn to 015.Igor

Thank you for your observations. I think i'll use notam "trick" to avoid the problem. I tried a couple of IAP approach to lime (ILS-Papa Rwy 29. a nice 15 DME arc from ORI-VOR, localizer interception at 13 miles, 4000 feet); no problem at all. I have jeppesen sid/star/enroute charts, and all the available italian freeware and payware scenery airports :-) Igor

Some new about the lirp-lime flight.I had two new flight (same flight plane). The first one was ok, RC4 did a good job, so I was vectored to intercept the localizer about 20 miles SE from lime. The second one wasn't right. I was told to descend to FL120 within 30 miles (I did in in 15 miles). Then approach gave me instruction to descend to 9000 (if I remeber well) and then to 6000, and gave me 015 heading. Few minutes later I was vectored to intercept the localizer (heading 315) at about 13 miles from lime, mantaining 6000 feet with qnh 1009 (like in the previous flights). Here:xoomer.virgilio.it/igor.bischi/Screenshot.jpgxoomer.virgilio.it/igor.bischi/Screenshot2.jpgis a link to two screenshots. The first one is the plane cockpit a few second before ILS clearance to runway 29. As you can see, the glide-slope is already centered. The second one is the fsnav screenshot of the plane position taken in the first screenshot.Thank you (and good new year).Igorp.s.apart from this issue, RC4 is a very good improvement from RC3!

To be honest, when I wrote yesterday I remembered FL120, but I'm not sure, maybe it was 110. I didn't ask anything to approach. I was told to expect vectors to runway 29. I didn't make any special request, only a "default" ILS vectored approach. Maybe the only difference between my flight and your is the localizer intercept distance: 13 miles for me and 17 for you. I'll check it again with a third flight and then I'll tell you.Thank you.Igorp.s.in the RC4 options which aircraft type did you set? I set turboprop. Could it modify the approach localizer distance policy?>Hi Igor,>>I just flew your plan without a problem but there was one>major difference.>>70 miles from LIME I was given a crossing restriction of FL110>(a nearside crossing restriction so RC was intending to send>me to rwy 29).>However you were given a crossing restriction of FL120 (a>farside crossing restriction suggesting RC was intending to>send you to rwy 11).>When you contacted approach were you told to expect vectors to>rwy 29 or did you have to request that runway?>After contacting approach did you make any special requests>(an iap, a short final?)>>Approach gave me initial instructions to fly heading 015>descend to FL90 (when about 36 miles from LIME).>I was then assigned FL80, then FL 70 then altitude 6000.>I was then given the 315 heading to intercept the localiser>which I did about 17 miles from the airport, just after>intercepting the gs.>Not quite perfect but almost.>>All the best,>>John