Actually I think LM are working on the Premise of putting a whole bunch of monkeys in a room with a typewriter and letting them bash away at the key. Eventually you get the Complete works of Shakespeare :lol:

 

Anyway I am back to fiddling around with V2.0

IT LOOKS FANTASTIC!

and it is silky smooth on high setting.

 

Since I have it installed I will try the patching route since I went the Full install of 2.1 before.

The only issues I could find with 2.0 was the black screen and the stability.

 

Edit:

 

No just to clarify I am not comparing the Fine and Highly talented gentlemen at LM to a bunch of Monkeys.

Its the posters in the forum :biggrin:

 

 

putting a whole bunch of monkeys in a room with a typewriter and letting them bash away at the key. Eventually you get the Complete works of Shakespeare

 

No you wouldn't.  You'd get the Internet. 

 

Hook

 

 

Come on Noel, I know you know better ... there are endless threads about OOMs in FSX and P3DV2 ... not many on XP10 64bit front however   I see it all the time, XYZ says "this never happens to me" ... 3 months later after another thread from XYZ "my first OOM, help!"

 

Rob, that is an odd comment as the issue here is about why does 2.1 generate way more OOMs for way more people.   You've changed the issue from 'Why do OOMs now happen to nearly everyone' to 'Everyone will eventually get an OOM' in FSX and P3DV2.0.'  That's nonsense Rob.   I repeat:  I never came close to an OOM before.   Not even in the ballpark!   Now I can watch the VAS counter and it's just a steady increase until she blows and in a very short time.  2.1 is fundamentally different in this regard and if I had confidence starting w/ a fresh install of everything would solve this, I would.  But there is no consistent evidence that this is the case for anyone here that I've read, have you?  You selected my comment re not reinstalling everything.  Do you have ANY evidence this matters at all in this situation? 

No you wouldn't.  You'd get the Internet. 

 

Hook

 

Can I get a new typewriter? I bashed mine with a rock and now it OOM's.......

Well, I went back to V2.0 in my opnion this better than 2.1.
As the monkeys trying to write a work of Shakespeare is overdone, but I noticed people posting answers in forums LM, with great lack of education, lack of professionalism I thought, but I can not say that these people has a LM to proceed so as coarse.

But it still posts were not removed or monitored, as happens here
 

http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=5672

http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=5577.0

 

João Alfredo

An easy analogy with data types... using 'long' or 'float' all the time instead of 'small int' when small integers is really all you need. Software optimization skills come with experience.

 

4Gb of addressable memory provided ample space for a viable simulation as proven by version 2.0.

 

I know a lot of programmers (myself included), and I don't know a single one that loads up their classes with longs and floats everywhere instead of int out of laziness or misinformation (I have to think about it when I add a long, it's so out of character). Firstly, float isn't a replacement for either of those, due to imprecision. But more than that, I almost never see a long in any code at all. You generally use int everywhere unless circumstances dictate otherwise. Int is already huge, numerically. Could you replace a bunch of ints with shorts to gain some space back? I suppose, but it's certainly a diminishing returns type problem.

 

People grossly misunderstand the 32bit to 64bit application conversion process. It's not about going through the code and changing all the data types. The data types will work just fine as is. The real challenge is in changing your internal collections code (hand rolled if in C, hand rolled/STL if in C++) to handle the larger address space. In most cases, that's really just changing one or two data types (the collection index). In the ESP/P3D/FSX case, there's still legacy ASM in there and who knows what other god awful allocation code going on that is probably non-trivial to unravel. There's also the challenge of the bitness of third party DLLs, which would not be compatible any longer. Every addon would have to recompile their C gauges to link against the new libs.

 

I know I'm preaching to the choir here, but most people mistake this as a data type conversion problem.

 

-Matt

ANZ121 your post is right because to many people not happy and want good P3D now   but why   and it is because people pay for it.

 

If P3D is free nobody as right to not be happy but because people pay $200.00 I think people can ask for good P3D now.

 

Olga Vankranendonk

ANZ121 your post is right because to many people not happy and want good P3D now   but why   and it is because people pay for it.

 

If P3D is free nobody as right to not be happy but because people pay $200.00 I think people can ask for good P3D now.

 

Olga Vankranendonk

 

People need to learn once again (because it is a dying human trait), to have a little bit of patience. Yes, I understand frustration. Yes, I understand feeling a little bit let down as a consumer. Yes, I understand feeling that YOUR or MY needs are not being met immediately. Yes, I bought FSX and encountered the same frustrations with that as many did (and continue to do) as some are experiencing with P3D.

 

Regardless, there is no need for the rudeness, continual moaning and posturing that has been shown within the Avsim forums of late and is now starting to come through on the P3D forums. Yes, I accept it if somebody wants to delete the programme within 72 hours - that in itself speaks volumes of the moaner. But, I do not need to hear this time after time after time and in thread after thread. People need to grow up - Period. (And in terms of average age, I can assure you that the average age of the P3D purchaser base has dropped somewhat with this latest release outside of the original LM target market).

 

