Jump to content

majapahit

Members
  • Posts

    1712
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by majapahit

  1. download and use simFBB it's way better FFB
  2. For the Rift in DCS KA-50 & A10C do you need the Touch Bundel / 2 remotes and sensors or perhaps its convenient for xtra functionality? (special offer now in NL 519,- euro)
  3. Thrustmaster TARGET Script manual gives HEX USB codes as examples and a list HEX USB appendix. Thrustmaster TARGET GUI generates USB ‘decimal codes’ per a dropdown and are somewhat ASCII, but I cannot find a list of corresponding decimal numbers and key references. What ‘decimal’ code/list is used for TARGET GUI USB keystrokes? THX
  4. Was looking for an update for Logitech G940 Leds that works with my 2017 DCS 1.5.xx Since I found the solution buried deep in a thread I thought I would mention this. I'm running latest DCS.1.5.7.7473.311 found a working export.lua dated 2017 from PVI_Eagle Thanks PVI_Eagle has the following aircraft inside, "UH-1H" "Ka-50" "M-2000C" "A-10C" "L-39C" "L-39ZA" tested KA-50 left 4: weapons targeting (RED on/off) right 4: autopilot (GREEN on/off) https://forums.eagle.ru/showpost.php?p=3059069&postcount=5 direct link his export.lua https://forums.eagle.ru/attachment.php?attachmentid=157780&d=1487757102 needs Morg's G940leds.exe (not his example_export.lua which is obsolete) Post https://forums.eagle.ru/showpost.php?p=772603&postcount=20 Direct link https://forums.eagle.ru/attachment.php?attachmentid=32827&d=1256749524
  5. Is there an update on this install for KA-50? running latest DCS.1.5.7.7473.311 EDIT: found a working export.lua dated 2017 from PVI_Eagle has all aircraft inside, tested KA-50 left 4: weapons targeting (RED on/off) right 4: autopilot (GREEN on/off) https://forums.eagle.ru/showpost.php?p=3059069&postcount=5 direct link his export.lua https://forums.eagle.ru/attachment.php?attachmentid=157780&d=1487757102
  6. This happened in my A10C It was HUD and canope mods, color, size, etc If you run mods, disable them all and see what happens .. ?
  7. because the different buttons have different 'logic' in their 'mechanics' they're the same in pairs, but do everything different in switching 'state' I use good old TARGET to define those 'non default hardware' actions. Gear up/down can be done in 1 toggle with a specific switch, but that's more the exception than the rule, any other action 'when press' 'when release' one must use TARGET, I didn't before with a 7970HD or a GTX 970 card, for it eats CPU, but now with a GTX 1080, I don't notice TARGET running.
  8. Not a solution, but you're assigning two different values to the same action <value_down = >, that can't be right
  9. you can make your GUI 1,2, 3 etc wide bytheway, all will fix labels as long as you start with x=0 (apparently labels overlay x coordinate had a parameter in its equation set to the fixed left x parameter of the GUI, an oopsie)
  10. start as usual your GUI (& the game messages) will be on the left screen, that's all (and the labels not in a crazy place)
  11. to 'fix'/workaround in 1.5.7.x define your GUI starting left screen your radio messages etc, will then also appear on left screen (not bad actually) GUI= { x = 0; -- <======= This fixes Labels, GUI on left screen y = 0; width = 1920 ; height = 1200 ; or 1080 if you have 1080p } UIMainView = GUI -- UIMainView = Viewports.Center DO YOU READ THIS DCS, labels are fixed with GUI starting at the left screen, so ......
  12. After updating to Update 1.5.7.7473.311 (which runs really smoothly) I noticed a bug with my 4 monitors setup. Display of labels his major 'offset' (like 3 mile to the right @ 3 miles). Using 4 monitors in T-formation 5760 x 2160 When testing using only one monitor 1080p, there's no problem. Attached a screenshot.
  13. = SOLVED - Found it was 1 of my many Mods (HUD mods, color, canopy) drilling down now which one exactly
  14. LABELS way off 1.5.7.7631.314 (and 1.5.7.7473.311) Labels of targets and objects are off-set by a couple of miles ! A10C
  15. version 1.5.7.7473 isn't even mentioned in the DCS update thread, is it stable? You know the change log for this one (so I might try this on)
  16. A10C latest update DCS 1.5.7.7631.314 to Dark HUD? autoupdate_log_old INFO : DCS/1.5.6.5199.291 (x86_64; EN; WORLD,A-10C,FC3,CA,SU27-ULTIMATE_campaign,KA-50,UH-1H,SU-25T_video_EN,KA-50_video_RU,FC3_video_EN,A-10A_video_EN) STATUS: Successfully updated to 1.5.7.7631.314 Did 2x update repair Deleted and reinstalled A10C module same result, Ray Ban HUD when reverted back to 1.5.6.5199.291, clear ?
  17. STATUS: Successfully updated to 1.5.7.7631.314 STATUS: Asking Yes/No: OS restart is required before running the game. Restart now? What's with the "OS restart is required before running the game" with 1.5.7.7631.314 an environment variable? // never see this before ..
  18. " How to repair or update DCS World? Windows Start Menu / All Apps / Eagle Dynamics. Locate the Repair option for the DCS product (version) you wish to repair. Note that you can do both repairs and updates from this location. Cleanup and repair Remove your user mods if you have any, and backup any changes go into your Eagle Dynamics\DCS World [Openalpha,openbeta]\bin folder. There, hold Left Shift and right click and click "Open Command window here." ( Windows 10 creators update now uses powershell, type cmd in powershell and then continue ) Then, type the following exactly as printed: DCS_updater.exe cleanup this will delete all non official files then do a dcs repair DCS_updater.exe repair You can find the youtube tutorial here: " it's a good idea to download and figure out how JSGME.exe works to install mods that can be reversed, you then also know how to properly install mods.
  19. My problem with GTX960 (or 7970) was - as Mustang mentioned - type of AA rendering (SS, MSAA). I use Nvidia Inspector and set AA to 16x, nothing more (highest AA without any sampling), and if need be (FSX with a 7970) textures to 'performance', my guess it's a driver issue and the VGA memory gets swamped.
  20. Don't think 1.5.4 has Deferred shading, that's only in 2.xx Nevada
  21. did all of that and just noticed, doesn't quite work 100% but almost, labels won't show (how weird is that)
  22. that's 'incompatibility' or bugs mine did the same with 4 screens, 'windowed', crash, not usable (define MFD output in your monitor setup, not as handsome) now, when I test with 2 screens (my 1080 is RMA), full screen vertical 1920x2160, works flawlessly you'll have to wait for an update that works on your config .. (1 screen 1080p should always work presumably)
  23. "set: DisableSnapViewsSaving = true Within this file: C:\Program Files\Eagle Dynamics\DCS World\Config\View\View.lua SnapViews.lua Gets automatically created by DCS in the C:\Users\[uSER]\Saved Games\DCS\Config\View Folder when you save a snap view."
×
×
  • Create New...