RodBorza

I believe that from Monday on we will receive a lot of new announcements from the third-party developers. Many veteran simmers are seeing the writing on the wall and know what will happen: many will charge for the update, alleging "backwards compability issues". Not gonna be surprised if PMDG announces "a new 737 NGXu24 for US$ 69.99 for new users and 49.99 for existing ones".

Yes, that's the idea. Arcade game. Now players will be able to start from the outside,maybe open a door or close a baggage compartment and then "enter" the airplane. Career mode maybe scripted. Missions for sure very scripted, like in the old FSX. XBox centric game. Not for the study level crowd.

Yep, I agree with you. They are not going to be free missions, but heavily scripted ones, similar we had in FSX. Go there, do that, get back. And, when you are finished, they will release a new mission DLC for only $ 19.99. The sim will become more arcade with time. The study level companies can use and will use the platform to appeal to its fan base, but serious simming is not and will never be the priority to Microsoft and company.

LOL. You are kidding, but there is a lot of truth on what you are saying. The very reason why I bought MS2020 was because I was eagerly waiting for A2A to jump aboard. Then nothing... I lost interest for the sim with time. Now A2A will take two years to adapt to the new MS2024, then two more years to adapt to the changes being made to the MS2024, then Microsoft announces MS2028, then A2A has to go after it... Then they will release the Comanche to P3Dv5.

I agree. Not good at all. Now all the add-ons will have to be bought back, because of "compatibility issues". As an add-on, should be ok, as a new game, not so much.

Yes! Panning around with Track IR now has no freezes or stutters. Worked very good for me.

Well, I tried it and it seems to be working. I have a i7-4790K and all cores are woirking at 100%. Capped as said above, and now while I still have some stutters, I don't have major stutters as before. I use TrackIR and have a lot of stalls and stutters if I move my head too quickly. Now, not so much. I'll continue further testing. At least now I don't have the dreaded "Limited by mains Thread" sign always red as before.

