Jump to content
The simFlight Network Forums

deep42

Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by deep42

  1. Vorsicht mir dem Vistalizator. Man beachte diesen Link: http://social.microsoft.com/Forums/de-DE/genuinewindows7/thread/6f6b1cb8-e84e-4c1f-a2ac-181a77d2f772

    Eine Alternative ist hier beschrieben: http://mark.ossdl.de/2009/08/change-mui-language-pack-in-windows-7-home-and-professional/. Voraussetzung ist, dass man Zugriff auf ein Original Language-Pack hat.

    Hinweis:

    Zum Installieren der Sprachversion reicht der Befehl:

    dism /online /add-package /PFAD ZUR lp.cap

    BCDEDIT und BCDBoot sowie die Registry-Änderung braucht man nur, um die Anzeige-Sprache von Windows umzuschalten.

    Damit sollte FS2Crew in der Lage sein, die korrekte Sprache für die Spracherkennung zu verwenden.

    Ich muss dazu schreiben, dass ich das nicht mit FS2Crew (besitze ich nicht) sondern ausschließlich mit eigenen, Spracherkennung verwendenden Programmen ausprobiert habe.

    Hier gibt es auch noch einen interessanten Beitrag: http://keznews.com/6149_Download_Windows_7_MUI_Language_Packs_-_Official_32-bit_and_64-bit_Direct_Download_Links

    Gruß

    Peter

    P.S.

    Ein Image-Backup wäre vor der Aktion vielleicht ganz hilfreich, egal ob Vistalizator oder dism. Ich übernehme jedenfalls keine Garantie. ;-)

  2. First PayloadStation is for the 2 pilots, second and third for Front and Aft Stewart third and fourth for the Front and Aft Cargo. The following 68 stations each contain the weights for the 68 seats. (Flight1's ATR 72 Configuration Manager assumes 172 lbs for a man, 150 lbs for a woman, and 77 lbs for a child.)

    So I can calculate an average value for one seat from the available values, and a simple multiplication will give me an approximate payload.

    Fortunatly I dont need the exact value for my flight planning program, that depends on zero fuel weight and fuel weight values, of course. And theses values ar provided by FSUIPC.

    It is just that the program shows the values for empty weight and payload to the user, so they should not be totaly wrong.

  3. Sorry, I cannot offer any way. 61 certainly seemed many many more than anyone would need.

    Regards

    Pete

    Hi Pete,

    thanks for your answer, even so it doesnt make me happy :-(.

    Well, until 3 hours ago I assumed the same. But the developers of Flight1's ATR decided to use one payload station for every single seat. So they ended up with 73.

    Okay, I will have to do some calculations to get the payload (at least approximate).

    Regards Peter

  4. Hi Pete,

    I have a problem reading the payload station data using FSUIPC. Flight1's ATR uses 73 payload stations. But in offset 0x1400 is room for only 61 stations. The manual says "If there are more you can‘t access them this way."

    So my questions is: Is there a way to get those remaining 12 stations? I couldn't find one in the docs. Or is there another way to read the complete aircraft payload? I wouldnt need the individual stations data (currently)?

    Best regards

    Peter

  5. Hi Pete,

    Really, for an all WinXP setup, the best and most flexible way is to specify nothing at all in the Wideclient INI files (no protocol, no server details), and just use ProtocolPreferred in the Server's INI to select TCP, SPX or UDP. I use UDP throughout these days, but configuring it as I say allows you to change over just by changing that one Server parameter.

    I have done, what you have suggested. Now, everything is ok again.

    I should have read the manual and cleaned up my Ini-files earlier, but "never change a running system" :D

    Thanks a lot for your quick response.

    And BTW thanks for your great work, keep it up.

    Regards

    Peter

  6. Hi Pete, hi Peter

    both Server (name cw101; IP 192.168.0.101) and Client (name cw106; IP 192.168.0.106) are using Win XP SP2.

    @Peter: Thanks for the tip about the ServerName-entry. When I add the ServerName=xxxx line everything works fine.

    And it works as well if I remove the line ServerIPAddr=192.168.0.101 from the WideClient.ini.

    Thanks for your help

    Peter

    P.S.

    Here ist my WideClient.INI, (the one which doesnt connect):

    ##################################

    ; PLEASE SEE WideFS documentation for parameter details

    ; =====================================================

    [Config]

    Port=8002

    Window=32000,32000,160,34

    ;Visible=Min

    Visible=Yes

    ServerIPAddr=192.168.0.101

    ;ServerName=cw101

    ButtonScanInterval=20

    ClassInstance=0

    NetworkTiming=5,1

    PollInterval=2000

    ResponseTime=18

    ApplicationDelay=0

    TCPcoalesce=No

    WaitForNewData=500

    MaxSendQ=100

    Priority=3,1,2

    OnMaxSendQ=Log

    NewSendScanTime=50

    MailslotTiming=2000,1000

    Port2=9002

    Protocol=TCP

    ; -----------------------------------------------

    [user]

    Log=Errors+

    UseSendInput=Yes

    KeySend1=123,16

    KeySend2=123,24

    ##########################################

    and the WideServer.in:

    ###########################################

    ; PLEASE SEE the documentation for parameter details

    ; ==================================================

    [Config]

    Port=8002

    AutoRestart=0

    AutoUpdateTime=13

    MaximumBlock=4096

    NoStoppedRestarts=Yes

    RestartTime=10

    SendTimeout=15

    TCPcoalesce=No

    AdvertiseService=1

    Port2=9002

    ; -----------------------------------------------

    [user]

    Log=Errors+

    KeySend1=7

    KeySend2=7,1

    ; ===============================================

    [ClientNames]

    1=CW106

    ###########################################

  7. Hi,

    I have just updated to FSUIPC 3.65 and WideFS 6.6.5 (both registered).

    I copied the new FSUIPC.DLL and the new WideServer.DLL to the Modules folder of my FS9 installation and the new WideClient.Exe to the WideClient folder of my Client PC always overwriting the previous versions.

    Unfortunately now WideClient.exe doesn't connect to the server.

    If I replace the WideClient.Exe version 6.6.5 with my previous version 6.5.1 everything seems to work fine.

    Here is the WideClient.Log for the not working WideClient 6.6.5

    ********* WideClient Log [version 6.65] Class=FS98MAIN *********

    Date (dmy): 29/06/06, Time 00:10:29.953: Client name is CW106

    297 Attempting to connect now

    297 Trying to locate server: IP protocol needs ServerName or IP address!

    297 Failed to connect: waiting to try again

    1328 Attempting to connect now

    Why does version 6.5.1 work but version 6.6.5 doesn't? Any ideas would be appreciated.

    Thanks in advance

    Peter

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.