Jump to content


Highest Reputation Content


#417029 Updated modules

Posted by Pete Dowson on 18 October 2010 - 11:14 PM

Note that mostly this Announcement will contain only the changed modules. You will almost always need the main release installed first. For those please go to http://www.schiratti.com/dowson

The FS modules here, when supplied without Installer, need copying into the FS modules folder once extracted.

Please note the format here. The links for all the updates are listed first. For interim releases only, notes about changes are listed separately, below.

Install complete FSUIPC version 3.999z8 Install FSUIPC 3.999z8 for FS9 and before

-- For changes see the History document in the full install update.

FSUIPC version 3.999z9a only, for those with 3.999z1 or later already installed FSUIPC 3.999z9a

-- Fixes an ancient and obscure bug which nevertheless can crash FS on loading with certain INI file arrangements.

 

 

Install complete FSUIPC version 4.937 Install FSUIPC4937 for FSX and Prepar3D versions 1.4 and 2.0-2.4

FSUIPC version 4.937b, for those with at least 4.937 already installed FSUIPC 4.937b

-- Deletes orphaned profile entries from INI

-- Keeps axis assignments for new profiles if so requested

-- Fixes error in Lua mouse.wheel function.

-- Provides OOMcheck=Quiet option (no audible VAS warning)

-- Single byte offset 3124 gives P3D EXE version number, 10-14, 20-24.

 

WideFS version 6.999m WideFS 6.999m
Full release including documentation.
-- signature removed

-- See WideClient changes below.

 

WideClient 6.999m WideClient 6.999m
-- signature removed
-- 6.996 adds a colour facility to ipc.display.
-- Wideclient 6.997 with "event.textmenu" support in Lua (FSX only)
-- WideClient 6.998b supports text menus with more than 400 characters using FSUIPC 4.909 or later.
-- WideClient 6.999 fixes an odd bug when applications connect with bad Atom names.

-- WideClient 6.999b fixes a problem with Radar Contact options when generating APL plans from PM's CDU.
-- WideClient 6.999i supports extra Lua functions: see FSUIPC4 History

-- Wideclient 6.999j adds event.offsetmask.

-- The ButtonScreen now sends no button change for positions without a label or with a single space as a label.

-- Plan generation from the PM CDU "Route.bin" file deals with the latest format containing 'degree' signs.
 

PFC driver version 2.41 for FS9 and earlier PFC 2.41
PFCFSX driver version 4.41 for FSX, ESP and P3D PFCFSX 4.41
-- signatures removed

PFC HID device driver version 1.41 for FS9, FSX, ESP and P3D PFCHID 1.41
-- signature removed
-- 1.33 fix for AP APR mode not setting Glideslope option

-- 1.34 fix for macro name matching and proper macro file selection on aircraft change

-- 1.35 fix for a silly bug introduced in 1.34 which could significantly slow FS down!

-- 1.36 eliminates a 1-2 second pause when AutoSave options are in use

-- 1.37 added support for separate macros for positions on multiway switches

-- 1.38 and 1.39 only added clearer logging, especially for macro file selection

-- 1.41 fixes some further macro selection problems

 

Pete Dowson
15th October 2014


  • 3


#451010 New FSUIPC4 registrations for 2013 need version 4.859n or later!

Posted by Pete Dowson on 14 January 2013 - 05:26 PM

Oops. Same date limit was in FSUIPC4 too!

Pete
  • 2


#450631 FS Commander won't let me load flightplans?

Posted by JerryJet on 03 January 2013 - 12:42 PM

So it can save flightplans in those formats, but can't then reload those very same flightplans unless they exist in FSC's format? And I paid $40 for this??? Can I just say how stupid that is?


Flightsim Commander is released as shareware letting you evaluate the program to see if it suits your needs. You can also read the exhaustive manual which explains how and why FSC saves flightplans. Numerous different planes/companies can be chosen when saving, but one is always checked and can never be unchecked. I'll let you figure out what that means.

Jerry
  • 2


#473460 Thank you Peter

Posted by Jennifer on 08 November 2014 - 05:18 PM

Peter, I have created this account so I can stay anonymous. I don't want or need any recognition or thanks. This post isn't about me, it is about you.

 

I first purchased FSUIPC back in the early days. I have used it every since, from one computer to another. You have always, at least to my knowledge, allowed us to reuse it, without paying another charge. I am in the process of moving to PD3. I have just built a new computer to run the new program and I purchased a new copy of your FSUIPC and WIDEFS.

 

