Michael - go back and read his post again, e.g. "without using any fingers."

Haha - thanks, I see.

And by using DX12 force all customers to upgrade their simulator to W10.......

 

I highly doubt Lockheed will do a forced OS change without some major notification as well as ample documentation ahead of time.

........and an extended period of testing using the early adopters within the flight sim community to help iron out any issues which may have escaped detection during the formal beta phase. So, you never know, it might happen sooner than we think, but whether we see those initial forays in Version 3.xx remains to be seen.

 

Mike

 

Still, a lot of people may be happy if LM manages to solve the OOM issue in P3D3. Unfortunately, this doesn't include me, as I never had an OOM since version 2.2. It's just a matter of type of usage.

 

So you are currently running P3D at the maximum possible level of detail, with lots of detailed payware addons running at the same time? Of course you aren't....and that's where significant VAS optimisations are going to benefit the P3D community. Those that aren't experiencing OOMs at any time are obviously scaling back the detail levels and minimising the use of multiple addons simultaneously, so this would give them the opportunity to push a bit further. Those of us who always want to use a certain combination of addons at relatively high detail levels (and who currently suffer OOMs now and again) will (hopefully) be able to do this without getting dumped to the desktop!

 

Significant VAS optimisations are (IMO) rather more welcome than DX12 at this stage of the game.

So you currently run P3D at the maximum possible level of detail, with lots of detailed payware addons running at the same time? Of course you aren't....and that's whereHere

Here are a few facts on my setup/usage:

 

- Screen resolution 3440 x 1440, only one monitor

- EVGA GTX 760, 4 GB VRAM

- I exclusively fly GA (Alabeo C172 / A2A C182)

- Only 1024 textures

- I only make short flights (max. 1 hr)

- No panel on display (neither 2D nor 3D), only scenery, as I have a hardware (XTOP) panel including 9 Saitek FIPs, Radios etc.

- No TrackIR

- I only activate scenery batches I am actually using (via SimStarter), grouped according to ORBX as Global, NA, EU, OC (including the corresponding add-ons in the region)

- I use UT2 for AI traffic which essentially runs outside the simulator using its own .exe

- I rarely use real weather, and if so, inject it via a networked laptop

 

On the other hand:

- All scenery sliders fully right including both Autogens except Mesh (5 m according to ORBX) and bathymetry off

- Some shadows on, medium shadow quality

- I use some scenery known as heavy, including Toronto + Sydney

 

This may not be the typical setup/usage, but no single OOM so far in 2.4 or 2.5, believe me or not. Actually, I am quite happy with what I have right now, and this is based on more mediocre system, which some of you even might laugh about.

 

Kind regards, Michael

MIchael

 

How did you get UT2 to work in P3D?

 

Jack

So you are currently running P3D at the maximum possible level of detail, with lots of detailed payware addons running at the same time? Of course you aren't....and that's where significant VAS optimisations are going to benefit the P3D community. Those that aren't experiencing OOMs at any time are obviously scaling back the detail levels and minimising the use of multiple addons simultaneously, so this would give them the opportunity to push a bit further. Those of us who always want to use a certain combination of addons at relatively high detail levels (and who currently suffer OOMs now and again) will (hopefully) be able to do this without getting dumped to the desktop!

 

Significant VAS optimisations are (IMO) rather more welcome than DX12 at this stage of the game.

 

I am betting that if something is doing to reduce VAS usage, it won't be very long before some users add enough add ons to cause their  OOM's to reoccur.  

MIchael

 

How did you get UT2 to work in P3D?

 

Jack

As far as I recall I was using the evil Estonian Migration tool. It was a bit tricky when I first installed it (under 2.2? - long ago) and I forgot details. I think I had to make a dummy directory and files which UT2 insisted to have under

 

C:\Users\(your profile)\AppData\Roaming\Microsoft\FSX

 

(I took all files from a former FSX installation.) Besides I had to add

 

[Entry.9]

Path=SimObjects\UT2 Aircraft

 

into P3D Prepar3D.cfg (goes now into SimObjects.cfg).

 

When I re-installed P3D2.5 I saved /UT2 Aircraft under /Simobjetcs and the /Flight One Software directory. After installing 2.5 I moved them back and added the Simconfig.cfg entry and this was it.

 

Kind regards, Michael

I use UT2 in P3D v2.4, and it works fine. I don't recall having to do anything significant to get it working, other than using the Estonia Migration Tool. It's worth noting that I run UT2 airliners @ 100% (since I didn't spend huge amounts of time and effort updating and adding lots of new schedules and aircraft models to only see a fraction of them in the simulator), which is one reason why any improvements to VAS in P3D v3 would be very welcome!

And by using DX12 force all customers to upgrade their simulator to W10 and rewrite their probably custom written drivers for their complete cockpits, including a very very painful bugfixing phase and maybe a new certification if they have one?

 

Remember the jump from FSX to P3D 2.0? I don't either...It's the new normal.

Isnt 64 bit a priority over DX12? Seriously. We need the extra ram space instead of constant turning things off and scaling things back.  DX12 will come but in order to exploit all its features its going to need alot of help when the core of the sim is based on 2005. Not to mention, DX12 is just too new with nothing proven other than demos. DX11 will be sufficient for the time being

If it isnt 64 bit, then perhaps by some miracle they segmented various parts to use external memory rather than be contained all within the 4gb VAS box. Is that even possible? As in example of the core weather engine using memory outside the core, and the AI engine external as well. Sounds complicated, but perhaps its easier then redoing all that legacy code to 64bit.

the core of the sim is based on 2005

So Dave... you've seen the source code?

No-one will be forced to do anything. If you want DX12 you use Win 10. If you don't, you don't. Simple enough. I'm sure P3D will continue to operate on obsolescent equipment as that is actually how half the simulation world works.

No-one will be forced to do anything. If you want DX12 you use Win 10. If you don't, you don't. Simple enough. I'm sure P3D will continue to operate on obsolescent equipment as that is actually how half the simulation world works.

+1

So Dave... you've seen the source code?

Of course not. Isnt it common knowledge that its very foundations are on FSX? How much is rooted out is anyones guess but I still see BGL files and unless something drastic changes, these will be around for a bit still.

But what do I know. Im not a programmer.

Remember the jump from FSX to P3D 2.0? I don't either...It's the new normal.

 

But private persons are not the benchmark. Your benchmark are customers that sell F18 cockpits or other trainers to companies probably even the military. Saitek hasnt even managed to bring out a working W10 driver for the X55 even 1 month after the launch of W10, now imagine what joy those companies would have. Especially since nothing has been anounced whatsoever.

 

Companies usually upgrade under two circumstances their operating system. 1. it brings some gigantic new productivity or other killer application (that doesnt happen) or 2. Microsoft announced EOS for that operating system. Usually for any company with any sort of security compliance that means upgrading to a new OS.  That is why large companies shut down the last XP on the 8. April 2014 then switched to Win7 and will keep that until 14. January 2020 the absolut latest. So you won't see any commercial company force W10 on any customer anytime soon. That is just a simple fact.