Sign in to follow this  
windshearDK

Very strange issue with P3D V3

Recommended Posts

Dear all

 

I have now been flying a few flights, and I can see now that somehow the PMDG is working at slower speed than the rest of the sim.

 

the clock works, but the timer itself I have timed it myself, reads 1.35 for every 1 second real time. Also the flap deployment time and engine startup takes a lot longer than I ever saw either in P3D v2 or FSX...!

 

I have no clue what is causing this what so ever!


Here is an example.

 

I just arrived at CPH from DXB a flight that takes around 6.5 hours. My gate departure was around 5 am GMT, as you can see the timed flight time was 4:22 when in fact it should say something around 6 hours.

 

ek151.jpg

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Never expierenced that. Did you do a clean install and load the aircraft after a default one was loaded?

Share this post


Link to post
Share on other sites

Is you system heavily overclocked? I have heard of system heavily overclocked acting weird with passage of time. If you are overclocked lead the default clock in your bios and see if the problem still persists.

Share this post


Link to post
Share on other sites

Dear all

 

I have now been flying a few flights, and I can see now that somehow the PMDG is working at slower speed than the rest of the sim.

 

the clock works, but the timer itself I have timed it myself, reads 1.35 for every 1 second real time. Also the flap deployment time and engine startup takes a lot longer than I ever saw either in P3D v2 or FSX...!

 

I have no clue what is causing this what so ever!

Here is an example.

 

I just arrived at CPH from DXB a flight that takes around 6.5 hours. My gate departure was around 5 am GMT, as you can see the timed flight time was 4:22 when in fact it should say something around 6 hours.

 

ek151.jpg

 

 

I am a P3D V3 user and I have not experienced this issue with the -200LR/F/-300ER.

 

Just to be sure, I launched the sim, and ran a few time tests. First, using the chronometer function 1 minute on my iPhone 6 timer, was 1 minute on the -300ER chronometer.

 

Second, I tested the elapsed time function. 1 minute on my iPhone 6 timer, is 1 minute on my -300ER elapsed time function. 

 

Not even a second of difference between real world and PMDG timer functions.

I also tested flap extension from Flaps UP to Flaps 30, full extension took ~57 seconds. Same extension time as in my FSX SP2 install. 

 

Regarding overclock causing potential time issues? I have been running a overclocked i7 4790k at a always stable 4.7Ghz since I put the new system together a year back. No issues, and I doubt there is a relationship between the two.

Share this post


Link to post
Share on other sites

I think you should check your install and maybe even do a clean one just to make sure. The off timing is strange, especially if you are not using time compression.

Share this post


Link to post
Share on other sites

have you checked the P3D v3 settings under Options > Simulation Rate?

There is a Half speed and Slowest setting?

 

Share this post


Link to post
Share on other sites

Are you using an Asus motherboard?

 

Certain boards from them were affected by a faulty realtime clock / CMOS which can cause weird issues like this.

Share this post


Link to post
Share on other sites

Thanks guys!

 

Well before installing V3 I had P3D 2.5 I did not have these issues at all!

 

My sim speed is checked to be on normal.

 

I installed V3 on a new HDD and thus it's a clean install.

 

I am writing you because it's an issue I have never ever come across, yet I am suffering from it.

 

Please help

Share this post


Link to post
Share on other sites

Would stutters or fluctuations in FPS potentially explain, the simulator clock is independent of the 'windows' or software clock and any pause in the simulator would 'freeze' time so to speak. This would not be compensated for because the simulator isn't aware of a change in the difference between your system clock and it's own simulated artificial clock.

 

If a pause or stutter occurred say many times a minute unnoticed then that is a lot of time lost. I have seen this problem before although never to that scale where I have noticed time seems to disappear. As an example I have a clock auto synced with an atomic clock in my house and before a flight I will sync them together, they certainly are not the same a few hours later.

 

I would consider checking whether your system is stable and also try changing settings and locking FPS internally to 30 so that there aren't any stutters or losses. If it is running at a solid 30fps constantly and time still drifts then it is very difficult to explain why it is happening beyond some very complex problem beyond P3D. Flaps and custom engine code use some kind of internal timing to make them realistic so it is very obvious they could be affected by problems with keeping time. in the aircraft.cfg, the flaps for example will have a defined extension time which then rely on the timing mechanism. If this mechanism was compromised either by a system that cannot keep time properly or one which is unstable then I'm sure you would see something go wrong.

 

