Jump to content

=36=Witcher

Members
 View Profile  See their activity

  • Posts

    429

  • Joined

  • Last visited

 Content Type 

Everything posted by =36=Witcher

  1. =36=Witcher
    Yes, something must have gone wrong with the LOD definitions.
  2. =36=Witcher
    Penso che la scarico subito
  3. =36=Witcher
    When in List->DLINK->Page 2, using the dobber I can select the datalink callsign number and then callsign letters; antway, using the ICP up/down only has effect on the first letter (which is highlighted) but not the second one. Another dobber down moves the cursor to the Flight Lead line, so there seems to be no way to change the second letter.
  4. =36=Witcher
    No, not possible.
  5. =36=Witcher
    I don't have any issue with it in BuddySpike and DDCS. Do you have any other mods perhaps?
  6. =36=Witcher
    Dove vedi quest'opzione?
  7. =36=Witcher
    Potresti provare con programmi tipo LogMeIn Hamachi che creato delle "LAN Virtuali" che in teoria aggirano il problema. Ma si aggiunge comunque un po' di latenza, e tutti i partecipanti devono averlo installato e configurato correttamente.
  8. =36=Witcher
    Se hai Eolo, a meno che le cose non siano cambiate di recente, non hai un IP pubblico e quindi non sei raggiungibile dall'esterno
  9. =36=Witcher
    That would be perfectly fine, we have plenty of combinations to use after all. Perhaps just make it explicitly non-bindable with an error message of some sort, or even add a note in the manual... I mean, something to just notify the end user so that he doesn't spend hours trying to figure out like I did
  10. =36=Witcher
    You basically have two options: completely disable the numbers, or fix the skin in order to get the correct ones. Both methods involve editing the description.lua file, but removing them is kinda easier than having them displaying properly.
  11. =36=Witcher
    Yes, I have two languages set up, but LAlt+LShift+H seems to have no effect on it whatsoever. Anyway I removed the second language, so I only have one now (Italian), and the issue still persists.
  12. =36=Witcher
    Latest beta, no conflicts shown
  13. =36=Witcher
    Hello! I know it sounds weird but... it looks like LAlt+LShift+H does nothing in any module, despite being assignable from the options. What I mean is that I can assign LAlt+LShift+H to any control in any module, as any other binding, but then pressing those buttons does nothing when in cockpit. Is there a reason for this? Is this somehow a reserved binding not documented?
  14. =36=Witcher
    Già scaricate giorni fa, molto belle!
  15. =36=Witcher
    It happens since... I can't even remember. Also di IDN arrow turns accordingly.
  16. =36=Witcher
    Ok, so I totally misunderstood your first answer Thank you!
  17. =36=Witcher
    But then you don't you have an higher risk in incurring in stack limits? Perhaps I misinterpreted your answer?
  18. =36=Witcher
    No, I'm not experiencing any issue right now, but I wanted to play on the safer side. Yes, I'm talking about selecting them in the CTS main menu... Maybe a neat idea would be to implement some sort of "customizable sets" in the UI in order to have a quick selection of the profiles in different scenarios... but I don't know how many people would use that
  19. =36=Witcher
    Ok, I'll build my profile only for the modules I'm actually using then.
  20. =36=Witcher
    Hey, just a quick one: does the number of enabled profiles in CTS actually matter for the risk of hitting the stack limit? In other words, can I safely enable 10 modules even if I only use a couple of them most of the times?
  21. =36=Witcher
    As far as I know, water flashing on PG is due to some fog setting on the map. Unfortunately don't know exactly which one. You could try something moth the mission editor. Also happens to people without this mod and, don't know if it's related, also happens in at least another game, still with water surfaces. Out of curiosity, which GPU you have?
  22. =36=Witcher
    If you're going in a modern scenario, you're only going to lag behind. M2000C is a great dogfighter but only has 2xFox1 and 2xFox2. Against Fox3s it's going to be hard to score a kill unless you learn to sneak behind your enemy and only push when you're supposed to.
  23. =36=Witcher
    I'm afraid it's not... It's only that the previous log was wrong. Now he posted the correct one, and as far as I can see it's fine. @DaveMoi, honestly I have no clue. What if you open the Device Analyzer and try to press some of the buttons? Do you see some input registered from the Virtual Keyboard? Also, when you imported the profiles in DCS, did you also assigned BTN30, BTN31 and BTN32 as modifiers?
  24. =36=Witcher
    It's 2000-9, isn't it?
  25. =36=Witcher
    Ok, so the F-16 profile is applied. Howrver, all those "Device cannot be found" don't look good at all. Can you detect the devices in the main Target GUI? Is the Virtual Controller working per se in DCS?
×
×
  • Create New...