[Saving QW FP - an odd problem]

Hi Volker

Didn't see an attachment but assume you were referring to the .ini file within the support folder. Checked that and the 09 path was good.

At the same time, I noticed that the QW fp seems to be in the same format at FS9 and I realised that I had never saved a file into the default FS2004 flight simulator files folder {never use FP in that folder.} So just to make sure that the path was correct, I saved a couple of fp into that folder. Then tried QW again and it worked!

Now repeated several times - including going back thro' FSX and P3D and it is still ok in FS9.

Looks as though its all ok now - as always many thanks for your help.

Best Wishes

John

[Saving QW FP - an odd problem]

Thanks Volker

Support folder sent.

I have just tried again after checking all my paths etc with the same result. When I save to QW in FS2004, I see the following error message:

"Error in writing FS9 plan"

This is using the QW146 - I have no other QW aircraft

All other add-ons write FS9 plans correctly..........

regards

John R

[Saving QW FP - an odd problem]

I've been running FSC on a networked system for many years and recently upgraded to V 9.2.1. Just installed QW146 and found the following problem trying to save QW fp:

1. Using FSC in FSX - no problems, I can save all add-on aircraft fp into their relevant folders in FSX: Ifly, PMDG etc and QW.

2. However when using FSC in FS2004, I can again save such fp as iFly and LDS but I cannot save QW. If I try to save QW I get a "cannot find FS2004" error - yet I have the correct FS2004 path set and iFLY etc save without problems.

Anyone any ideas?

John Rooum

[Lost WideFS Connection to FSX Only]

Pete,

Many thanks for your prompt help as always.

Ports were all correct with no conflicts. I eventually went for any changes I had made over the last few weeks and un-installed a couple of programmes I had tried. I then un-installed MSE from both systems (which I had swopped for AVG Free as the latter seemed to be growing with every update) - no change. I then reinstalled MSE to search on line for solutions but carefully made sure that both firewalls were off. The first option I tried after this - "voila" Wide FS connected immediately and after a couple of tweaks simconnect was also back on line.

In the end, I suspect that somehow a firewall had still been active on one of the systems - although I don't understand why it only affected FSX and not FS9?

An interesting 24 hours but we got there.

Best Wishes

John R

[Lost WideFS Connection to FSX Only]

For well over a year, I have been running FS9 and FSX {on 2 separate partitions} networked to a second computer via an ethernet connection as an FS Support system with Wide FS to run programmes such as Squawkbox, FlightSim Commander etc etc. During the last month I flew FS9 exclusively but today tried FSX. It ran correctly except that Wide FS would not connect. Fsx showed Wide Server waiting for clients and Wide Client showed waiting for a connection. A copy of the wide client log is as follows:

Date (dmy): 13/01/11, Time 17:40:06.640: Client name is JER

94 Attempting to connect now

110 Trying TCP/IP host "JER1" port 8002 ...

110 ... Okay, IP Address = 169.254.208.49

21172 Error on client pre-Connection Select() [Error=10060] Connection timed out

21172 Ready to try connection again

Repeated until I close dowm - note, the IP Address identified by the log is correct

So far I have checked the installation on both computers against the Wide FS manual, ensured all firewalls etc are turned off, reinstalled my windows network, and checked that all necessary files are shared and can be seen and opened in Network Places.

All to no avail. But Wide FS/FS9 still works perfectly! On the other hand, I have also lost the FSX Simconnect connection between the two computers!

So it seems to be something blocking the client computer seeing FSX - with either Wide FS or SimConnect - but nothing else!

Not sure where to look next so v grateful for any suggestions

John R

[IVAO - Display of On-Line Aircraft]

Volker,

Started a new thread as it appears that this is a totally different issue to the last post. If my understanding is correct {after an exchange on the IVAP forum}, it is worth publicising here in case anyone else is confused

In essence, there seems to be a significant difference in the way VATSIM and IVAO softwares treat on-line multiplayer aircraft on FS9.

Vatsim software identifies all on-line aircraft as "ordinary" FS9 AI aircraft - they are identified in Traffic Explorer and pass through FSUIPC to FS Commander as such. Thus they are displayed by FSC as normal AI aircraft.

However, IVAO software {IVAP} has a built in TCAS system which looks for multiplayer aircraft with Transponders "on". Any without a Transponder On" are ignored. Those with a transponder "On" are {I assume} passed through FSUIPC as a traffic table to the IVAP TCAS for display. This same table is passed to FS Commander and displayed as AI aircraft. Thus FSC only displays aircraft with transponder on - which is why they appear when turning onto the runway and disappear when turning off the runway.

Of interest, FSX is different. IVAP uses simconnect so passes those on-line aircraft with Transponder "on" direct to IVAP TCAS whereas all IVAP on-line aircraft [even without transponder} are also still identified as "AI" for the FSUIPC traffic table and passed thro' to FSC separately. Hence, in FSX, FSC "sees" all on-line IVAO aircraft both in the air and on the ground.

Hope this might help others.

Regards

John

[Missing plane on the map]

Volker,

I do appreciate that - I have been using FSC for many years both on and off line. But this is a crazy problem. It only occurs with IVAO/IVAP - using VATSIM/Squawkbox I see all traffic as appropriate. The key seems to be that ground traffic will only display when it is on the runway - once it turns off the runway it disappears. It must be something somewhere in the FS9 - IVAP - FSUIPC - Wide FS - FS Commander interface which differentiates between aircraft in the landing/take off phase and those taxying or parked. As Squawkbox has no problems, it could be something in the data that FS9/IVAP is sending to FSUIPC?

I've searched all the relevant forums with no luck - I'll try a post over at IVAP next.

Bets Wishes

John

[Missing plane on the map]

Wonder if anyone has seen any other solution to Rolf's problem. I have exactly the same setup and have recently installed IVAP to fly IVAO.

Watching the FSC display compared with the IVAO aircraft that I can see in FS9:

1. Landing aircraft show in FSC throughout the approach and touchdown but disappear as they turn off the runway.

2. When aircraft are taxying out, they are not on the FSC display but as they turn on the runway, they suddenly appear on the FSC display.

Almost as though, IVAP/FSUIPC has a "switch" which recognises aircraft entering or departing a runway.

Note - standard FS9 AI traffic or VATSIM traffic is still show correctly on the ground.

Many thanks in advance for any ideas.

John R

[Black screen]

Pete,

Thanks for the response. I wasn't criticising but had discussed this problem on two other forums with guys who had the same problem with a lot better hardware than I have. Hence I came here to see if there was anything else I might try. By the way, it occurs using Alt-enter as well as the menu.

However, I have found that if you switch off AA in FS9, the dialogue box comes up and can be accessed ok but with a black screen behind it. This is even if you are using AA through the graphics card control panel.

In addition, there are other odd graphics issues with Win7/FS9 in full screen mode [eg right click over scenery area and cursor changes from white arrow to solid black arrow} so I guess it goes back to my original conclusion that I have a Win7/FS9 problem which could be graphics card and/or drivers or perhaps DX11 incompatibilty etc etc .

Best Wishes and, as always, many thanks for all your efforts in keeping FSUIPC etc available to us.

John R

[Black screen]

Unfortunately, I have the same problem with Win 7 and have tried:

1. Two separate computer systems {one AMD, One Intel C2D}

2. Two different graphics cards {NVidia + ATI}

3. Several different drivers from original win7 drivers to latest from the card manufacturer.

All with no effect - select FSUIPC in full screen and FS9 goes black screen.

Odd that FSUIPC in Win 7/FSX is ok.

Suspect that perhaps its a Win7/FS9 problem but to date no other add-ons have any problems. Grateful for any other options I might try.

Many thanks

John R

[FSX - Registering Wide FS?]

Thanks Pete.

"Interpretation" was the wrong word. Particularly as I am English and not many miles away from you.

I don't pretend to understand the intricacies of FSUIPC but when I read that the "client part is the same as before" etc, I am afraid that the wish was master of the thought and I jumped to the wrong conclusion.

Ah well, off to SimMarket for Wide FS {and I have missed out on the bundle - that'll teach me}.

Best Wishes

John

[FSX - Registering Wide FS?]

Firstly my apologies - I have searched but could not find the answer.

I have a fully registered copy Wide FS for FS9. Today I have purchased a license for FSUIPC for FSX and I interpreted the web site as not requiring me to purchase a new Wide FS license {as the FSX server is already in FSUIPC4}.

However, while I can immediately register FSUIPC4 in FSX, I cannot remove the "register Wide FS" box.

Grateful for advice.

John Rooum

[X52 Axis not recognized.]

Interesting - I have spent the last few days trying to use this axis of my X52 as the steering tiller using the new Beta version.

To add to Francois' comments - both rotary axes on the X52 throttle [the other is below the highlighted control in the screenshot] can in fact be assigned directly in FS9. I have used the highlighted one for several months as a tiller by assigning it to rudder control in the FS9 assignments dialogue. FS9 also seems to retain the twist grip stick as a rudder control by default.

However, when using FSUIPC control, the highlighted rotary control is not recognised either in "assignment" or "calibration". Occasionally, when the control is first moved FSUIPC will assign a letter but that is all - the numbers do not change as the control is moved.

But of note, the other rotary axis control can be assigned using FSUIPC and works perfectly as a tiller. Not as easy to use but still effective.

I have no idea why the highlighted control cannot be assigned in FSUIPC - a quirk in the X52 software perhaps??

John Rooum