How do you say P3D isn't "buggy", Vic, and where are you getting your metrics from on the number of people who are actually experiencing problems?

Edited February 24, 201412 yr by KingGhidorah

Rather be a constant praiser than a constant complainer. I found what works for me - if you haven't - too bad for you. Out of the 100's that are having OOM's - from what I've read, a great many of them *are* doing it wrong. There are also those who are just having problems no matter what they try. What you don't seem to understand is the 100's of people who are doing it right are busy flying not complaining.

 

In the DirectX 11 developer blog, Wes Bard promised that with the right GPU, we can easily max out the autogen sliders. Those who are trying to do so are doing it wrong?

Yep, I'm doing it wrong. Stock scenery, stock aircraft, stock weather. Omm! No oom before 2.1

 

But it must be us. Those guys insist that it is. Oh, but of course they turn stuff way down, because apparently the sliders are just for entertainment purposes, the entertainment being the ooms! Or maybe they are there so we can take pretty screen shots for the few minutes that the program runs before a crash.

 

The only thing that is really annoying me right now is the insistence that we who are having problems are somehow incompetent. We just can't figure out how to run the program. That inference is driving me nuts.

That's the problem with writing - some people take it as painting everything with the same brush.

 

I didn't say EVERYONE was doing it wrong. I said "from what I've read, a great many of them *are* doing it wrong"

 

There are a lot of folks who ARE doing it right and still getting issues. Generally, this doesn't mean that the PROGRAM is buggy - it means there are SPECIFIC system and USER issues. In this case, there IS a general issue with the autogen.

 

If you feel incompetent - that's your problem - I didn't say that everyone who is having a problem is incompetent - it's just that many of the posts I've read are from people who appear to be just barely computer literate. Weed those out and then you can define the problem.

 

Yes, I know it's prettier to run with sliders maxed and I am sure that LM is aware of that also. My issue is with the constant griping about the same thing until it escalates to posts that question how looing LM will last with P3D, etc.

 

Voice your opinion, stand up and be counted - sure - then adjust your sliders and go fly and have fun UNTIL LM resolves the issue.

 

There are a lot of folks here who are much sharper than I who are having issues - but they acknowledge there is an issue and move on - COMPLAINING AD NAUSEUM will not solve the issue. I am sure that LM gets the message but at some point beating the same old drum will provoke a negative response.

 

They have an update which has definite issues - they are working on it - does anyone here REALLY think that posting "what a piece of garbage P3D is" and "LM should be ashamed" etc is really going to accomplish something?

 

Wouldn't you rather be flying than complaining? Adjust and fly and give them a chance to fix the issues.

 

Vic

Let's say that I go to the store and buy a new flat screen TV and when I get it home it works fine for two hours and then dies.

 

I think it's just human nature to assume that all TVs of the same make and model are also "broken".

I think it's just human nature to assume that all TVs of the same make and model are also "broken".

All too true. The TV is a good example of my point though. Consider - You buy that HDTV and a few days later, the HD part dies and you only get to watch regular. You make your complaint, they say they will send out a tech. Now - do you continue to complain loudly how big a piece of garbage that TV and the dealer is OR do you sit down and watch regular TV while it is being repaired?

 

This is analogous to what is being done by "SOME" people with P3D. That is what I am responding to. I am just as frustrated as the next but I tend to enjoy what I have rather than complain about what I have not.

 

Vic

 Now - do you continue to complain loudly how big a piece of garbage that TV and the dealer is OR do you sit down and watch regular TV while it is being repaired?

 

 

That's an interesting take on things.  If I found out that others had similar problems, plus a host of others with that TV model, and then the technician came, and fixed some things while other things broke...then yes, I would probably start to get a little angry with that model and offput if others tried to tell me that I'm simply being malcontented.  At the very least, I would be mad at myself too, for falling for the hype and making a stupid purchase, especially if I had read the warning signs and chosen to ignore them. 

 

