would expect developers to find other ways to reach the function of their addons at the time of development, as otherwise then we may have numerous services to perform simple checks etc running in background with system boot increasing windows startup time, security concerns as well as chances of unforeseen conflicts with unrelated software.

 

I, for one, would love to hear of an alternative solution that is:

 

1) Non-intrusive (i.e. doesn't replace the default DirectX DLLs in the Prepar3D folder, causing umpteen compatibility issues)

2) Can run immediately when the Prepar3D process is started so it can initialize the proper handlers which need to run before the Prepar3D DLLs had a chance to load, at which time "it's too late"

3) Will sit dormant taking virtually zero CPU time.

 

With Windows 7 and later, the check for "process started / process ended" is virtually nil in terms of performance footprint.

 

If you really wish to have a constructive, technical discussion on this matter, feel free to stop by our forums, identify yourself and start it.

As mentioned before this is to be decided at the time of development and up to the developers how pragmatic they want to be in including/designing new features against making changes to the system or stock sim content. Some users may prefer it and some may not, so only useful thing to add here is the specific features and the service should be made optional if possible and user be notified at the time of install, with perhaps another option to not install service into the system and ask user if comfortable to start the application manually (a version to close on sim exit) from its folder before sim launch.

I, for one, would love to hear of an alternative solution that is:

 

1) Non-intrusive (i.e. doesn't replace the default DirectX DLLs in the Prepar3D folder, causing umpteen compatibility issues)

2) Can run immediately when the Prepar3D process is started so it can initialize the proper handlers which need to run before the Prepar3D DLLs had a chance to load, at which time "it's too late"

3) Will sit dormant taking virtually zero CPU time.

 

With Windows 7 and later, the check for "process started / process ended" is virtually nil in terms of performance footprint.

 

If you really wish to have a constructive, technical discussion on this matter, feel free to stop by our forums, identify yourself and start it.

 

Lefteris, is it possible that these initialized handlers may interfere with the correct functioning of the other developer's aircraft in any negative way?

Thanks.

No, they shouldn't be.

No, they shouldn't be.

 

Lefteris,

 

I am a FSX, now SE, long time user.

 

I don't want to spend my money in the professional license of P3D, and then in your superb A320, to fund out that all I gain is shadows, which I actually even disable with the DX10 fixer, as well as I usually set autogen density to NILL when using FSX or P3D ( monthly license ) with AEROWINX PSX for the visuals only. Of course

 

I've been in the fence for a long time between waiting for FSLabs A320 or going Airlinetools A32X, and it's getting really near to a final decision, but I would really use your help in portraying the true advantages of using p3D instead of FSX for my simulation engine, to run just your A320 and a few A2As I have.

 

I actually even have the PMDG 777 for both versions ( a very stupid move I did a couple of years ago... ), but honestly, unless better performance and stability isn't what I am getting from P3D, then I would rather profit from my good-old FSX:SE instead, specially given the low level of graphics quality I set when using either sim.

 

Are there any additional advantages, from a development and maintenance cycle pov in using P3D instead ?

 

Thanks for any answer.

Are there any additional advantages, from a development and maintenance cycle pov in using P3D instead ?

 

My 2c on this matter: P3D should me more stable, have better VAS management, look better and actually perform better. Note the word "should". It is also in a very little need of tweaking, mostly just setting sliders appropriately.

For me, at least, I have an occasional DXGI error with A320, but that's about it. My P3D neither crashes nor has problems, the problems start when you start piling stuff, trying out drivers, blah blah blah... install a clean machine, put working drivers, and enjoy. For me it also performs way better than FSX ever did, and with that it looks better.

 

Now, since you said:

You disable shadows.

Turn off autogen (really??).

and I question how stable your FSX is...

 

Then P3D will not bring you much of the benefit, per se.

 

Lately there are some serious issues with P3D general, see problems with VAS and GPU crashes (DXGI errors).

 

That said, LM are coming out with P3D v4, which will be 64bit... so there's that.

 

With P3D, you get a platform that is being developed, instead of stagnation.

@SimonC

 

yes, for me that's when it will actually be worth the change - 64 bit.

 

Thx for sharig your thoughts.

David,

 

How can I check which CPU I am using? and if it's 4 core? Also, how would you put TrackIR on specific cores?

 

I'm not as tech savvy as I should be for this hobby, but i'll learn quickly!

 

Thanks!

 

You would add the following to Prepar3D (FSX).cfg

 

[JOBSCHEDULER]

AffintyMask=85 // 116 or 245

 

Here is an answer from Steve W the AM guru:

 

http://www.avsim.com/topic/504275-unbelievably-smooth-performance-question-re-cloudterrain-shadow-impact/page-2#entry3574307

 

01,01,01,01 = 85 dec - sim - best rendering

10,10,00,00 = 2 LPs for apps

 

or

 

11,11,01,01 = 245 dec - sim - best loading

10,10,00,00 = 2 LPs for apps 

 

The best thing that I did was to download and install a program called Process Lasso, start the sim or app and navigate to the process running in Lasso and assign the AM by selecting:

 

CPU Affinity\Always\Select CPU Affinity and select the cores that you want to assign remembering that you must read the binary code above from right to left.  In the case of AM=85 cores 0,2,4,6 are being used for the sim and you would set your apps to use cores 5 and 7 which is only done with Process Lasso.  It's pretty easy once you get the hang of it, remember to put the [JOBSCHEDULER] section in your .cfg and set Process Lasso as well.

 

Robert

No, they shouldn't be.

 

Does this update make the A320 compatible with the latest version of P3D that was just released?

I am a FSX, now SE, long time user.

 

I'm a fsx box user, my experience with the bus:

-no oom issue with latest version. Autogen normal, scenery complex normal. As next wx. Did few flts between orbx kpsp and ksts spanning orbx socal and nocal, about 0.6gig vas remaining. Same for uk2k egph and egll using orbx Scotland and England.

-fps wise 20-25 at those complex airports. Not bad.

-dx10 fixer w cloud shadows, no problem.

-all in all a very satisfying bus

 

Since you can get the p3d version by paying the price difference between fsx and p3d, you can try it first on fsx then go to p3d later if needed. No need to decide fsx or p3d now if fsx is still being used.

 

Also, remember reading no autogen is worse than minimum autogen from standpoint of smoothness as the renderer was said to run better with some of it.

Does this update make the A320 compatible with the latest version of P3D that was just released?

 

It is compatible with Prepar3D v3.4 (3.4.22.19868)  

It is compatible with Prepar3D v3.4 (3.4.22.19868)  

Perfect.  Thank you.