News:

Precision Simulator update 10.175 (29 May 2024) is now available.
Navburo update 13 (23 November 2022) is now available.
NG FMC and More is released.

Main Menu

VisualPSX Suite build 5427 uploaded

Started by Garry Richards, Mon, 10 Nov 2014 05:13

Markus Vitzethum

Hi Garry,

good to hear that your are keeping the traffic display. ;-)

It was really helpful today on a VATSIM flight from Miamia to New York JFK. It was on this flight when I observed what seems to be a pattern.

One multiple occasions I noticed that nearby enroute traffic at other levels (e.g. crossing left to right or flying opposite direction) was shown in FSX (*) (see note below) but not on the TCAS and not in the traffic list.

I think the pattern I observed is as follows: since not all the time there was nearby traffic, it happened that I was alone in the skies. Nevertheless, the last aircraft that was nearby before flying out of range was kept as #1 in the traffic list of TrafficPSX. After flying out of range, it was no longer visible in FSX (and kept with constant data in TrafficPSX). Under these conditions, TrafficPSX did not update its traffic list again when new aircraft are coming within range. It still shows the outdate #1 entry but not the new nearby aircraft.
Exiting and restarting TrafficPSX immediately solves the problem; it shows the correct nearby aircraft - until all of them are out of range and the pattern starts again.

It might be due to internal works of how FSX handles its traffic list of aircraft. I once looked at that (FSUIPC) data some years ago and found it difficult... may AI aircraft are not properly terminated under VATSIM conditions.... (but the are definitely gone in FSX).

Maybe this is supported by another observation: when I disconnect my Vatsim client (vPilot), the Vatsim traffic is gone in FSX but still present in TrafficPSX and PSX. There seems to be difference in how FSX and TrafficPSX handle the AI traffic data.

Disclaimer: I have practially no FSX AI traffic. I am looking at Vatsim traffic only.


Last but not least one brief comment on the VisualPSX debug 2: is it just me or does it take longer with debug2 to get FSX initialized. I noticed that the re-positioning of FSX - the time when the FSX "loading" progress (e.g. "loading terrain data, 32%") is shown takes so much longer, or more, precise, is repeat maybe 4x times.
I noticed, first because it seems longer, but also since the low-power computer running forward right view (running an older VisualPSX version) is finished so much fast aligning FSX than the powerful computer running for center view (running Visual PSX debug2).

Hope this help,
  Markus


(*) note: with right click in FSX I can switch view to the other aircraft; there is a full list of all aircraft)

Garry Richards

Thanks Markus. Very useful information! I will investigate.

Cheers,
Garry

Website: flightsim.garryric.com

Garry Richards

#42
Markus,

Here is the debug 3 version of TrafficPSX. I think I have fixed the stuck traffic problem. Again your detailed notes pointed me to the likely cause.

Re VisualPSX there should be no difference in startup times between recent versions. Try swapping them to see if the difference changes.

Cheers,
Garry

Website: flightsim.garryric.com

Markus Vitzethum

Hi Garry,

excellent, thanks. I'll try as soon as possible - which means a new test flight and hope that my wife does not complain.  :)

Markus

CHEDHKG

Hi Garry,

I do also confirm that now I can see the traffic on PSX (from IVAO).

However between Debug2 and Debug3, the XPDR as well as the COMMS are not synched anymore between PSX and FSX. But still testing this very nice piece of software !

jlpilot

Quote from: Garry RichardsIf you use the instructor to position PSX at a gate or holding point the FSX position provided by VisualPSX will probably not match because FSX scenery positions are not very accurate.
To overcome this you should taxi PSX to the gate or holding point using the FSX scenery as your reference. Then save the situation for future use. Whenever you load that situation the FSX visuals will show that you are at the correct location.

Got it  ;)

Quote from: Garry RichardsThis may not matter to you for a visual takeoff using the FSX runway as your reference but if it does then simply set the departure runway before you start to taxi to the runway.
...look at the status page of VisualPSX for guidance. Turn the beacon off then use the PSX instructor to position PSX at the runway take-off position. The FSX aircraft won't move, but, if you can see the PSX instruments or windscreen, you will see that it moves to the runway and then moves back. VisualPSX will show that it has set the offset for that runway. Now you can turn the beacon back on and start taxying. When you turn onto the runway FSX and PSX will be aligned.

A clever solution, even if I do say so myself.  ;)

Cheers,
Gary, thanks for that. This works quite well! Problem solved. Thanks again!
Regards,

Jermaine.

Britjet

Hi Garry

I have been going round and round an extended hold at DXB with 100% traffic based on MyTraffic 3d, monitored with Aivlasoft EFB to see what is actually there..All of the traffic shows OK on FSX visual display.

I would say that TPSX is picking up about 30% of the traffic - it is difficult to find a logic to it - sometimes it is missing aircraft that are very close, and sometimes picking out higher level traffic with intermediate level traffic being missed. (I completely understand the above/below switch btw).

It sometimes seems to cling onto one aircraft and not look for any others?

Hope this helps..

Good luck with the gardening... It is raining here so can't do mine :-)

Brit

Hardy Heinlin

Hi Brit,

PSX does not show more than 7 aircraft.


|-|ardy

Britjet

Hi Hardy

Thanks, yes, I gathered that - but it often shows only 2 or 3 when there are more nearby..
A bit frustrating!

I was wondering if it had something to do with the number of AI aircraft - eg if there are too many in FSX does it stop analysing?

Brit

Markus Vitzethum

Hi Garry,

Quote from: Garry RichardsHere is the debug 3 version of TrafficPSX. I think I have fixed the stuck traffic problem.

as far as I can tell: it works.  :D

(I did yet another flight across the continental U.S. yesterday evening. Traffic was lite but enough to prove that the pattern I described is gone. Most of the time I had no nearby aircraft but whenever a Vatsim TCAS target came within 40 miles, it was correctly shown on the ND.
Actually, TrafficPSX saved the day for some 200 virtual Vatsim passengers when another aircraft which was not talking on Vatsim UNICOM (and missing my calls) set up for a landing approach on a very closely spaced runway 35L at KDFW. I never saw him visually but on the ND. Separation was less than 5nm/0ft and I had to switch to another runway (35C -> 36R) to avoid, luckily there are plenty of them at KDFW.  :) )

Regarding comms and XPDR not working ... it did work well on my combination. (FSX, TrafficPSX debug3, PSX_beta10, vPilot)

Re VisualPSX: everything did work well on that last flight. What happened on the last flight might be an effect of connecting the other PSX clients. I'll investigate further and let you know when I have something reproduceable.

Markus

Garry Richards

Hi Britjet,

I have found that the traffic selection procedure has bugs and will release a fix soon. Thanks for testing and reporting.

Cheers,
Garry

Website: flightsim.garryric.com

Garry Richards

Quote from: chedHKGHi Garry,

I do also confirm that now I can see the traffic on PSX (from IVAO).

However between Debug2 and Debug3, the XPDR as well as the COMMS are not synched anymore between PSX and FSX. But still testing this very nice piece of software !
Hi chedHKG,
I cannot replicate this behaviour. PSX does require two presses on every second time you swap frequencies, perhaps that was the cause?

Cheers,
Garry

Website: flightsim.garryric.com

Markus Vitzethum

Hi Garry,

just a quick and funny question regarding VisualPSX: is VisualPSX doing any settings with FSX regarding fuel or fuel tank status?

I am asking because I'm running xACARS (for FSX) as a flight logger and reporting tool. It connects to FSX and I am back to the state where I can use xACARS in my PSX setup. To have a more or less correct fuel number reported in the xACARS I am setting the departure PSX fuel also in the FSX default 744. However, I discovered that every, say, 10 minutes I find the center fuel tank in FSX re-filled to 100% (> 50 tons) and I have no idea why. There are only three programs talking to FSX: VisualPSX, TrafficPSX and xACARS (via FSUIPC+WideClient).

Thanks,
  Markus

p.s.
Did yet another 3.5h flight yesterday evening with the debug2 and debug3 version, everything is running smoothly.

Hardy Heinlin

#53
The frequency swap switch function delay in PSX is a Boeing feature. It prevents inadvertent double swaps.

Reference: page 164 at the bottom.


Cheers,

|-|ardy

Garry Richards

#54
Hi Markus,

I never expected the wide array of peripherals that people such as yourself are using with PSX. VisualPSX keeps the centre tank of the FSX aircraft topped up so its engines will not stop in flight. This is only of consequence to those using the FSX engine sounds.

I guess the solution for your purposes is for me to make the topping up optional. Would you like me to do that?

Cheers,
Garry

Website: flightsim.garryric.com

Markus Vitzethum

Hi Garry,

it is just one add-on for FSX.  :) (And one of the nice things is, I can do track maps of my flights with it and store them in a SQL database.)

As an alternative idea ... would it also be possible to sync each individual tank of the FSX default 744 with the respective tank of PSX? E.g. every 30 seconds? Using such an approach would allow the FSX aircraft fuel to be in sync with the PSX fuel status and have the accurate fuel number also in the xACARS reports.
I had no close look but it looks like each fuel tank in the B747-400 is present in the FSX model.

I think, if it works, this also helps with engines not running dry (in FSX).

But if not, I'm also happy with an user-selectable option. But then again, it looks like I have to battle the risk of engines running dry. (Do you have any more data on that? Are there any fuel pumps or is it selectable which FSX tanks are emptied first?)

Thanks a lot,
  Markus

p.s.
While we are at it ... is also possible to sync the parking brake?  :)

Britjet

Quote from: Garry RichardsHi Britjet,

I have found that the traffic selection procedure has bugs and will release a fix soon. Thanks for testing and reporting.

Cheers,


Thanks Garry, much appreciated.
Britjet

Garry Richards

Quote from: Markus VitzethumAs an alternative idea ... would it also be possible to sync each individual tank of the FSX default 744 with the respective tank of PSX? E.g. every 30 seconds? Using such an approach would allow the FSX aircraft fuel to be in sync with the PSX fuel status and have the accurate fuel number also in the xACARS reports.
I had no close look but it looks like each fuel tank in the B747-400 is present in the FSX model.
I've looked into this in detail and concluded that it would be too large a job. I've also decided to leave the fuel top up unchanged to protect users.

Quote from: Markus Vitzethump.s.
While we are at it ... is also possible to sync the parking brake?  :)
I tried to implement this - the code is in place - but SimConnect won't play ball. A pity because I had this feature working in the old PS1 days.

Cheers,
Garry

Website: flightsim.garryric.com

John Golin

To be honest the proper approach is an app to retrieve the data from PSX and sync the info... trying to bodge something through FSX is a very unattractive way to go about it...
John Golin.
www.simulatorsolutions.com.au

Markus Vitzethum

Hi Garry,

> I've looked into this in detail and concluded that it would be too
> large a job. I've also decided to leave the fuel top up unchanged
> to protect users.

checked. I can (and will) work around this. Thanks for checking.

> To be honest the proper approach is an app to retrieve the data
> from PSX and sync the info... trying to bodge something through
> FSX is a very unattractive way to go about it...

John, I fully agree with that approach. It is just that the specific app talking to PSX does not exist (yet? - it is also a matter of resources) and I am trying to work with an existing solution (which is luckily working mostly fine.)

Markus