I did it because I consider you one of the greatest contributors to the hobby of flight simulation and flight simmers. As a former military and general aviation pilot I understand the added immersion flipping real switches and turning real knobs adds to the illusion of actually flying. Because of your charitable gifts to flight simming, and I consider them gifts, we can all enjoy the hobby so much more.

 

So thank you for FSUIPC and your continuing support of the program. Few, if any, have given so much to Flight Simulation than you have. My buying an additional copy is a small measure of my thanks.

 

 Jennifer


  • 1


#473174 Several issues with NWI

Posted by Pete Dowson on 29 October 2014 - 04:50 PM

Hello, Pete.
I've tested those issues with FSX and P3D 2.4 with FSUIPC 4.937 installed on both.
 

It looks like FSUIPC generate incorrect metar string for wind layers.
I can set 3 layers of winds by setting metar:

GLOB 151552Z 20000KT&D100NG 20202KT&A200NG 20404KT&A400NG CLR 15/05 Q1013
And I get 3 layers of winds.
As I think similar configuration set to NWI generates metar:
szMETAR="GLOB 151041Z 20000KT&D100NG 20202KT&A200NG 20404KT&A200NG 0050&B0&D1 CLR 15/05&A24 Q1013 "
And I get only first 2 layers. Count of layers is 2 because in NWI generated metar second and third layers have similar altitude. 
 

 

I would need to see the actual NWI writes you are making to comment on that. When I test using the WeatherSet2 program, which is the demonstration and test bed for NWI, it works. To understand what might be wrong in your case I would need to see exactly what you are doing. Maybe via logging?

 

I won't have time in any case to look at this till December now, earliest, and i would be loathe to change anything because it is very old and very complex code and I'm likely to do more harm than good. It is also well used code, at least in the past. Nowadays good weather programs like OpusFSX and ActiveSky use SimConnect directly of course.

 

The above also applies to your precipitation base question. I am really amazed you can find such discrepancies after all these years though.

 

If I understand correctly, you recommend to use METAR for setting weather in FSX and P3D.

 

 

Well it involves much less for FSUIPC to do -- it simply passes it on without checking. so any errors are yours. ;-)

 

It's really my best answer because I don't think I'm in any position to ever adjust or change the NWI.

 

So, should I use offset 0xB000 for setting metar? 

 

 

If that's where it is documented -- sorry, i don't have access to my reference documentation at present. I think you might still need to set the ICAO (or 'GLOB') ID into the C8xx area -- doesn't it say that?

 

Does it matter what a day and time to set in metar after icao code?

 

I don't know. i wouldn't have thought so.

 

What a correct sequence for setting the metar for: 1) an arbitrary weather station 2) global (and replace weather on all stations) 3) all station was not set?

 

 

Why would there be a "correct sequence"? I'd need to refer to the Simconnect documentation for such data in any case. All FSUIPC is doing for you in the mode is sending the request on.

 

And how to get a global and station weather? 

 

 

You read the weather as documented. That populates both the NWI data areas AND gives you a METAR in the appropriate offset -- probably B800 as far as I recall?

 

Please be aware that the formats of READING and WRITING weather are rather different in a number of areas. The documentation is not good for either. Maybe the documentation in the P3D SDK is better. I don't know.

 

Regards

Pete


  • 1


#473003 Several issues with NWI

Posted by Pete Dowson on 24 October 2014 - 04:25 PM

  1. Wind layers. All is good when count of layers <= 2. If count of layers is greater than 2, it applies incorrectly. Seems like data (except UpperAlt) in all layers, except for the first two, are shifted by 1. I wrote a workaround for layers with indexes greater 2. I can describe my solution if it neccessary

 

Is this a new bug in P3D's SimConnect?  Have you checked the actual SimConnect METAR strings which are being sent to SimConnect, because all the NWI does is make FSUIPC build those strings. I'm pretty certain it's always been okay with FSX and SP2/Acceleration versions of SimConnect.

 

 

  1. Visibility.
    • a ) Why visibility is broken into two parts: a field Vis and an array UpperVis? Is this correct to count Vis as a first layer and layers from an array as a consequent layers? 
    • b ) When I write visibility layers to global section of the NWI, only layer from Vis is applying. When I read visibility layers from the NWI global section, I also get only first layer in Vis.

 

