It's been less than 24 hours. Why don't you consider this 'teething problems' and give them 60 days to sort out the issues. Let's give them the benefit of the doubt.

 

I did, hence why I turned to them for help. You have to expect some frustration and emotion to show itself in these situations. It's stressful sometimes when things don't go right. 

Seeing as though LM team are actually listening to the community this might just be the ticket to contribute and give feedback so the issues can be fixed.

Seeing as though LM team are actually listening to the community this might just be the ticket to contribute and give feedback so the issues can be fixed.

 

They've always been helpful. I read there mostly and tend not to bother them unless I need something..  I think a lot of people unintentionally forget (because of P3Ds ties to FSX) Lockheed Martin are not a game company and therefore don't (and can't) carry the stereotype "support" most game companies have. Most game companies setup a support forum ran by people who didn't even develop the game, or the email support is from a minimum wage point and click tech support person going by bullet point scripts who at most can "escalate" your case to someone who makes 50 cents more an hour.. With P3D's support forum you are literally getting help from the guys who sit and hammered out code.. 

Yes, the LM team seem to be a little more serious around the whole support thing but they do mean business. Besides, they, too, want to know when their product is not working the way it should.

COMPLETELY personal opinion.  But LM is a big company, like Thales and Raytheon, their focus is corporate business; billions of dollar type business, therefore by them opening up P3D to us (i mean they could really just structure it the way like CAE and others so that only corporate customers will get their software), you could say we are the subject area expert and knows probably more ins-and-outs of FSX than they do; heck we are a large body of nerdy mass who spends time looking at it without getting paid!  So by they opening this up to us, we could "help" them track down any potential problems and make their corporate products bug-free, and make some money on the way rather than pay people (who are less enthused about it) money to find bugs...

 

Just my opinion.

With P3D's support forum you are literally getting help from the guys who sit and hammered out code.. 

 

For that, it makes me felt the money well worth spent, although I haven't used their customer support yet.

 

The CTD problem I am no doubt the first or the only one, so I'll just hold off for their first patch (or alike) to release.  If I still find problems, I can speak up then.

 

Aside:  I really like the business/development model that KSP and Arma3 (and probably some of the DCS products like Huey and the new heli) employs; where they get a basic software running, then release it to the public (paid or free).  Through time they improve WITH their customers and the development is just ongoing!  If anyone know what kind of dev/bus model this is, please tell me, I'm keen to read it up as I'm doing something similar as well.

Brendan, it's pretty much the same model being used very successfully by SCS, a small development company in Europe. They interact with customers directly and make incremental updates every few months (sometimes more frequently).

SCS as in the Bus Sim (IIRC) company?

After installing some complex mesh and vector scenery I've been having lots of OOMs. I need to turn down the settings quite a bit to get the sim running for more than 10+ minutes. I have no water effects, only cockpit shadows, medium AI levels, and medium autogen settings.

 

What bugs me though is that P3D comes up with an OOM message before closing, but I can't find anything in the event viewer about what caused the crash. So, what I needed to figure out next was if the OOM came from VAS or VRAM filling up.

 

I suspect my GTX580 might not be able to handle the sim. It has "only" 2GB of VRAM, so I have lowered the tessalation to put less strain on it. Working OK so far.

 

That said, mesh loading is just as ugly s it was in FSX/P3D (I use 10m mesh). The building of the mesh in front of you as you fly is very obvious, and really takes away any gain I get from less autogen popping. Again, that might just be my computer running too slow.

 

I've also had a few CTDs happening when tuning settings and slecting stuff from the menues, but I haven't been able to duplicate them.

I am very sad. I am trying to run this software for 3 days. First, I've struggled to install. At the end, I couldn't install it without complete format and reinstall of OS. Now, I am having ntdll.dll errors at launch (start) menu (whenever I go to menu). This was one of the most difficult errors in FsX. I've tried several tricks but didn't work. I am also asking this to LM forum, but I don't expect them to solve it.  

 

I had v1.4 installed and working perfectly. It's hard to understand why v2 giving me hard times. I'll try for another couple of days, if I can't get it to work, I'll give it back and get my refund. 

26 hours of use (flying) in P3D 2.0 and no CTDs, OOMs or any other crashes.   Just the black screen error at the beginning.

 

I have sensible settings, that I know my system can handle.  

 

Saying that, all settings, from autogen, to traffic, and of course the new stuff like shadows, are ALL set higher than I had them in FSX.

 

Brendan, I can't really see the logic in cranking all settings to absolute max, to try to break it, then complaining and talking about getting a refund     - when it breaks.

Brendan, I can't really see the logic in cranking all settings to absolute max, to try to break it, then complaining and talking about getting a refund     - when it breaks.

 

I'm just going to take a random stab here and say by this comment here, you have no idea about software development...  Isn't testing is all about pushing your software to the brink and see how it handles, and trying to make it break-proof?

 

Let me put it another way - you buy a CPU that claims it's been stress tested for 48 hours and stable, to put in your new computer, you run stress test on it WITHOUT overclocking (running everything stock).  24 hours later, the CPU fries, does that mean you shouldn't expect it not to break within design specification?

 

Secondly, I invite you to go through all my initial post and replies, which one post/line/word makes you think i am complaining or demanding a refund?  Even so, you get a fried CPU that you are running within the expected envelop, do you just take a teaspoon of concrete and hold onto it, keep quiet and say... oops, I should have just trusted them when they say it's been stress tested for 48 hours, now 24 hours into the test it's fried, it's my bad :(

I'm just going to take a random stab here and say by this comment here, you have no idea about software development...  Isn't testing is all about pushing your software to the brink and see how it handles, and trying to make it break-proof?

 

Let me put it another way - you buy a CPU that claims it's been stress tested for 48 hours and stable, to put in your new computer, you run stress test on it WITHOUT overclocking (running everything stock).  24 hours later, the CPU fries, does that mean you shouldn't expect it not to break within design specification?

 

Secondly, I invite you to go through all my initial post and replies, which one post/line/word makes you think i am complaining or demanding a refund?  Even so, you get a fried CPU that you are running within the expected envelop, do you just take a teaspoon of concrete and hold onto it, keep quiet and say... oops, I should have just trusted them when they say it's been stress tested for 48 hours, now 24 hours into the test it's fried, it's my bad :(

 

Make as many personal assumptions as you wish Brendan. :smile:  Actually I was an IT Programme Manager for 20 years, but clearly I'm not as smart as you :wink:

 

Regarding the refund comment.   You said this :-     :rolleyes:

  

Yea I'm running defaults as well.  About posting to LM, I'm sure I'm not the only one, I'll give them 60 days to get it sorted

 

- there is still a vast lack of logic in what you were doing, by virtue of the fact that you're showing any surprise whatsoever when you got the crash.     

 

Anyway, I'll leave you to continue with your "testing".   I'm not interested in arguing with you.

I am very sad. I am trying to run this software for 3 days. First, I've struggled to install. At the end, I couldn't install it without complete format and reinstall of OS. Now, I am having ntdll.dll errors at launch (start) menu (whenever I go to menu). This was one of the most difficult errors in FsX. I've tried several tricks but didn't work. I am also asking this to LM forum, but I don't expect them to solve it.  

 

I had v1.4 installed and working perfectly. It's hard to understand why v2 giving me hard times. I'll try for another couple of days, if I can't get it to work, I'll give it back and get my refund. 

 

Did you try deleting the .cfg file?

 

Make as many personal assumptions as you wish Brendan. :smile:  Actually I was an IT Programme Manager for 20 years, but clearly I'm not as smart as you :wink:

 

Regarding the refund comment.   You said this :-     :rolleyes:

  

 

- there is still a vast lack of logic in what you were doing, by virtue of the fact that you're showing any surprise whatsoever when you got the crash.     

 

Anyway, I'll leave you to continue with your "testing".   I'm not interested in arguing with you.

 

As your responses have gone outside the scope of this discussion, it would indeed be a good idea to stop now and let someone else input their experience and their thoughts.  But it's ok Dave, I forgive you, you have a good day/night now

Did you try deleting the .cfg file?

Yes, I've tried that. I've downloaded package three times at different PCs just in case first one is corrupted. Install-uninstall may be 10 times. And nothing on PC now, vanilla OS with drivers and p3d. No addon whatsoever. Hell I even put uiautomationcore.dll into p3d folder (it seems this helped other user who is having hard times with fatal errors at v2).

One other strange thing is that default flight starts on the water not on runway. I tried to use it without going to start menu just like v1.4 but this also makes it impossible. I've changed default flight to something else but next time I load it started on water again.