Slayer

If the main program thread is maxed out it can look like low GPU usage because the GPU is waiting on the CPU. Usually you will see  your core 0 at 100% and the others a lot lower. Remember your CPU usage statistic is a combination of all cores averaged out.

You can see how this works by using default P3D settings and observe your CPU GPU usage, then start cranking up all the sliders and at a point your GPU usage will actually drop off.

Anyone tried dropping their refresh to 50 Hz(european). Would of course have a system that can maintain it but 50 is easier to attain than 60....

8 hours ago, Noel said:

Yes this seems to have fixed the issue in the test flight I just did in the Dash 8 in a complex scene.  I can enable auto-fill and the stuttering issue remains resolved.  This was corroborated by LM on their forum when I posted the issue there.   He also said leaving game bar enabled could also contribute to this problem for some.

We had a similar issue for a few people during testing for the MV KA350i  with the screen flashing etc, disabling that also corrects that problem.

5 minutes ago, JRMurray said:

In prepar3d.cfg, I tried changing LocationFullScreen=x1,x2,x3,x4. I changed x3 and x4 to the resolution of my monitor and kept x1 and x2 at 0. For example, I have a 1920x1080 monitor, so I changed that line to ...

LocationFullScreen=0,0,1920,1080

It didn't work. Each time I tried, it changed back to LocationFullScreen=0,0,1912,1072. Can't figure why.

Because you loose pixels for the window border width? 4 pixels each side.

I think this is a Windows problem not a P3D problem. I've seen it in beta testing. Has to do with a update to Windows10..

Try this: Right click p3d icon, go to properties, check the box for "disable full screen optimisations"

See if it gives the same effect as unchecking that box in P3D.

Expect a bit better performance than 4k because of less pixels to push.

Ive got 2 of the EVO. Samsung is known for their speed and reliability. All of my sims run on them no probs or stutters from loading.

Didn't see which sims your using but 64GB is recomended in Xplane if you use UHD mesh. Im wishing I had bought 64GB now...it will eat 32GB easy.

I suspect this problem is similar to the contiguous memory allocation problems we had in FSX but now on the GPU side..

Also I believe there is a fix for SLI users included as well but it's not listed in the changelog

In case you missed it:

You need to be registered on the support forums 

http://milviz.com/forum/viewtopic.php?f=105&t=11967

Changelog:

Please FULLY uninstall the previous version of the aircraft before installing this one.

This version is the final version of the update. There will be no further changes unless there are any reproducible CTDs that somehow hid from the beta and development team. We intend to release it formally to all customers in the next few days but we are giving support forum users a first look at it (this helps us ensure that no issues appear with a much wider audience and it gets you all the new version for the weekend). I have done my best to summarize changes from the last release below. There are likely many more changes that I did not list.