As somebody wrote recently in the P3D forums - you can either take the view of being the sad old victim, or you can take the time to contribute in a constructive manner. I know which posts I would rather read through.

 

As I said it really is quite sad to witness, especially as the team have been so engaging with the community. I wonder how long it will last before the kiddies or kiddie mentality kills it?

Now it would appear that I have gotten ride of the stutters!. As I posted earlier there was a romour floating around that the bluries could be cured by replacing the V2.1 autogen file with the autogen file from 2.0. I got the impression from the LM forum the Beau was skeptical about this because he seemed to suggesting that the only thing in the file that mattered .xml I believe was identical in both versions. Anyway about to give up on P3DV2 and shelve it for the time being I thought what the heck I give this a shoot.

 

Uninstalled V2.1 the associated files as per LM instructions and got really anal and searched the regedit.exe for entries containing Prepar3D and one by one deleted a whole bunch of Keys containing Prepar3D and Lockheed Martin. Spent about an hour at that and got sick of it so I didn't quite get them all and its risky too. right! I did see something that I thought was odd while searching registry entries and that was a few Keys that contained both Prepar3D and WinchX. For those who don't know Winch is an FSX addon for launching gliders with a winch. Fun though because I only had it installed in FSX on a different drive from the drive P3DV2 is on so why did it show up in a Prepar3D registry key? I read some speculation somewhere about FSX if installed on the same machine as P3DV2 that might cause problems? I didn't think so but given what I found perhaps it can?

 

 

After a reboot I did a fresh install of V2.0 and played around with it vanilla using the mouse as yoke and no trackIR and It was fantastically smooth.

 

Added the FSUIPC for my X52 and TrackIR and played around with it for a while got the black screen a couple of times and the Rt something or other error a couple of times 2 so the stability wasn't great but it was fantastic. Now I was blasting around at Supersonic speeds at low level in the F22and the autogen was great. Building and trees gradually appearing in the distance and I think that's gone in V2.1 :(  and only very slight blurries that disappeared once I slowed to about 250knots. And did I say smooth?

 

Anyway the whole point of the exercise was to harvest the Autogen folder so I could reinstall V2.1 and stick the V2.0 autogen folder in the v2.1 directory so I copied everything in the V2.0 folder to my dead storage.

 

A this point I thought instead of removing 2.0 and doing a full install of V2.1, I would try the patch since I hadn't tried that before. So following the instruction posted by Adam Breed exactly, I patched the existing V2.0 install.

 

Now I have to say I didn't really believe the people who claimed that it was perfectly smooth at 20FPS but now I have to eat my words or was it my hat?

 

The stutters are gone even at 20FPS at reasonable speeds.

 

I wasn't looking for blurred textures or popup because I ran out of time but stutters are completely gone!

I mean better than V2.0 gone!

 

I am sure that this will be getting sorted out in fairly short order and I hope this gives anyone feeling let done hope.

I will try to post some more info tomorrow

Not sure if it was mentioned, but LM did fix the widescreen cone for rain/snow.. now covers the whole screen.. but still looks like you are going into a vortex or wormhole

ANZ121 what is a little patience  when was P3D available for us 2 year ago right so I think 2 year after people are patient.

 

If P3D was release 6 month ago I can understand your post but after 2 year people are not patient.

 

When I buy P3D I was very happy for people simmer and I think it was good for 3PD to sell more addon and for us now after release of patch 2.1 addon do not work like before more broken Orbx last addon release is not advertise for 2.1 patch.

 

I think some people like tweaking and trying to fix P3D problem  just read all post here but I want to fly not look at forum to fix P3D  LM as to fix it but how long to wait 2 year again for some fix so 4 year and not sure if P3D is good for $200.00.

 

Is ok if you wait and you are good waiting again 2 year maybe more for what you expect for $200.00 but me will buy again if P3D can fly 90% more compare to tweaking.

 

People post here because of problem not because of flying P3D so people post less and fly more when P3D is good so people will moan less.

 

Olga Vankranendonk

I see a lot of complaints about backwards compatibility being broken... interesting.

 

You can't have it "all" people, you really can't.

 

 

ANZ121 what is a little patience  when was P3D available for us 2 year ago right so I think 2 year after people are patient.
 
If P3D was release 6 month ago I can understand your post but after 2 year people are not patient.

 

P3D v2 isn't P3D v1… P3D v2 has been released almost three months ago so… there is nothing wrong with being patient right now.  ^_^

I guess your PC is still intact and inside the building, Jeroen?

P3D v2 isn't P3D v1… P3D v2 has been released almost three months ago so… there is nothing wrong with being patient right now.  ^_^

 

I think what the woman is saying is that it's not a clean sheet design.  P3D1 is not P3D2 is not FSX is only true insofar as they are iterative versions of the same core.  Saying P3D has been out for 2 years, and the legacy FSX is 8, so get on the ball LMC (!), does not really strike me as some far-out perspective from an impatient whiner who can't wait 2 months.