I remember 3PD telling they do not make addon for XP10 because all new XP10 patch release break 3PD work.

 

P3D is making same as XP10 for 3PD.

 

Olga Vankranendonk

 

 

With all the scenery add-on's that is available, I think a 64 bit app. is ESSENTIAL.

 

In the same toke, it doesnt matter if you have a 2000 bit FS if an app isnt properly coded for the sim.

In the same toke, it doesnt matter if you have a 2000 bit FS if an app isnt properly coded for the sim.

 

It actually does matter a lot when you consider the VAS limitation still exists within P3D. So no, it is not the same toke - something has to be done to re-code the old FSX rendering engine that is also used in P3D. If not, the frustration levels of users, and ultimately scenery/airport developers is going to come to a head.

 

I am at that cross road now where I have to decide which road I am going to embark on. P3D would have been my obvious choice if a 64bit option was ever in the pipe line. Unfortunately that does not appear to be the case and as such I'll take the knock (in terms of apps not working cross platform), and move to X-Plane 10 64bit. Where I can become part of a larger community that will take X-Plane to new heights (this is only in regards to more developers making scenery and quality add-ons for X-Plane). Really looking forward to a long haul flight with scenery/add-ons etc where I don't have to worry about an OOM towards the end of the flight!

 

This is not a contest to see which is better but merely stating a fact that something needs to be done to blow some new life into the old FSX rendering engine.

 

Cheers,

That should work but I've had trouble w/ getting user-created profiles to work and I never have investigated why, so I just jumped to modifying the GLOBAL.

 

 

Creating a user profile worked. Your settings looked nice, except that the shadows were slightly jaggy, especially in the interior of the aircraft. Even setting shadows to Ultra made no difference. It's a minor point though, since the overall look of the sim is improved by using the settings that you listed.

You can stay with FSX like programs - get taunted with great airports and scenery that you simply can't use without worrying about an OOM.  Wonder how many people with lots of scenery etc. live with this frustration!!!

The choice are yours and I think as long as we support an application that in the sense of memory handling,limited you in what can be achieved, the developers will not care about us and continuing selling products that is a potential time bomb waiting to go off and explode in everybody's face's.

And it already happens.

The simple fact is that you can't get away with the 4 gigabyte VAS limit.

And with all the scenery's that are available, it is not possible any more to do a flight from A to C, overflying B, without getting an OOM on your final approach to C.

Oh, you can use an auto saver or save your flight manually, but what if you flying on VATSIM, saving the flight ,flying the ILS approach and get an OOM?

 

If somebody can address that 4000 megabyte VAS limit, by all means I will buy that product.

XP already done that by going to 64 bit.

 

 

Creating a user profile worked. Your settings looked nice, except that the shadows were slightly jaggy, especially in the interior of the aircraft. Even setting shadows to Ultra made no difference. It's a minor point though, since the overall look of the sim is improved by using the settings that you listed.

I think it depends exactly what angles the shadow edges are coming in at.  Sometimes they are razor sharp and other times slightly soft/jaggy.  Anyway glad it's helping for you.  I'm still not very happy w/ water, though it's very cool up close ;o)

Xplane 10 already took the 64 bit path, why not P3D?

With all the scenery add-on's that is available, I think a 64 bit app. is ESSENTIAL.

I don't think you'll find anyone who disagrees with the rationale for L-M coding a 64bit version...

 

However, keep in mind that Austin didn't just wake up one morning, flip a few switches in the compiler and make a 64bit build of X-Plane! It took several years of hard work to refactor the source code such that both 32bit and 64bit versions could be compiled.

 

Wes Bard of L-M stated unequivocally last month that a 64bit version will come eventually, but quite properly refused to commit to any time line, since he honestly cannot determine such at this juncture.

I don't think you'll find anyone who disagrees with the rationale for L-M coding a 64bit version...

 

However, keep in mind that Austin didn't just wake up one morning, flip a few switches in the compiler and make a 64bit build of X-Plane! It took several years of hard work to refactor the source code such that both 32bit and 64bit versions could be compiled.

 

Wes Bard of L-M stated unequivocally last month that a 64bit version will come eventually, but quite properly refused to commit to any time line, since he honestly cannot determine such at this juncture.

 

That is very good news. So there is a light in the dark tunnel after all.

 

I'm fully aware that coding a 64 bit application is not like waving a magic wand and hey, presto!

Eventually Microsoft will drop it's support for FSX and with that the activation process too.

 

That is why I had so high hopes for LM's P3D.

And to know the fact that they are looking at a 64 bit P3D is very good news after all, regardless the time frame.

 

Regards,

 

Johan

Wes Bard of L-M stated unequivocally last month that a 64bit version will come eventually, but quite properly refused to commit to any time line, since he honestly cannot determine such at this juncture.

 

Can you quote what Wes Bard actually said? The last statement  I've seen from  Wes Bard on January 20, 2014, 16:33 read

 

 

"We haven't announced anything on a 64bit version yet, just that we're looking into it..." 

 

         :

Can you quote what Wes Bard actually said? The last statement  I've seen from  Wes Bard on January 20, 2014, 16:33 read

 

 

         :

It's been pointed out to YOU before. What part of the YES that he wrote did you / do you not understand?

I'd rather they fix feature memory bleeds on a 32 bit platform than deal with sloppy programming on a 64 bit platform. Programmers tend to get lazy when resources are plentiful

Can you quote what Wes Bard actually said? The last statement  I've seen from  Wes Bard on January 20, 2014, 16:33 read

 

 

         :

See here:

 

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

 

 

I'd rather they fix feature memory bleeds on a 32 bit platform than deal with sloppy programming on a 64 bit platform. Programmers tend to get lazy when resources are plentiful

 

Where did this NON-SENSE come from?  Maybe this thread should be locked, this is just an absurd statement.

Where did this NON-SENSE come from?  Maybe this thread should be locked, this is just an absurd statement.

 

Not nonsense at all. This phenomenon is really common in modern games.

 

And why would Lockheed Martin bother with optimising memory usage when they have 192GB of VAS?

OMG, give it up on the 64-bit migration!  They'll get to it eventually, or better yet a new company will take Outerra or other and bring us fully 64-bit native core & add ons, fully integrated!  It's going to happen w/ the caveat being climate change will change everything and it appears maybe sooner than later.  Enjoy what you have as it's pretty darn good already!