7 minutes ago, simmerhead said:

FYI Simconnect isn't supported by LM anymore. It works still,  but we don't know for how long.

I don't know why you are saying this, but  for your information LM added not only corrections to functions that belong to Simconnect for the SDK 4.2 but also new functionalities, If it wasn't being supported anymore clearly they would have never done such thing.

Prepar3D SDK New Features Extract

Added Voice Control SimConnect sample

Added SimConnect camera type to create external AI cameras

Added ability to listen to SimConnect_Text messages with SimConnect_SubscribeToSystemEvent

Best Regards,
Simbol

8 minutes ago, simmerhead said:

FYI Simconnect isn't supported by LM anymore

SimConnect is supported and still a fundamental part of P3D, but it would be wise for developers to STOP using the Legacy SimConnect and move to using P3D's SimConnect.  There are still MANY content providers using the Legacy SimConnect so as to avoid having to write two code paths (one for FSX and one for P3D V4).

PMDG does not require FSUIPC.  I currently have nothing in my fairly elaborate setup that requires FSUIPC. However, for some cockpit builders it's a very important tool ... Pete was working on some issues with LM who have been very helpful working with him and I'm sure as soon as Pete returns from vacation he'll update FSUIPC for V4.2 support.

Cheers, Rob.

 

 

Sorry, I was talking about the legacy SimConnect versions... I had trouble a while back and I got message from LM that they didn't support the SimConnect version I used anymore.

7 hours ago, JoeFackel said:

Again: 4.2 won't make your hardware faster and also won't tune your ingame-settings to reasonable digits.

Maybe you are not sure what ppl mean with this, but there seems to be a problem with exactly what he is asking for, and this problem is NOT related to "powerful" hardware. Or better said, maybe it is, but in a nother way as one thinks.

When i had my "old" pc, an intel i5 7400 and my geforce 1060 ive seen many ppl in our community talk about this problem. They dont had the overall blurrie problem what most ppl mean, its opposite, all textures are pretty crisp even but suddenly all photobh sceneries doesnt load fully anymore and stay blurry. I thought "wow, im sure they all set their sim too high" or something like that and i thought they have the typical overload that causes the known blurries. Myself i didnt see this, my sceneries with photoground where super crisp. Manila (Pacsim), Fortaleza (Tropicalsim), EHAM etcetc, they all worked very very well and stayed pretty much crisp all the time, besides the usual drop outside of LOD. And i had a lot less powerful pc as they had.

Now ive upgraded all of my hardware, i have a better MB (asus prime z270k), an i7 7700k, a 1070 msi aero ITX OC and faster ram. Also an ssd with a lot more "power" as the old one.

When i bought this pc i said myself that i dont go all out on settings, despite having over double the power over the i5 7400 / gf 1060 3gb pc. So i used my exact same settings on the new machine bec i knew for fact that i never saw all the mesh/elevation and details before and i wanted to try how my settings work now on the new pc.

Guess what. Now i saw exactly what they mean with blurry photoground. Yes, the whole sim of course behaves a lot better as on old pc, yes the sim runs on higher fps now, yes the elevation and mesh etc is all better now too (remember i use same settings) BUT the phtoscenery is blurry.... Its as if it doesnt even try to load up to the highest detail level anymore.

There seems to be something else that influences this, i dont know how yet, still investigating it too and trying to solve it. Bec now i basically never get areas like Manila fully crisp anymore, on my low end pc i had no issues. Again, SAME settings. In short, the higher end pc has more troubles wth the photoground than the low end, despite the whole sim running better on same settings on the new pc.

On the first (and second) look for me it looks as on higher end hardware much more resources go into the orbx terrain, or whatever it is and photoscenery gets less priority as before. I dont know why and how, but this is how it looks. My whole terrain is like mentioned far better now on new pc (again, on same settings as i had before on the old one, wich has its reasons but i wont go into that here) but photoscenery stays blurry. I can fly over and pver an area and it wont load up to the sharpest level. While havinf the whole terrain around the photoscenery ultra crisp, mesh/elevation built fully to highest detail and have locked fps stuck at max lock of 30. Its as if the hptoscenery doesnt have any benefit at all from higher hardware and opposite, it even has bad effect on it bec suddenly the terrain outside gets higher priority, or can benefit it better which blocks somehow the calculation of the photobg.

But im not an expert, maybe it has to do with the cores and how the sheduler calculates/loads terrain. I have no idea, i can only describe what is happening on various kinds of systems.

And i guess this is what the others mean too when they talk about blurry photoground.

 

I made the jump and updated.

I did the client and Content update. 

After that I did AS update, PTA update. 

Deleted config. installed my SF textures etc.

Fired up 4.2 rebooted and did my FPS text with the NG not 1 FPS more and not 1 less. all seems well. 

So to conclude in despite my fears all went really well and was easy. 

Now FSL/MadDog............waiting! 

18 minutes ago, SaenchaySor said:

Maybe you are not sure what ppl mean with this, but there seems to be a problem with exactly what he is asking for, and this problem is NOT related to "powerful" hardware. Or better said, maybe it is, but in a nother way as one thinks.

When i had my "old" pc, an intel i5 7400 and my geforce 1060 ive seen many ppl in our community talk about this problem. They dont had the overall blurrie problem what most ppl mean, its opposite, all textures are pretty crisp even but suddenly all photobh sceneries doesnt load fully anymore and stay blurry. I thought "wow, im sure they all set their sim too high" or something like that and i thought they have the typical overload that causes the known blurries. Myself i didnt see this, my sceneries with photoground where super crisp. Manila (Pacsim), Fortaleza (Tropicalsim), EHAM etcetc, they all worked very very well and stayed pretty much crisp all the time, besides the usual drop outside of LOD. And i had a lot less powerful pc as they had.

Now ive upgraded all of my hardware, i have a better MB (asus prime z270k), an i7 7700k, a 1070 msi aero ITX OC and faster ram. Also an ssd with a lot more "power" as the old one.

When i bought this pc i said myself that i dont go all out on settings, despite having over double the power over the i5 7400 / gf 1060 3gb pc. So i used my exact same settings on the new machine bec i knew for fact that i never saw all the mesh/elevation and details before and i wanted to try how my settings work now on the new pc.

Guess what. Now i saw exactly what they mean with blurry photoground. Yes, the whole sim of course behaves a lot better as on old pc, yes the sim runs on higher fps now, yes the elevation and mesh etc is all better now too (remember i use same settings) BUT the phtoscenery is blurry.... Its as if it doesnt even try to load up to the highest detail level anymore.

There seems to be something else that influences this, i dont know how yet, still investigating it too and trying to solve it. Bec now i basically never get areas like Manila fully crisp anymore, on my low end pc i had no issues. Again, SAME settings. In short, the higher end pc has more troubles wth the photoground than the low end, despite the whole sim running better on same settings on the new pc.

On the first (and second) look for me it looks as on higher end hardware much more resources go into the orbx terrain, or whatever it is and photoscenery gets less priority as before. I dont know why and how, but this is how it looks. My whole terrain is like mentioned far better now on new pc (again, on same settings as i had before on the old one, wich has its reasons but i wont go into that here) but photoscenery stays blurry. I can fly over and pver an area and it wont load up to the sharpest level. While havinf the whole terrain around the photoscenery ultra crisp.

And i guess this is what the others mean too.

 

Thanks for posting this explanation, as it has saved me the time  Yes it has NOTHING to do with too high settings. I have had exactly the same problems. I have spent the best part of five months tweaking and testing, but nothing has worked. For those who say it is too high settings or it's the 4k monitor, nah. I am running with all setting on low, with no DL, no HDR, none of the other FPS eaters, 4MSAA. My rig is i7 [email protected] with 16Gb 3200Mhz RAM, all SSDs and a GTX1080TI. Nothing works to stop slow loading photoscenery.

13 minutes ago, SaenchaySor said:

There seems to be something else that influences this, i dont know how yet, still investigating it too and trying to solve it.

In my experience, the primary causes of this (when moving from older hardware that was not blurry) to newer hardware that is having a case of the blurries can be attributed to:

1.  BIOS/EFI issue
2.  Intel's Turbo Boost Max technology (driver and BIOS setting)

Here is a video showing the problem when I went from a 5960X to my 7900X:

The immediate solution was to disable Intel's Turbo Boost Max technology.  The long term solutions was to wait for ASUS to provide a BIOS/EFI update along with an updated Intel Turbo Boost Max Driver.  So if anyone is experiencing this strange behavior when moving "up" to better hardware, it might be worth checking for an updated BIOS/EFI and updated Intel Turbo Boost Max driver ... or simply disable Turbo Boost Max and test to see if that fixes the issue.

Now, be aware that the source of "blurries" can be many things, this is just ONE source off "blurries" I'm presenting above and how I solved it.  In my case, this was NOT an LM problem, it was a hardware problem.

Cheers, Rob.

1 hour ago, Rob Ainscough said:

SimConnect is supported and still a fundamental part of P3D, but it would be wise for developers to STOP using the Legacy SimConnect and move to using P3D's SimConnect.  There are still MANY content providers using the Legacy SimConnect so as to avoid having to write two code paths (one for FSX and one for P3D V4).

PMDG does not require FSUIPC.  I currently have nothing in my fairly elaborate setup that requires FSUIPC. However, for some cockpit builders it's a very important tool ... Pete was working on some issues with LM who have been very helpful working with him and I'm sure as soon as Pete returns from vacation he'll update FSUIPC for V4.2 support.

Cheers, Rob.

 

 

Rob       or anyone who has tested it

Do we have confirmation that FSUIPC version 5.122a or c work with P3Dv4.2?

Thanks

Joe 

3 minutes ago, joepoway said:

Do we have confirmation that FSUIPC version 5.122a

I'm still using 5.121 and that didn't cause any problems, but like I said, I don't really "use" it as much as others do, so I can only confirm that it's not causing any problems and can't confirm it's actually working as expected.

Cheers, Rob.

13 minutes ago, joepoway said:

Do we have confirmation that FSUIPC version 5.122a

It's working for me.  I only use it for my PFC throttle quadrant. 

6 minutes ago, Rob Ainscough said:

I'm still using 5.121 and that didn't cause any problems, but like I said, I don't really "use" it as much as others do, so I can only confirm that it's not causing any problems and can't confirm it's actually working as expected.

Cheers, Rob.

OK thanks Rob.

I like you don't really use it except to calibrate controllers but want to make sure it won't cause the "looping" issue before I install the new client. I only have access to v5.122 not 5.121 so I hope it doesn't cause any issue as well.

Joe

1 minute ago, Bluestar said:

It's working for me.  I only use it for my PFC throttle quadrant. 

Thanks!

On the subject of FSUIPC, i use it mainly for throttle controller settings for different types of aircraft. I could probably do without it if P3D were to implement the capability to assigning different Axis, button configurations per aircraft such as X plane has done.

10 minutes ago, Adrian123 said:

On the subject of FSUIPC, i use it mainly for throttle controller settings for different types of aircraft. I could probably do without it if P3D were to implement the capability to assigning different Axis, button configurations per aircraft such as X plane has done.

You can. All your assignments are in the standard.xml file. Just make a copy for each a/c and switch as necessary. I use FSUIPC to do it now but that was the way I did it before. FSUIPC is much easier once it's set up but a few batch files to swap the xml's out work.

Vic

 

13 minutes ago, Adrian123 said:

I could probably do without it if P3D were to implement the capability to assigning different Axis, button configurations per aircraft such as X plane has done.

This can already be done in P3D without FSUIPC, both calibration, raw input, and exporting/importing of settings.  The only thing missing that FSUIPC will do is the automatic association to an aircraft when selected.  P3D you have to manually import your saved aircraft controller configuration after loading the aircraft.

Cheers, Rob.