Changes from 1.0.1 (Dec 23, 2019)
FMS Changes
-Fixed cycle dates showing yellow at all times
-Fixed broken "NEW HOLD" LSK
-Fixed reverse wind entry
-Fixed issue with entering small negative coordinates
-Fixed typos/display inaccuracies on the ARRIVAL DATA page
-Fixed broken duplicate waypoint selection on PERF TRIP page
-Fixed incorrect elevation display on ARRIVAL DATA page
-Fixed incorrect default hold data
-Fixed airport position initialization not entering departure airport
-Added RX## waypoint system for VECTOR approaches
-Fixed overly restrictive filtering behavior
-Fixed incorrect departure/arrival/approach filtering
-Fixed broken SEC FPLN ROUTE MENU link
-Fixed SEC FPLN page change behavior
-Fixed labeling of SEC FPLN DEPART/ARRIVE pages
-Fixed ability to select transitions when not displayed
-Corrected "NBDs" typo
-Fixed procedure name designations
-Corrected (as much as possible) the behavior of the "RWY" text on the legs page
-Fixed localizer data not showing all runways
-Fixed inability to use LSK-copy method to copy waypoints further down the flight plan
-Changed default HOLD speed
-Added ability to display TEARDROP and PARALLEL HOLD entry type
-Fixed erroneous "CANCEL HOLD" display
-Fixed page indexing issue with departure runway selection
-Fixed FIX INFO drawing
-Added FIX INFO intercept calculation (first pass, WIP)
-Fixed incorrect duplicate leg detection
-Fixed incorrect leg sequencing when adjusting a SID/STAR
-Made DIR TO after auto sequence inhibit revert to auto sequence
-Fixed unintentional modification/data updating of active legs from the DIRECT TO history
-Moved ini locations for better re-usability
-Moved pilot route location for better re-usability
-Added Navigraph chart viewer system
-Improved FIX INFO entry and display
-Fixed inabilty to enter VERTICAL DIR TO altitude via scratchpad
-Made editing TO leg directly perform DIR TO
-Improved display of DIR TO vertical fields
-Improved restriction of DIR TO vertical entry
-Fixed inability to reselect an approach after passing the missed approach point
-Discontinuities are no longer inserted after the departure for empty flight plans
-Made an internal change to prevent multiple DIRECT TO objects from being created
-Fixed an issue incorrect reselection of the FROM LEG when changing a STAR/APPR
-Fixed font size on DEP/ARR pages
-Fixed clicking DEP/ARR from the ARRIVAL page not returning to DEP/ARR INDEX
-Various other fixes
-Fixed leg text copying on FPLN page
-Fixed a CTD related to certain leg entry
-Switched flyover handling internally to prevent unneeded @ display
-Fixed hold exit prompt text
-Made modifying leg flyover behavior cause a flight plan modification
-Fixed name of certain HOLDs
-Fixed ability to improperly copy current position before entry
-Fixed an issue potentially incorrectly deleting legs
-Fixed incorrect leg wind entry index
-Allowed copying of leg wind data
-Made HOLD portion of missed approach remain when new approach is selected
-Fixed missing designation for certain approaches
-Fixed certain FIX behavior
-Fixed VA/CA overfly
-Going DIR to a non-flightplan waypoint during a HOLD now advances the hold behind the (DIR) object
-Made airport/runway DIR TO use proper DIR TO system
-Made insert/non-FPLN DIR TO within MAP portion of FPLN erase subsequent map legs
-Improved selection/resetting of ILS data
-Fixed re-selection of STAR/APPR from leg control after completing MAP
-Fixed detection of waypoint chains for dissimilar object types
-Fixed incorrect double-insertion of holds under certain conditions
-Fixed incorrect DIR INTC CRS entry behavior
-Fixed SP RNG number accuracy
-Fixed inability to enter VNAV DESCENT TGT SPEED
-Fixed TRANS ALT display on VNAV CLIMB page
-Fixed TRANS FL display on VNAV DESCENT page
-Fixed inability to enter C/F on TEMP COMP page
-Fixed inability to delete marked points
-Fixed inability to edit second marked point description on each page
-Fixed wrong line select copying marked point latitude/longitude
-Various leg/calculation fixes
-Added automatic setting of vertical usage based on surrounding waypoints (closing gaps)
-Added additional parameters to the runway leg for visual approaches
-Fixed hard-coded "SGF" text on FIX page
-Fixed FROM leg EFOB updating
-Fixed EFOB calculation issue
-Fixed inability to enter ISA DEV properly on LEG WIND page
-Allowed copying of leg ISA deviation

Systems Changes
-Corrected ATC ID of liveries
-VCP improvements
-Removed invalid panel.cfg entry
-Removed invalid aircraft.cfg light entries
-Removed "repair" and "modify" installer options to prevent unintentional de-activation
-Made fuel/payload stay as-is when startup scenario is set to current conditions
-Added check box to enable/disable hardware mapping
-Missing panel bitmap added

PL21 Changes
-Fixed a possible CTD relating to changing flight plans
-TAWS No longer causes erroneous alerts on load
-Fixed display of charts when CHARTS menu was re-opened
-Doubled resolution of PFD and MFD for better readability
-Allowed zoom, pan, and rotation of charts
-Added moving airplane symbol to charts display for geolocated charts
-Added procedure turn arrow display
-Updated size of flight plan arrow
-Made arrow not appear at incorrect times
-Fixed screens not clearing and redrawing fully
-Fixed drawing of runways for visual approaches
-Fixed FIX display behavior
-Fixed several crashes related to leg indexing
-Fixed RTU/FMS transponder syncing
-Fixed a PLAN related CTD
-Fixed missing RESERVE fuel display on MFD PROG

Visual Changes
-Fixed fire extinguisher indicated level
-Fixed missing texture
-Fixed reversed EMER FREQ
-Fixed the GND COMM and EMERG FREQ buttons
-Fixed reversed animation of right aileron trim movement
-Fixed cabin-side cabin door lighting
-Added wing views

In addition to the list above, significant improvements have been made to the following areas:

Leg sequencing

Leg location/prediction calculations

VNAV

LNAV

DIR TO and leg insertion behavior

Overall systems accuracy

Overall model accuracy

Overall texture accuracy

Overall night lighting accuracy

9 hours ago, mauri2007 said:

It's not about how many lines of code P3d5 shares with FS9. It´s about that the P3Dv3 graphics engine is the same as the FSX graphics engine. Exactly the same. I know what I am talking about, although I am not a "guru".

On the other hand, I really wouldn't know how to build a new (and better) graphics engine. Even though I had 1000 years to do it. But the truth is that the graphics engines are the same. I'm so glad you enjoy P3D. I have done a lot for years with P3Dv4, DCS or X-plane. But that does not stop me from complaining about the problems inherited from other times.

Wrong: Not same GFX engine, DX9, DX10,DX11 now DX12

Not everything can be threaded out to different cores nor would it always benefit to do so. It's not really a core 0 bottleneck... 

Wondering how it will affect AI ship traffic myself.

Hi, You need to go to the Milviz support forum , there is a updated WX in the top of this thread.

http://milviz.com/forum/viewforum.php?f=157

Counterfeit?