In FS2004, for which the NWI was devised, it was only possible to have one visibility layer. Trying to use more never worked. Therefore the original design was for one layer. The additions was done in such a way as to not break existing programs. And yes, the layers all count.

 

I suspect the Global weather facility in SimConnect only allows one layer still. The global setting is really only used as the initial default for weather stations not yet set up.

 

 

 

  1. Clouds.
    • a ) When I write cloud turbulence 0, it apply as 1 in P3D. So I can't set no cloud turbulence. All other values works well.
    • b ) Precipitation base altitude apply to P3D weather 10 times less. So I should to multiply this altitude by 10 before set it. It is not bad solution, but it reduces this altitude's available range to write.

 

Check the METAR string being sent. It sounds like some odd changes in the SimConnect weather interface have been introduced. Please just double-check using the string versions -- you can get those by FSUIPC's logging or SimConnect logging.

 

If P3D have changed these things I suggest you might want to look at sending the METAR strings yourself rather than use the NWI.  I'd hoped folks would have moved on by now from that system devised in 2003 to match the binary hacked interface into FS2004.

 

You can send the strings via FSUIPC if you'd prefer not to use SimConnect directly.

 

 

 

  1. When I set up a lot of layers of clouds, winds and temperatures, a graphical artefacts are appear in the sim. In some cases weather in the sim simply disappear and weather set to clear (visually).

 

Hmm. Sounds like quite a few of the bugs in FSX's weather facilities have been carried over into P3D and maybe even made worse. Of course FSUIPC has no control over "artefacts" I'm afraid.

 

Pete

 


  • 1


#472989 Airbus & FSUIPC.ini settings for AutoSave

Posted by Pete Dowson on 24 October 2014 - 09:40 AM

In the manual I read: 

Up to 32 “AlsoManage” lines can be given, numbered 1 to 32.

 

but I did not know that only 8 of these lines are supported, yes I think it would be great if this can be expanded.

 

Oops. It IS 32! I was looking at an old printed version of the manuals -- I am too mean to keep printing new editions! Sorry. It used to be 8 -- it was changed in version 4.80, a couple of years ago!

 

So, assuming you aren't using a pretty old version (check that first please), something else is wrong.

 

I notice here:

 

AlsoManage8=PMDG\PMDG 777X\PanelState\*.FLT.0.rte
 
(for examples), that although there are spaces in the complete pathname, it still works without the " ". So maybe you don't need those " " around lines 9 and 10 after all. Can you try without? (Sorry I'm hypothesising in these matters -- all this code is so old (as am I) that I can't recall it all, and delving into it sometimes takes longer than simply trying things).
 
Pete

  • 1


#472987 Airbus & FSUIPC.ini settings for AutoSave

Posted by Pete Dowson on 24 October 2014 - 09:24 AM

The AlsoManage 9 and 10 is not working, everything else is working.

Any idea why?

 

As most certainly documented, there are only 8 AlsoManage entries supported. Up till now that's always been plenty. I could see if that's easy to extend and if so, do so.

 

One more question was it the line "Next2" for I did not find this in the manual.

 

 
"Next=" just keeps track of where, in your cycle of 10 saves, the next one to be replaced goes. You can see line 1= has the latest time, line 2 the earliest, so it is next to be removed and re-used.
 
Pete

  • 1


#472863 Rudder & Steering Tiller problem

Posted by VHRAK on 19 October 2014 - 09:46 AM

Being an old senior citizen and new to FSUIPC I have a small problem and have spent many hours trying to come up with a solution and thought " lets ask the experts"

The only aircraft I fly is the Sim-Avionics B777 in FSX......There are 2 controllers FDS FC1 which controls the toe brakes. They work fine. The other FDS FC1 controls the Elevators, Ailerons, Rudder and steering Tiller. Everything works except the Rudder & Steering Tiller. All the controls are assigned via FSUIPC. Herewith my fsuipc4 ini file for your perusal.

[General]
UpdatedByVersion=4934
History=7RSANSW7Z4M2ZVG7EGAVN
InitDelayDevicesToo=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=Yes
FixMachSpeedBug=Yes
DeleteVehiclesForAES=Yes
AutoScanDevices=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=Yes
SuppressWindVariance=Yes
WindTurbulence=No
TurbulenceRate=0.5,2.5
TurbulenceDivisor=40,40,80,80
SuppressAllGusts=Yes
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=Yes
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=Yes
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=Yes
RudderSpikeRemoval=Yes
ElevatorSpikeRemoval=Yes
AileronSpikeRemoval=Yes
ReversedElevatorTrim=Yes
ClockSync=Yes
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=No
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
OOMcheck=Yes
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
LuaRerunDelay=66
Console=No
NewInterceptTextMenu=No
DelayedMouseLookZoom=No
FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0
SimConnectUsed=10.0.61259.0
 
