Jump to content

Snail

Members
  • Posts

    131
  • Joined

  • Last visited

Everything posted by Snail

  1. I took the plunge and updated to 1.5.8 and 2.2. All modules are installed now. Thanks for helping me out!
  2. I have read som less good reviews of 1.5.8. and 2.2 How can I choose to upgrade to e.g. 1.5.7.11762?
  3. The planes also won't install in 1.5.7: same error message.
  4. I can't remember to have seen a picture of Viggen pilots having maps in their kneepads. It would be very much appreciated though if the pilot became available! :thumbup:
  5. Yes, those empty seats are spooky: like nobody is flying this plane.............
  6. Today I bought 3 modules (Normandy 1944, Spitfire mkIX and Mustang) and tried to install them from within the module manager. My current install is 1.5.7. The message I get is this: version 1.5.7.11476.394 is not available See attached log file. Any idea how to solve this? autoupdate_log.txt
  7. This is the part of my lua file (added lines are bold) --Navigation {combos = {{key = "N", reformers = {"LCtrl"}}}, down = 3001, cockpit_device_id = devices.NAVIGATION, value_down = 1.0, name = "Datapanel IN/UT Input / Output switch IN", category = "Navigation"}, {combos = {{key = "N", reformers = {"LShift"}}}, down = 3002, cockpit_device_id = devices.NAVIGATION, value_down = 1.0, name = "Datapanel IN/UTInput / Output Switch OUT (UT)", category = "Navigation"}, {down = 3008, up = 3008, cockpit_device_id = devices.NAVIGATION, value_down = 1.0, value_up = 0.0, name = "Navigationpanel Button L MÅL", category = "Navigation"}, {down = 3009, up = 3009, cockpit_device_id = devices.NAVIGATION, value_down = 1.0, value_up = 0.0, name = "Navigationpanel Button LS", category = "Navigation"}, {down = 3010, up = 3010, cockpit_device_id = devices.NAVIGATION, value_down = 1.0, value_up = 0.0, name = "Navigationpanel Waypoint BX", category = "Navigation"}, {down = 3011, cockpit_device_id = devices.NAVIGATION, value_down = 1.0, value_up = 0, name = "Navigationpanel Waypoint 1", category = "Navigation"}, {down = 3012, cockpit_device_id = devices.NAVIGATION, value_down = 1.0, value_up = 0, name = "Navigationpanel Waypoint 2", category = "Navigation"}, {down = 3013, cockpit_device_id = devices.NAVIGATION, value_down = 1.0, value_up = 0, name = "Navigationpanel Waypoint 3", category = "Navigation"},
  8. I've copied those lines to the default.lua in the AJS/joystick folder, in the navigation part of the file, just above the 'down = 3011 etc' line, but they don't show up in the controls section. Any additional action needed?
  9. There are only three devices listed there: joystick, keyboard and mouse. No TM MFD's and no Logitech G13... Though they do show up in the controls section ingame... Any ideas?
  10. While setting up my HOTAS etc. I want to use a TM MFD bezel for the navigation panel. In the controls section ingame the 9 waypoint buttons are present to be assigned, but the BXL, L/MAL and LS/SKU buttons seem to be missing. Is there any way to assign them?
  11. Yes please? I'm not really familiar with these things.
  12. If I understand it right, it's not possible with my setup. I have a main 1920 x 1080 screen and two small 800 x 600 monitors which I normally use for my BMS F-16 setup as MFD's.
  13. Just downloaded your files and copied them in the right directories. How do I get the radar image on my second screen? (if I choose 3 screens in setup, I get a very narrow window for DCS on my main screen).
  14. John, your tutorials are really appreciated! Thank you very much for your efforts!
  15. Yes, it was more simple than it seemed. The instructions in the SendOwl email were pointing in the wrong direction. Got it running now.
  16. Yes, I do have the open beta installed at my side.
  17. It may be my bad, but I haven't been able to download the Viggen yet. Yesterday I finally got my email from Heatblur/sendowl with a download link and serial number, after pre-purchasing on december 23... Great, I thought, finally I can fly this beauty. This morning I had the time for an install and a first glance. So I clicked the download link in the email which got me to a page where I a download button appeared (to be used 3 times max) and the license code was presented. Looked good. So I clicked the download button, which took me to the general DCS World download page, this one: https://www.digitalcombatsimulator.com/en/downloads/world/ No Viggen to be seen there. I tried it a second time, now logged in (maybe that was my fault). No difference and no Viggen. So I spent 2 out of 3 download attempts which only got me nowhere. Getting a bit frustrated to say the least. Edit: my return email to sendowl lead to nothing, their reply says I should be contacting heatblur/leatherneck...
  18. I have successfully sent an email to get a download link. Now successfully waiting for a response...
  19. These throttle clicks etc. sound exactly as I remember them when I was in the Aviodrome Viggen cockpit. Great job!
  20. Nothing in the spam folder either. PM sent.
  21. I have pre-purchased it on day 1, but didn't get an email for download yet (also checked the spam folder).
  22. I got the 1.5 Early Access by the link above, but it installed 1.5.5.60565 again. How do I get 1.5.6?
  23. Very nicely done! When all five are done, you could combine them to one movie for whoever is interested in the Viggen.
  24. And above that: the SF is a photoreconnaissance aircraft. For proper gameplay, it would have to fly over the target area first, take 'pictures', fly back, let the pictures be developed whereafter the actual missionplanning can begin. I don't see that happen in multiplayer settings, maybe in singleplayer for those few(?) who like to extend their missionbuilding that way. Having said that, the SF37 would be nice as an AI addition, for immersion purposes. It only takes a reshape of the nose section and some extra pods and skins.
×
×
  • Create New...