Probably I would to. Considering there is only one critical issues with P3D2 - I'd hardly call that a host of problems.

 

One last time -

Being unhappy is not the issue - ENDLESSLY carping on it as *SOME* have done is what I am referring to.

 

Vic

But Vic, you can at least see why people have a valid counterpoint to the some of the gushy threads with titles along the lines of "P3D is Mahvelous" that paint an idyllic picture of it, right?

Oh yes!! I am just as annoyed with them. It's a great program with a few issues AND most importantly, a team that appears to be willing to listen to feedback. They know it has issues and they discount anyone who says it's the next best thing to sliced bread as easily as they do the chronic complainers.

 

I'm just saying cut them some slack - at least LM is working on fixing the issues - what has MS done for FSX lately?

 

I really do think that P3D2 will be the sim of choice in the very near future. Reading in the LM forum, they've already identified the cause of the paging problems which cause the OOM's and are working on it. That's the main issue. Most of the other complaints can be traced to improper installation and/or setup or inadequate hardware. JUST like FSX, P3D really needs string hardware fore the best results.

 

I say that knowing that Rob Ainscough whom I consider extremely sharp and has top of the line equipment, is having issues that I don't see.

 

Patience is a big plus in this case.

 

Vic

zzzzzz, zzzzzz, zzzzzz :Yawn:  can someone please wake me up when P3D is sorted, thanks.

I say that knowing that Rob Ainscough whom I consider extremely sharp and has top of the line equipment, is having issues that I don't see.

 

 

There are some users who have more problems than most, for no apparent reason and that is unacceptable for a product such as P3d.

 

But other people have "apparent reasons". The "apparent reasons" include having display settings that are too demanding for the hardware, tweaking the cfg file, fiddling with NI, installing every add-on possible, OCing the CPU and even operator error.

 

With FSX I tried all the "apparent reasons" because the product is outdated and for me became terribly unstable. I eventually slimmed it down to work just with TacPack and it still crashes now and then, but it is usable.

 

With P3d, I have experimented with the "apparent reasons" and all I have gotten is more instability. One unusual feature of P3d 2.x (which may even be a bug) is the following. I am happily flying P3d without any problems (Yes, this is possible) and then I read a post about someone who got 1.27 more fps by setting FIBER_FRAME_TIME_FRACTION to 0.10 and well I just had to try it. Change the cfg file. Run P3d. It runs exactly the same. Of course on multicore machines that is the expected result. Stupid me for thinking that it is still 2007.

 

Then a few days later, P3d starts crashing with some goofy error and I can't figure out why, since I've made absolutely no changes to anything that affects the sim, except the FFTF entry. I delete the FFTF line in the cfg file and it makes no difference. P3d still crashes. I rename the cfg file and then P3d runs fine. I change all the settings back to way they were originally before I messed with FFTF and P3d continues to run fine.

 

Now how can this be? I assume that the template for the default Prepar3d.cfg is stored as a text resource either within the exe file or in a dll and when the app is run and it doesn't find a valid prepar3d.cfg file, it recreates it. But why does manually editing the cfg file do something weird? Even LM says when all else fails, rename Prepar3d.cfg, but why?

Good question. Same was with FSX. My guess is that it starts with certain variables zeroed out. Every time you run FSX/P3D and exit - it writes to the config file. Let's assume that some variable in memory didn't get cleared properly at the time of the write - next startup you have bad data. Same rationale I suppose it saying one should always start with a "clean" default flight and then switch to your fav a/c to be sure all variables are initialized.

 

We have been spoiled with FSX and P3d in a way, in that I think we sometimes forget how extremely complex the programs are. IIRC, Wes or Beau at LM said something like a million lines of code or more.

 

Vic

My philosophy is that Microsoft have been producing quality flight simulation software since the 90s and I will always be loyal to only a flight simulator that is from them. For me, FSX works perfectly and I will never be leaving them!

Why so many dislikes? :rolleyes: