OnCourse Software

Hi all.
After a long time break in P3D flying (more than half year), finally I have possibility to come back to my hobby. I updated win 10 and PF3 and immediately I have discovered the problem.
When I want to change flight plan path application crashes.
More details on recorded movie and windows event log.
https://youtu.be/jvy19F62ZLI

That an incompatibility with a PF3 skin. Try changing the skin. Personally I use the one named 'Zune' these days and haven't had any issues. Quickest way for me to explain how to change to this skin is pen the PF3.INI file in Notepad and search for the [System] section then change the UseSkins and Skin2 parameters to match the following:-

UseSkins=2
Skin2=Zune.cjstyles

Changing the skin to your fixed the issue.
Now I have discovered another one but do not know if I should create new thread or just post here.
Problem is with PF3_Displayer
I have two red dots on the bottom of pf3 displayer (seems to not have communication with PF3 ?), no info about next last wpt, Freqs, and comunications 1-0 are empty too. Still investigating what may cause problem.
What I did:
- edited pf3_display.ini: manualy adjusted local IP of the computer (FS and PF3 on the same PC)
- checked PF3Port=1010 -> if PF3 and FS on same machine does the traffic from PF3 to displayer goes through the router?
- Antyvirus full off
- Firewall full off

Still thinking ...

Let me know If I should create new thread

In the PF3.INI file you also need to change the following

[PF3Display]
PF3DispActive=1
SocketPort3=1010

Alternatively you can set this in Options #2, Advanced Options and INI File Tweaks, under the PF3 Display section (top left)

dmarch wrote: *

Sat Feb 20, 2021 1:25 pm

In the PF3.INI file you also need to change the following

[PF3Display]
PF3DispActive=1
SocketPort3=1010

Alternatively you can set this in Options #2, Advanced Options and INI File Tweaks, under the PF3 Display section (top left)

Everything working. Thank you for your support and your time. We can close the topic .
Thank you

Excellent, thanks for reporting back