Jump to content

colo

Members
  • Posts

    369
  • Joined

  • Last visited

Everything posted by colo

  1. Direct JDAM hits if entering precision GPS LAT/LON coordinates
  2. It works fine, if enter PP1-PP4 at once, and then just select AG and ripple JDAM one by one while selecting PP1-PP4 (so i don't need to select QTY at all) Video (you can turn on captions for more info)
  3. Hi, new version 2.1 is out: - added F-18 Hornet JDAM auto inserting coordinates from map for JDAM bombs on MDIs/AMPCD (manual pages 5-6) - added possibility to specify map coordinates in config.txt file (see page 5) - improved auto waypoint entering for F-18 (now on any MDIs/AMPCD) - improved reliability of switching instruments rotation (slower but more reliable) - improved reliability of AC switching (slower but more reliable) - fix - auto waypoint not working in Nevada map - fix - adding of waypoint not working on specific condition - fix - not able to see Harrier MPCDs (buttons remapped - on desktop you must push "Add keybindings..." to remap buttons) - fix - not able to switch to viggen - fix - not showing name of the instrument after switching from/to UFC - fix - sending of kneepad pages blocks server status window - fix - A-10C CDU position shifted 10 pixels to left on screen (this is A10C module bug) - corrected by template Here is video showing using aInstruments for entering coords for 4 JDAMs (you can turn on captions for info)
  4. Not possible to enter PP JDAM coordinates with elevation zero Hi, not sure if reported but it is not possible to enter coordinates with elevation 0 meters via UFC, PP stay crossed.
  5. Hi, sorry for late answer, Thank you for permission, I will implement maps and I will credit you in App and also on my website. colo
  6. Are they planning to release NHL F18 and NFL F18 this year ?
  7. I think that the problem with impatience is with the stable vs beta: - in stable, of course, stability is priority - but in beta, who cares if JDAM flight profile isn't optimal near maximum range, it is beta version and can have some bugs, and can be merged to stable when it is ready
  8. Hi sorry for inconveniences please note that while dragging instruments to monitor they cannot touch each other - if yes, they return back Please send me your monitors geometry - resolution and placement (left/right or top/bottom) to appsupport@lumatek.sk or here, and I will send you description how to fill resolutions. regards, colo
  9. Hi, new version 2.0 is out - as always, download server part from lumatek.sk website and client part from Google play Changelog: - added Hornet and Harrier UFC - added playscreen area config to desktop app - improved keybinding warning messages - improved picture quality for CDU and UFCs instruments - fixed wrong instruments swiping on hornet - fixed instrument export warning messages - fixed maximum CDU height in GUI config - fixed wrong labels placement in GUI config Please note that if you want to use Hornet and Harrier UFC you must re-run aInstruments in admin mode and: - push button "Export instruments..." to UFCs be visible on monitor(it take the same place as A-10 CDU) - push button "Add keybindings..." to insert new UFCs keymappings into DCSworld More info on manual pages 6,12 and 13. As the code has bloated and more instruments and functions become available, the next version 2.1 will be focused on code tuning and bugfixing. Thanx colo
  10. Hi, working hard to release 2.0 today / tommorrow 1. yes, you will be able to rotate UFC instrument 2. next version 2.1 will be focused on improving current functions and bugfix
  11. Hi, to the end of week, new version of aInstruments will be released with Hornet and Harrier UFC instruments.
  12. If you have dynamic DHCP IP address on your android device, then you must close android app (really close not just minimize) and then start aInstruments server again. aInstrumenst server sends discovery packets, which android device catches. If you have static IP address on Android device then, after closing and restarting aInstruments server, client should connect to server automatically.
  13. Hello, sorry for the delay, I don't receive notice from this forum about new article in this thread as usually.. Android device doesn't look for specific coordinates - it just receives picture from aInstruments server(desktop) part. So to adjust transferred picture coordinates, just set up X,Y, width, height coordinates in AMPCD fields on server(desktop) app and click "Save instruments position..." If you have any troubles with setup, please just send me description of your monitor(s) setup and debug.txt file to appsupport@lumatek.sk and I will send you preconfigured config file. Regards, colo
  14. Hello PB0_CEF, sorry for inconveniences. I have checked your transactions - 1st payed at 6:11 PM - this one was successful 2nd payed at 6:17 PM - this one was declined Please note that payment is fully managed by Google Play store, I have no influence on payment realization, i just see if it was successful. Please try to restart your phone/tablet and try run app again. You can refund app anytime within 2 hours time window. If you have any difficulties to run app later, I can refund your transaction anytime, please just let me know. Thank you ! Regards, colo
  15. Hi, new version 1.9 is out (can take some time to be visible on Google Play): - added rotation of single instruments top/left/right/down - tuned visual area of all instruments - fixed hornet AMPCD logic - fixed hornet AMPCD buttons - fixed non-working buttons after returning from CDU/Abris/ViggenNav Please see manual page 4 for more info. colo
  16. Hi, here are some notes regarding aInstruments: Admin mode should be used only if changing configuration of DCS World: 1. when you change instruments coordinates or monitor(s) configuration 2. when you need to export instruments (i.e. when you don't see instrument on monitor) After change close aInstruments on desktop and run aInstruments in normal mode. Admin mode is not intended as play mode. If you connect tablet(s) with desktop automatically: 1. make sure that desktop app and tablet app are closed (really closed not just minimized) 2. run app on tablet(s) 3. run desktop app If you connect manually - then it is reversed ! 1. make sure that desktop app and tablet app are closed (really closed not just minimized) 2. run desktop app 3. run app on tablet(s) 4. click from autodiscover to manual button on desktop fill IP address(es) of tablet(s) and click "Set IP"
  17. Thanx for feedback, - please can you send me debug.txt and error.txt file to appsupport@lumatek.sk ? I will try to fix it.
  18. I will look if it is possible to export Mig-21 radar screen from DCS World, and if yes, I will add it to aInstruments
  19. Hello, glad to hear that it works for you, thank you for your purchase and support ! Still working on improvements and fixes. Regards, colo
  20. Hello, thank you for feedback Currently I am implementing single instrument rotation with another method so I will test it also as alternative rotation method for dual mode which should works also on older tablets
  21. So if I understood it right - the problem appears only in dual mode ? Please can you send me screenshot to appsupport@lumatek.sk Thank you for feedback
  22. Hello it seems that you not copy config.txt from older version to new version on desktop - so coordinates of instruments doesn't match.
  23. Probably delivery alt below 150 ft is unrealistic From the book US Marine Corps F-4 Phantom II Units of the Vietnam War (what is interesting here is also that rear fuse on snakeye is mentioned):
  24. The break-x is visible because I was in dive It dissapears if FPM is above 0 degrees even in low altitude about 200 feets - it is visible on 10th second in the last video
×
×
  • Create New...