NikkiA

The default autogen. That was the most frustrating aspect of my OOMs, I'm running default scenery library except for some korean air 777 flight plans. I haven't added any of my scenery because until it's stable with default, what's the point?

I think I've narrowed down my OOMs to either the vegetation slider or using AS2012 for weather. Both seem to cause VAS usage to steadily increase. Pulling the vegetation slider back to the middle position stopped the flickering trees in the rainforests, and kept VAS usage more steady (although, oddly, at a higher baseline of 2.05GB instead of 1.91GB). It meant that there was a very noticable circle of trees out to about 8nm from plane position, but that's life, it still looks better than FSX. Also using AS2012 for weather appeared to have a constant leakage of VAS - perhaps METAR strings aren't getting dropped from the sim. Using FSrealWX2 with a lower refresh rate gave good results without ballooning VAS. Also winds with AS2012 seemed very wrong, so perhaps something it's doing is messed up. Hopefully ASn/P3D will come soon. I'm still becoming very weary of P3D, after not being able to use it at all since december thanks to crashes, lack of working weather, and random other problems, to be left with a sim that is unpredictable and unreliable is a bad situation, whereas I haven't had a CTD in FSX for about a year.

Weird, I loaded 10 gallons of fuel into my C172 yesterday before flying, just fine.

'GMT time' seems to be an even more comical option than it was with 2.0, but at least weather works now, whether it's usable or not will remain to be seen over the next 2 days or so I guess e: lol, it's even more insano comical than I thought.... 'GMT Time' appears to do the following: take the timezone offset from your default saved flight apply it *forward* to the time of any airport you select (ie, if you save a default flight in GMT, then US east coast becomes 5 hours in front of GMT, rather than 5 hours behind) That's so insanely wrong that you have to wonder how hungover the guy was that day. Oh well, at least that bug can be fixed with a 3rd party launcher

It sure is good that FS9 and FSX are totally not linked to a defense industry company in any way. [/sarcasm]

Yeah, and what do you think happens when someone starts pricing things in a place where people aren't willing to pay? That's right, they vocalise their objection on forums.

Just a few more days until we discover which major (new) bug makes it unusable for another 2 months+ (probably more now that the refund period is well and truly over for 99% of p3d users) while they patch THAT.

But no, it can't. P3D in it's delivered form is still not FAA approved for training purposes, you need to pay a 3rd party integrator such as Redbird a lot more money to be able to use it in such a capacity. For one thing, the FAA demands a constant and guaranteed frame rate for simulation for certification purposes, P3d, like ESP before it and FSX cannot guarantee that. Neither is there any difference in implied liability, P3d is still sold 'as-is' and no liability by LM is taken. The stated usages of P3d are in learning about the physics behind flight, the basic concepts of piloting - without any implied use as a "simulator" as it is legally defined by the FAA, and for use by systems integrators to produce FAA approved equipment for simulation (leaving the sticky legal aspect of making it FAA compliant to the third parties). Given that redbird have used FSX and X-plane in the past for their FAA simulators, the state of P3d as a 'professional' simulator is no more or less than FSX and X-plane. Also, I'll point to the following disclaimer on flight1tech's page for the 737NG: So that extra $20 (or extra $80 if you already own the FSX version) does not pay for any extra 'professional' use, it's still an entertainment product at the end of the day.

Borneo, mountains, mist and lots and lots of forest... shame there's no (good) scenery for airports.

Will that work with moving scenery carriers (or worse, "AI carriers" like the OP is asking - which shouldn't really be called AI carriers since they're not part of the AI system) I can imagine saving on-deck works fine for Kittyhawk and the static carriers that Acceleration adds, but I'd be surprised if it works for the Accel Nimitz or the AI carriers ships (which don't even exist in FSX's world until AI Carriers tells it to add them).

Mmm, so likely that people in china are going to get sued over something like a license. :lol:

It's probably that you have a texture in front of you (ie, windshield or such) that is taking a second or three to reload on the camera change. You can usually improve the texture loading by tweaking the bufferpools. Backup your fsx.cfg and give Paul J's suggestion in this thread a go: http://forum.avsim.net/topic/364342-flashingflickering-of-scenery-textures

Well, it certainly looks like it's improved (never thought I'd say that after how long I've been watching fgfs), still not there with xp10 or fsx, but getting closer.