[JoyNames]
AutoAssignLetters=No
0=FDS-FC1
0.GUID={C6662850-0034-11E3-8001-444553540000}
1=FDS-FC1
1.GUID={C6662850-0034-11E3-8002-444553540000}
 
[Buttons]
ButtonRepeat=20,10
1=R0,1,C65607,0
3=R0,3,C65615,0
4=U0,3,C65706,0
5=U0,1,C65706,0
 
[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No
 
[GPSout]
GPSoutEnabled=No
Port=COM1
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=
 
[GPSout2]
GPSoutEnabled=No
Port=<none set>
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=
 
[WideServer]
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002
 
[Sounds]
Path=F:\FSX\Sound\
Device1=Primary Sound Driver
Device2=Realtek Digital Output (Realtek High Definition Audio)
Device3=Speakers (Realtek High Definition Audio)
 
[ClientNames]
1=FLIGHTSIM2
2=FLIGHTSIM3
3=FLIGHTSIM4
4=FLTSIM4
5=FLTSIM5
6=FLTSIM3
 
[Profile]
1=Sim-Avionics 777-200ER
 
[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=Yes
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Aileron=-16380,-9091,-9091,-9091
Elevator=-1478,3744,7808,13792
Rudder=-6264,1984,1984,8576
LeftBrake=16288,16380/16
RightBrake=16352,16380/16
Flaps=0,16380
SteeringTiller=16192,16192,16192,16380
SlopeLeftBrake=-3
SlopeRightBrake=-3
 
[Axes]
RangeRepeatRate=10
0=0Y,256,D,2,0,0,0
 
[Axes.Aleirons]
RangeRepeatRate=10
0=0X,256,D,1,0,0,0
1=0Y,256,D,2,0,0,0
2=0Z,256,D,3,0,0,0
3=0T,256,D,36,0,0,0
4=1R,256,D,8,0,0,0
5=1U,256,D,7,0,0,0
 
[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=Yes
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
SteeringTiller=16192,16192,16192,16380
Rudder=-6264,1984,1984,8576
Aileron=-16380,-9091,-9091,-9091
Elevator=-1478,3744,7808,13792
Flaps=0,16380
 
[Buttons]
0=R0,1,C65616,0
1=R0,2,C65615,0
 
[Buttons.Aleirons]
0=R0,1,C65616,0
1=R0,2,C65615,0
 
[Profile.Aleirons]
1=Aleirons
 
[Profile.B777]
1=Sim-Avionics 777-200ER
 
[Buttons.B777]
2=R0,1,C65607,0
3=R0,2,C65615,0
4=U0,2,C0,0
 
[Axes.B777]
RangeRepeatRate=10
0=0X,256,D,1,0,0,0
1=0Y,256,D,2,0,0,0
2=0Z,1139,D,3,0,0,0
3=0S,256,D,36,0,0,0
4=0T,256,D,36,0,0,0
5=1Z,256,D,8,0,0,0
6=1R,256,D,8,0,0,0
7=1U,256,D,7,0,0,0
8=1V,256,D,7,0,0,0
 
[JoystickCalibration.B777]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=Yes
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Aileron=-15730,-1959,1676,16337
Elevator=-16207,-1057,1443,16177/16
Rudder=-16384,-1927,3137,16296
LeftBrake=2240,16256
RightBrake=2272,16224
Reverser=-16380,16380
FlapStarts=-16384,1,16379
Flaps=0,16380
FlapEnds=-16384,1,16379
SteeringTiller=-16191,-2084,-128,16383/16

Really appreciate your help...Thanks


  • 1


#472535 Prepar3d V2 - scenery issues

Posted by von on 11 October 2014 - 10:02 AM

With so many versions of P3D is is hard to understand where your program "installer"  is installing your software properly and supported / working properly.

 

I wonder how many pilots still have old versions of P3D installed?

Because you are spending a lot of time fixing your software for "all" previous versions of P3D.

 

I am current at P3D V 2.4

 

Actually, my specific question:

 

Does your current product installer setup file install your software automatically to P3D v2.4?


  • 1


#472490 How to add signature to Profile?

Posted by Ian P on 10 October 2014 - 03:07 PM

...or we can sneak ninja-like into the back office and change you to a member... Like... That...  :ph34r:

 

Wasn't me, honest guv!  :rolleyes:


  • 1


#472097 FS Commander problems on networked laptop (solved)

Posted by BPD on 25 September 2014 - 08:13 AM

For those suffering the problem of missing network drives that have been mapped under Win 7, may I suggest following this link:

 

Missing network drives in Windows 7 | Remote Administration For Windows

 

It solved the problem for me.

 

BPD


  • 1


#472030 FSC can't recognize important pathes (solved)

Posted by VolkerHeine on 23 September 2014 - 05:28 AM

Hi Morton,

 

The ONLY, however indeed serious, problem is that FSCommander won't show up the 'Z' drive to the FSX server path in the saving dialogue, which makes it impossible to save any flightplans. 

 

 

I'm sure you understand the following text.
If it is an error of the FlightSim Commander, then it would be a big problem.

 

Regards,

Volker

 


  • 1


#471950 Prepar3d V2 - scenery issues

Posted by Burkhard on 20 September 2014 - 08:46 AM

Happy to announce, that today I got through with the redo of all airports for P3D V22+ - 4 months of awfull work :(


  • 1


#471786 FSX Fiber Accelerator 1.310

Posted by BD-FSPS on 14 September 2014 - 10:13 AM

Your FSX frame settings never changes. It is consider the upper limit for frames.

 

You will have to READ the product's manual and understand how the application works.


  • 1


#471701 Toper 3 not working

Posted by nixdevelopment on 12 September 2014 - 01:09 PM

and also I would like to know what was fixed just out of curiosity. =)

 

UI was re-built from the ground up. Using template from earlier versions/projects seemed to fail on some machines, for reasons that are not known to me. 
I will be issuing an official update soon.


  • 1


#471689 Toper 3 not working

Posted by nixdevelopment on 12 September 2014 - 10:54 AM

...And it's me who make on pmdg777 page in facebook that Toper777 v 3 is out.

 

Regards

Thank you very much for this. I am very pleased you shared my tool with others to enjoy.


  • 1


#471547 LUA COM library

Posted by Pete Dowson on 09 September 2014 - 12:35 PM

Ok, I did some testing with updated code:

handle = com.open("COM3",9600,0) --COM 3 opened, 9600bps, no handshake
while 1 do
com.write(handle, "a")
ipc.sleep(500)
com.write(handle, "g")

ipc.display("overhead driver ok")

end

which does something... the message appears, the script runs, the Receiving LED on Arduino blinks quickly, but the arduino is not receiving what it is expecting to (the "a" should turn on a LED, the "g" should switch the LED off - which works from any Serial terminal app, so the arduino code is correct). Is here any way how to log the outcoming traffic from LUA?

 

 

 

I always debug serial port (COMn) problems using the free debugging tool "PortMon" from http://technet.micro...b/sysinternals/

 

Pete


  • 1


#471415 Who can help me

Posted by Paul Henty on 05 September 2014 - 09:02 AM

Hi Gerrit,

 

From what you wrote in post #9 above, you seem to be following the correct procedure.

 

The steps are written in the document called "installing and registering FSUIPC4.pdf". This is found in the Zip file containing the FSUIPC installer.

 

The procedure is the same for registering FSUIPC, except you just choose the WideFS radio button.

 

You say that the key disappears from the screen when you press ok. Normally, a message appears under the key input area. It will either say "Thank you. Registered okay", or tell you that the key is invalid.  With invalid keys it blanks out the key input fields. With a successful registration the key stays. 

 

Are you getting a message underneath the key saying the key is invalid?

 

The only way I could get the key to disappear without a message appearing underneath was pressing the [clear] button.

 

Paul 


  • 1


#471160 Can't create sessions on multiplayer?

Posted by scoobflight on 27 August 2014 - 07:37 PM

you always have to prearrange a session as you need to have the IP addresses of the participants.

 

post on this forum and ask for folks to contact you.  arrange a time via PMing each other and sharing IP addresses.


  • 1



About simFlight - simflight.com - simflight.de - simflight.fr - simflight.nl - simflight.pt - simflight.es - simflight.it - simflight.jp - simrussia.com - simMarket