Hello all, I'm new to this wonderful world of the PMDG 737. I'm using the (the now) old 737-800 with FSUIPC 5. The problem I'm having is that in a short route (SBSP - SBCT) when at the cruise altitude the PFD suddenly freezes, with speed and altitude not updating on the PFD. The MCP commnads become unresponsive. But the sim continues the flight and the NAV display updates. It stays this ways for some minutes, after that, everything goes crazy: the AP disengages, the airplanes is way out of route, I find myself at an altitude way below the one before... After this "UFO Lost Time" event, the PFD updates normally and I can command the MCP. I believe the problem is related to the route I've chosen, which connects a SID at SBSP to a STAR at SBCT by the exactly same point. The SID, PORB2A, connects to the STAR, ORAN1A, at the same point, SOVSI, with no airway between the two. In real life, airlines use FL 260 in the following route: SOVSI UL310 ORANA. I can program that route in the FMC, no problem. However, when in flight, looking at the LEGS page, the point near the TOC has an altitude which is lower to the chosen cruise altitude. The sim flies normally up until 23,000 feet. But when it gets to 24,000 feet, the PFD freezes. I've tried switching the CRZ altitude to 23,000 feet, but when it gets to 22,000 feet, the problem occurs again and again. I have searched the forums for similar problems and what I found is this: -FSUIPC Auto Save feature enabled: it is disabled now, but the problem persists; - Controls: no control calibrated in FSUIPC; - Panel State: well, maybe it is the problem, I don't know. I use a saved state with ground connections on (Chokes, Air Conditioning, Ground Power); - Doors: Front and aft doors open, Cargo fwd and aft open (I don't know if it could be related); Software Updates: P3d to the last one, FSUIPC 5.153, using PMDG operations Center v2. That's it. Maybe I shouldn't be setting a Cruise Altitude since it is a flight in an almost balistice route. May be the problem is the noob me on this thing. So, I'm open to ideas. If anyone had something similar and can help, I would aprreciate it. Thanks.

To ressurect this topic, in case someone still have the same problems. For me, it is related to the GPU video drivers. If I updated it, it will cause the same problem. If I change it, then some version of it will work just fine. What I've done lately is, once updated, and the sim works ok, no mouse freeze, I keep thet driver as long as I can. Only if any other game or application askes for an update, I keep the one I'm usinge, because it is working in P3D and has no effect on any other game at all.

Well, I tried. Supersampling and surface optimization off, but no joy. I've tried other tweaks as well, as vsync on and off. No joy too. Although sometimes I could run at seatdy 30 fps, with no stutters using Track IR on ORBX Los Angeles scenery ( a real challenge to the PC), I could not get rid of the shimmering. It was everywhere. So, I went back to may "old" Nvidia 670X. Although with only 1Gb of VRAM, FSX runs smoothly, perfect AA, no shimmerring whatsoever. Maybe it has to do with ATI drivers, or maybe my Power Source was not enough for the R9 270X. Could not figure it out... Edit: It seems to be a problem with the R9 series of video cards, including 270X Lots of people with shimmering problems. It requires a BIOS update...waiting on the manufacturer. Not related to the tweaks recommended in this thread.

Thanks dazz. I'll give it a try.

Hello all, Hello cvearl, Glad to see this topic still active. I have this problem of shimmering and white lines on FSX, P3D and terrible, terrible shimmering on X-plane. All that using an AMD XFX R9 270X 2048 MB. I initially thought that this new GPU would be the solution, but it only made things worse. Although frame rates rose, image quality dropped. I tried a lot of things. Spent more time tweaking than actually flying: Bojote's tweaking tool, fsx.cfg and Prepar3d.cfg properly tweaked, Radeon Pro set, CCC set with Multisample, Anisotropic set in FSX and set to 16x in Prepar3d, no Surface optimization, etc. All of this didn't work. One thing I noticed tough, that these settings only work for DirectX 9.0. I have FSX working with DX9 and it looks and works great. However, if I use the same settings in Prepa3d, I got a lot of shimmering. The same happens In X-plane (64-bit), with greater intensity. Reading through the pages of this thread, I could noticed that many of the tweaks shown here are for use with DX9. I would like to know if someone has found a solution to use with DX10 and DX 11, in case I missed in the middle of so many posts. I also researched on the internet, and in many forums people say that shimmering is something that is a problem inherent to AMD cards. So, I changed back to an NVIDIA 670X 1048 MB and voilá... no more shimmering, Although I don't get really fast frame rates and stutter free experience, in all my sims, the image is crisp clear, running with Dx9 in FSX, DX11 in P3d and totally shimmer free in X-Plane. Does anyone has a solution/explanation for this? My system specs are as follows: Intel i7-2600K @ 3,4 GHz - Hyperthreading on - FSX and P3D working with Affinity Mask = 252 16 GB RAM AMD XFX R9 270X 2048 MB Windows Home 64-bit Add-ons: Lots of Carenado Aircraft ORBX Global with Vector

Hey rgbalzaretti, Try this forum: http://forum.avsim.net/topic/441819-possibility-to-improve-fps/ It does help, although not a perfect solution.

And to answer my own question: Looking around the P3D forums, I found out that many people were asking how to make a AI aircraft become a flyable one on P3D. Thing is that what one got to do is to copy the panel folder from FSx into P3D. I tried doing the same with the F-35B and it worked. However, I had no sound. Then I looked on Dino's F-35A folder: all the sound files, the panels and STVOL configuration of the F-35B were there. My mistake was that I was porting only the F-35B and F-35C into P3D, and not porting the F-35A since it is already present as a default aircraft on P3D. Big mistake. The problem is that the .cfg files on the B and C models folders look into the A model folder for their panel and sound files. Then I ported the FSX F-35A folder into P3D, and now the B model works, with STVOL capability and everything. In order not mess up with Prepar3D, the default is originally named F35A. So, I pasted it with the name F-35A. Now on the vehicle list I have the default F35A, and all the Dino's models for the A, b and C models. And all working fine. The difference is that the default A model will have its publisher listed as AlphaFoxtEcho and all others as Dino cattaneo's. Very simple, very clever. I 'll let this post here as reference for anyone trying to do the same. Lots of fun with Dino Cattaneo's aircraft!

Hello all, I have Dino Cattaneo's F-35B and C models on FSX working perfectly. i tried to port them to Prepar3D v2.4 by copying their folders into P3d SimObjects/Airplanes folders, and by copying the respctive airplanes files on the FSX Effects folder to P3D Effects folder, but still it is not working. The issue is that P3D does not show the B and C models on the vehicle list. Does anyone have an idea of what may be happening? I think that P3D is seeing the B and C models as AI aircraft. If that's so, how can I change it? Thanks!