Aeroplane heaven has crash damage in P3D 4.5

X-Plane already has this with the default Cessna , you crash it it will break apart and have burning wreckage.

Don't know of any payware that has this feature.

Also I guess nobody remembers Microsoft Combat flight simulator. If memory serves it used the same  engine as FS2004?

As a tester(and customer) I can offer this (not to take any sides or make excuses)

This aircraft sim is very realistic. The depth of the systems Milviz have put into this product is incredible, it can compete with real world simulations of this particular aircraft.

These are my of observations and opinions:

1) Just about all of these aircraft in the real world come with different options that are ordered by their owners. So some military versions or some corporate fleet may have different options installed compared to others; there is no fixed standard version unless someone were to order an aircraft that is stripped of all options (unlikely) Even if you have real world experience the options presented here may not match what your organization ordered. Milviz tried to offer a "generic" version that would cover most of the commonly used options

2) Real world manuals cannot be provided due to copyright issues...real world manuals cost hundreds of dollars and would put this product out of the range of most simmers. You can't really compare it to PMDG products as the companies that produce the equipment and this aircraft (probably) don't really feel it's in their best interest to release their documentation for a simulation product. As a company, Milviz has to be very careful about fair use and  infringing copyrighted materials ( and lawyers and export laws and........) Milviz is trying to provide you with what they can legally so that you can fly and enjoy this aircraft.

3) There are some bugs,  as to be expected with any simulation of this depth. The Milviz staff is working very hard to find and fix them as soon as possible. Some "bugs" are actually how the real world systems work. I've seen it brought up many times during development " X should do X" and then a systems developer or someone with RW experience steps in and says no, "Thats how it works in the real thing". This bird does have a steep learning curve for the minutia BUT you still can get it up and flying for some enjoyable flights....IMO that is half the fun of sims, learning the intricacies and "gotchas"

For $80 bucks it's a good deal if you want a realistic simulation of this aircraft. There is nothing like it out there for this airframe ... period.

The electronic checklist is nice but I haven't seen video of anyone using it yet. Maybe overlooked but it beats flipping through a manual or alt tabbing or opening another window.

Push and hold the checklist button on the yoke for 5 or so seconds and it will pop up on the center display. Use the scroll wheel below the FMS( I use the 2D FMS for this) to scroll up and down in the selection and middle mousewheel click that selector or the button on the yoke to select/check an item  (not the joystick). If you want to hide the checklist just use the top left LSK on the center display and switch it back to FMS text  ( it has a "<" next to the button to push)

Edit: The ESC button below the FMS will take you back up one menu level.

On 12/28/2019 at 9:51 AM, TallTanBarbie said:

Hi Guys.  I just got the redux Milviz T-38 and the KA350 Super King Air and I can't get either of them to work.

I'm using the Saitek radio boxes, switch panels, throttles, and Cessna yoke/rudder pedals/trimwheel with for one and the Warthog HOTAS setup for the other and Spad Next for the interface. Not all the controls seem to work even when mapped correctly.

The KA350 has a gap in the front window seal (think that's been mentioned) and the T-38C has a landing gear lever with a knob where the alpha transparency is set too low and you can see through it.

They look great for the $140 I paid but I can't get them to start the engines -- and yes I read the manual.

Another user had the same issue of not being able to start engines and it was something with the saitek mapping , I cant recall the exact fix sorry. Are you able to start them just using the VC?

2 hours ago, mmc71 said:

V-sync on and triple buffering improves the flickering but does not stop it in my case. I've no clue what the full screen mode does, but I'll look into this. I've tested several drivers including the latest but I did not notice significant differences.

It's not a driver issue it is  something Microsoft added to windows 10. Need to right click P3D icon, pick properties , then compatability tab and click the checkbox for "disable fullscreen optmizations" flashing will be gone and you can put VSYNC back off.

Edit: you wont loose any performance or FPS...several other "games" need this turned off as well because of the same issue. Google is your friend 🙂

As with all these things it doesn't affect everyone or every vid driver version etc etc. I don't care to troubleshoot this further and it is probably for naught so I'm not wasting anymore time on it.

This "optimization" is also known to cause lag in some games...

The charts function does work but it isn't Navigraph charts. If you are willing to do a little prep work to put the charts in yourself you can have them. I'll put some instructions on  how I use it over on MV support if anyone is interested.

4 hours ago, Purr said:

Having the dc gen amber lights on for l and r gens...tried setting / resetting generators but no voltage showing. Can fully start and fly the aircraft but I can’t seem to get this indication to extinguish. Must be missing something...any ideas?

Once you start an engine be sure to turn off the respective start switch.

Good test. The only thing left that a reader has to substantiate is if 3-7 FPS gain is worth XXX dollars. In my experience, no not worth it unless you are running sub 30's on the FPS. RAM prices get crazy when you get into the higher bandwidth RAM. You didn't get extreme benchmarking handpicked RAM that often cost hundreds more than stock speeds, those are not worth the cost IMO for an additional 1 or 2 FPS than what you achieved.