Jump to content
The simFlight Network Forums

jcboliveira

Members
  • Posts

    1,699
  • Joined

  • Last visited

Posts posted by jcboliveira

  1. Some explanation.

    The anti irus could rely in signatures (see if inside the exe there is a match for the vírus pattern) or can also rely in heuristics. Heuristics is simply a nice word for common sense. The signature approach has some disadvantages, it only catch the virus after you update the database with that particular virus. The heuristic approach tries to overpass this problem by trying to guess if the file contains a virus, couldn’t find any information of how this is done. NOD32 is usually considered one of the best anti virus (maybe only surpassed by Kaspersky) however it can also raises the false alarms.

    In this case what you have to do is:

    - Temporarily disable IMON and AMON;

    - D/L FSUIPC

    - Unzip it (if you have problem right click, properties and unblock);

    - Install FSUIPC

    Enable AMON and IMON. You will notice that AMON will not detect FSUIPC.dll has a virus after install.

    José Oliveira

  2. I have FS9.1 latest FSUIPC and no problem with that plane. You could check what addons you have in the modules directory. The easy way is to sorte all the files by date. You will see a lot of them with the same date, those are FS9 modules. The others are the addons modules. Move the others from the directory and trie.

    Don't know why but I think it could be a registry problem. Open regedit and search for C400Loadout, bellow this key there is a key called version 3.0, see if the dwords for PortEngineDamaged and StarbdEngineDamaged are 0.

    José Oliveira

  3. "I am running a virtual airline, but I want to cut down my fleet to the 737NG. I´d like to know if there is a possibility to read out the ACARS information and send it directly to my cgi based database for the pilots rooster. No filling of pilot reports anymore (this is obsolete these days I think)."

    As far I know there isn't any SDK available from PMDG that will allow you that. Of course you can make (or use) a program that produces the acars messages.

    José Oliveira

  4. That is not a FS problem more a plane problem. In fact the tail Logolight, Landing light, Wing light etc are separated (I believe there are 19 possible light sources specified by MS SDK). In some planes you have the overhead switches working as they should. But the some producers (don't ask me why) choose to use the logo light in the texture and not using effects. Same goes for wing light etc. It's possible to change the planes to reflect the proper lights but it takes a lot of work.

    If you look at AVSIM you can find packages made for the 737 default.

    José

  5. Hi

    I know that is inefficient and I could pass the FSUIPC class address to the DLL as I did in the loader plug-in that I was trying to do, avoiding the double open, the only thing is that I don't have control over the dll code. Let's see if someone starts to do plug-ins.

    Tested the positions and didn’t detect any change. It could be a good method to change the plane weight, since it avoids the aircraft reloads that the loaders need. As far I saw it preserves the distances specidfed in the aircraft.cfg wich is good also.

    Thanks again

    José

  6. I have a program called FSAcars. This program uses FSUIPC. In this version it accepts plugins (dll that the program calls). This dll can also use FSUIPC.

    1- Since the dll aren't made by me and not my responsability if they use FSUIPC then they should manage FSUIPC calls if they want to use it.

    2 - The FSUIPC open function uses a file with the name given by the process name (to ensure that is unique) plus the retry name. The problem is that the dll and the program bellong to the same process so the name is the same. To ensure that there isn't any problem this name must be changed.

    The original file name in the DLL = program file name:

    wsprintf(szName, FS6IPC_MSGNAME1 ":%X:%X", GetCurrentProcessId(), nTry);

    The new name in the DLL

    wsprintf(szName, FS6IPC_MSGNAME1 ":%X:%X:DLL", GetCurrentProcessId(), nTry);

    A different problem: offset 1400 payload changes.

    Noticed that it only changes the aircraft weight reported by FSUIPC if you go in to "Change Payload menu" and press ok . Without pressing the ok the plane weight reported by FSUIPC stays the same as before the offset 1400 write.

    Thanks

    José

×
×
  • 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.