I don't know what it is, but I've consistantly had a problem with FSX's default scenery corrupting itself over time, a couple of years back it was TZs being corrupted and ending up with airports that were persistantly in the wrong timezone. Last night as I was just about to touchdown at SFO, I had the crash detection kick in and say I hit the airport boundary fence (I was at about 70'), and I saw the plane model instantly get moved from where it was, to ground level. Sure enough experimenting with various aircraft and altitudes, I needed about 150' at the end of 28L to clear the fence. Re-installing the Scenery folder from a 'just after install' backup fixed everything. But I really wish I knew what causes it, I don't often fly into SFO so I can't say for sure when the latest corruption occurred, but since this FSX install is only 2 months old, it can't have happened that long ago. Normally I'd suspect external things that fiddle with the default scenery - I've always suspected that the default nav data update out there was responsible, because it was the last thing I installed the two times I had the TZ corruption, but this time the only thing that's touched the scenery folder was AS2012 and a manual install of some ground textures. It's just really frustrating that these things happen - and invariably take so long to diagnose properly. I don't have enough experience with P3D to know if it will suffer the same problem, hopefully not. [Rant over :mad: ]

I'm a little concerned that their rigidity to the old fashioned release model is going to make for a very frustrating year ahead. Many of the bugs were complete showstoppers - the lack of working weather for example has kept me from using P3D at all in the last month - and would have benefitted from a more modern 'release early, release often' approach. As is it, I fear that we'll get to the end of january, and there will still be massive (and some new) show-stopping bugs that mean P3D isn't usable until april or so whenever 2.1 or 2.09 or whatever gets released. The old fashioned approach only really works when you have a sizable and representative beta testing team, and are confident that there are no 'show stoppers' at release. The initial release of 2.0 proved that isn't the case.

I hope it's accusim'ed, we really need an accusim jet.

Make sure you go to the engine maintenance page within the maintenance hangar - sometimes it doesn't directly indicate a problem with an engine component on the main hangar page - I had a problem with cylinder #2 not holding pressure that showed nothing wrong on the hangar page, for example.

Don't think so, the lighting and reflections in the water look better than the flight/fsx engine is capable of (p3d 2.0 excepted, but it's not likely that engine either). And the terrain looks more like some of their recent xbox titles, tbh.

removing files from the package cache can really confuse the MS Installer, and be very difficult to fix. It *theoretically* should be OK to delete the files once you've uninstalled p3d from the system if you do need the space (and it's a lot of space) back. Removing the package cache files while it's installed, will render the installer unable to uninstall p3d, and require a pretty invasive manual uninstall from the registry and even then doesn't guarantee things will be truly gone. If you have some way to archive them somewhere where space isn't so important (another drive, 2DVDs or 1BD-R), then I'd recommend that.

I had to ask for a reset on day 2, since I installed / uninstalled 2-3 times on day #1 trying to fix the 75C weather bug - noone else was reporting it, and everywhere I asked if others were getting it I had no response at first, so I assumed my simconnect was corrupt. In the end, I totally borked both my p3d and fsx installs because I had simconnect missing, but thinking it was installed, so had to reinstall windows, and bam, 'unable to activate' They responded fairly quickly, but I got quite a chiding email from them. They *say* that it should detect same machine reinstalls as being the same machine, and not count against them, but if that's the case, there is an activation limit of '1', which is a bit insane IMO. It's the first thing that really disappointed me (the second being some a/c that won't work that I'd love to use in p3d as well as fsx).

Well, I was getting that same CTD if I left it inactive, and disabling mute on loss of focus has indeed stopped the CTDs, so I honestly do think it's the same bug, worth testing for HighTowers anyway.

It's almost certainly this one: Remember FSX/P3D cuts audio when you defocus the sim, which is almost certainly implemented as the Direct3D sound object being disassociated from the sim.

Makes sense IMO, given that P3D2 has better support for external flight models, and turboprops are notoriously awful in FSX using the default flight model

The way a pitot tube works is that it compares pressure of the air hitting the front of the pitot tube (which is forward facing in the airstream), with a reference 'static' source of air (ie, just the regular outside air pressure, but not moving in the airstream - hence the name static). This is usually done by an air resevoir somewhere on the body of the aircraft, that has a vent to the outside. Because vents tend to freeze over, a second air resevoir is often fitted that becomes the 'alternate static source' or 'alternate air'. I believe the alternate port is usually heated to avoid the vent icing over, but I'm not certain. Anyway, having two static sources in case of the primary freezing is a requirement for IFR equipped aircraft.

I've been using Open Clouds 'free til xmas' for the time being, since it works around it, haven't seen any problems between it and FSCaptain, and the metar reports for arrival seem to be correct. But yeah, the 75C thing is an annoying 'bug', and it's a little disheartening that LM haven't addressed it at all so far. Hopefully ASN will have a (temporary) work around because I'm looking forward to it, and there's no way LM will release a patch before monday.