I would first try the processor at stock speed and also check the Windows event logs for any WHEA errors. A CPU cycle after all occurs every second and an unstable CPU might be compromised in properly defining what a second is.

Share this post


Link to post
Share on other sites

I keep my fps locked at 30.

 

But if it's stutters, then I would have seen the same in V2.5 no?

 

What are WHEA errors?

Share this post


Link to post
Share on other sites

One thing to check for would be your antivirus exclusions. Remember that this is in a new directory (unless you changed it from the default). If you're still letting your AV scan it, this could cause some hangs, exacerbated by the fact that our aircraft (and likely the scenery used) are a heavy toll on the system. Unless you put the new directory in your AV exclusions, that could certainly be the case.

 

I keep my fps locked at 30.

But if it's stutters, then I would have seen the same in V2.5 no?

What are WHEA errors?

 

Not necessarily. I think it's about time that people begin to realize that v3 is not v2.5. There were rather significant changes to the code here. Remember all the people who ran FS9 just fine, but FSX brought their system to its knees?

 

Windows Hardware Error Architecture.

Share this post


Link to post
Share on other sites

I have seen very poor performance, but I will try to decrease the clocking of my CPU, it's still quite low, but I will reduce it even further

Share this post


Link to post
Share on other sites

I forgot to add that I get a terrain warning on final. Doesn't matter which airport I am using

 

Likely unrelated, but out of curiosity, do you have a destination airport set on the RTE page?

Share this post


Link to post
Share on other sites

Yes of course. I use PFPX and then load the flight I created into the FMC

 

Go to the FSX/PMDG/Navdata folder and delete ARPT_RWY.dat file. It will rebuild on the next sim load. That may fix the issue.

Share this post


Link to post
Share on other sites

I've been having this same problem with V3 and both the 777 and NGX.  After submitting a ticket, the response I got was that there seems to be an issue between PMDG aircraft and the migration tool that alot of us use.  If you've used that tool before, that's probably causing the issue, according to Ryan and Paul from PMDG.  

 

-Chris Jepsen

Share this post


Link to post
Share on other sites

I keep my fps locked at 30.

 

But if it's stutters, then I would have seen the same in V2.5 no?

 

What are WHEA errors?

 

Potentially but v3 has changed a lot from v2.5. A lot of addons are still basically ported directly over from v2.5 or even FSX so there is a lot of room for something to go wrong.

 

I just tested the chronograph myself with the 777 and v3 and the timing seemed more or less perfect. This problem seems to be a very specific one which I think requires the knowledge of the support guys.

Share this post


Link to post
Share on other sites

I am not using a migration tool I installed using PMDG installers which were compatible with V3.

 

Thanks Scandi!

Potentially but v3 has changed a lot from v2.5. A lot of addons are still basically ported directly over from v2.5 or even FSX so there is a lot of room for something to go wrong.

 

I just tested the chronograph myself with the 777 and v3 and the timing seemed more or less perfect. This problem seems to be a very specific one which I think requires the knowledge of the support guys.

Should I apply for a ticket then?

Share this post


Link to post
Share on other sites

I am not using a migration tool I installed using PMDG installers which were compatible with V3.

 

Should I apply for a ticket then?

 

To be clear - you don't even have to use the tool on our products. Even if it's simply installed on your system (to migrate scenery, as an example), it can cause issues.

 

Yes, you might as well submit a ticket. Any time you want active participation from the team, you should submit a ticket.

Share this post


Link to post
Share on other sites

I didn't use the migration tool to install the PMDG aircraft either.  But, I did have the migration tool installed on my computer to move some of my FSX sceneries over to P3D.  Paul said that the tool messes with the Windows registry and can cause problems with their aircraft.

Share this post


Link to post
Share on other sites

Ok I understand better now. I didn't use a migration tool for my other addons but I did install P3D V2.5 sceneries directly into V2.

Could this cause issues? If so would it help if I reinstalled the T7?

Share this post


Link to post
Share on other sites

Ok I understand better now. I didn't use a migration tool for my other addons but I did install P3D V2.5 sceneries directly into V2.

 

Could this cause issues? If so would it help if I reinstalled the T7?

 

Yes. As I mentioned earlier, it can cause issues simply by being installed. No, reinstalling the 777 will not help the issue.

 

See here (yes, I know this refers to the NGX, but the process is the same for any of our products):

http://support.precisionmanuals.com/kb/a115/737ngx-loads-minimized-in-p3d-v3_0.aspx

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this