Thursday, June 8, 2017

P3D v4, Unicode and vLSO

Guys,

As I posted earlier, the new Prepar3D version features Unicode support. I modified my FSchecker proggy so it now supports Unicode. You can try it to make sure it works well on your systems with P3D v4 installed.

22 comments:

  1. Hey Paddles, Thanks for the discussion on magic carpet. I have another issue. I am using uchi's kntu scenery in P3d v3 and I put the Mk14 file of yours in as directed on the install txt. It works perfect in FSX however, everyplace I have FCLP (ie Fentress, Choctaw, Meridian, Lemoore...etc) I can not see the IFOLS lights. When the sim first loads up it shows them. flashing...then I take off and the lights go dark and don't light up. I realize that most of the ifols were designed for FSX, however, is there a fix for P3d v3.

    ReplyDelete
  2. I tested FSChecker6 and works OK , but remember that P3D V4 now has many sceneries installed that not necesarily list in scenery.cfg...

    Jorge

    ReplyDelete
    Replies
    1. Oh, really? The v4 SDK states that 'The Scenery.cfg file stores the changes you make to your Scenery Library through the Prepar3D User Interface. You can manually edit this file using a text editing application such as notepad.

      Path to scenery.cfg
      %PROGRAMDATA%\Lockheed Martin\Prepar3D v4'

      However, you can place your custom scenery in any folder or even disk of your computer, but once installed via GUI it is listed in the scenery.cfg

      Delete
  3. Hi Robert,
    Unfortunately, these IFLOLS don't work properly in P3D. The only IFLOLS, which I do know works well in P3D, is the RFN gauge. This gauge will be fully supported in the new vLSO version

    ReplyDelete
    Replies
    1. Thanks Paddles. I for one appreciate all that you do for us.

      Robert "Axe" Timberlake

      Delete
  4. For me I am getting an Access Violation at Address 005D9E0B in module vLSO.exe read of adress 0000005A

    ReplyDelete
  5. Paddles , the P3D V4 community of Aicraft carrier pilots are getting desperate ... no RFN gauge , no SDB and no VLSO!!! give us an update as how are you going please ...
    Jorge aka aeronauta
    PS also an idea of how much are we going to pay for the new VLSO... I beleive that would be a fair option to recompense you for your work..

    ReplyDelete
  6. The upcoming version is 90% ready.

    ReplyDelete
  7. Appreciate it Paddles, looking forward to it.

    ReplyDelete
  8. Paddles

    Great news.
    Looking forward to it. Thank you!

    Russ

    ReplyDelete
  9. Fantastic news !!! Thank you..
    Jorge

    ReplyDelete
  10. With VRS saying they are not going to move the F/A-18E to P3D V4, I will probably stay with V3 for awhile. Will your next vLSO update also be compatible with V3, or only V4? Thanks.

    ReplyDelete
  11. It will support all P3D versions, from v1 to v4.
    It's a pity VRS won't support v4. I know that converting from 32 to 64 is a true PITA, but I hope they'll solve this problem

    ReplyDelete
  12. Great to hear Paddles! I agree with both of you points.

    ReplyDelete
  13. Paddles , can we give you a bit of a push in the way of an advance purchase commitment ?? give us a value and will see...!!!!
    Jorge

    ReplyDelete
  14. 1. I'd love to pay something for vLSO, one of the truly best add-ons with nearly a ZERO PITA factor!! So thanks!

    And to echo others - VRS not moving to support v4... sorry there are politics between them and LM ... but v3 will got the way of FSX soon. 64 bit is SOOOO much better.

    ReplyDelete
  15. How about this...???

    http://www.sim-outhouse.com/sohforums/showthread.php/107688-I-just-noticed-something-on-the-VRS-web-site

    ReplyDelete
  16. Hi Paddles

    Since the release of P3D v4.1 I've noticed that VLSO is no longer working. Anyone else seeing the same thing with 4.1

    ReplyDelete
  17. Mark , VLSO is a 32 bit app , it never worked in P3D V4 or V4.1 ...

    Jorge

    ReplyDelete
  18. That's because current vLSO simply does not support P3D v4, not because it's a 32 bit application. The next version (which is still 32 bit) will support 64 bit P3D, by the way ))

    ReplyDelete
  19. Oh I see , I assumed that it was going to be 64 bits , no problem running 32 buits outside of P3D .. for your info I run the tester on P3D 4.1 and works OK.. thank you for your work...

    Jorge

    ReplyDelete