Jump to content

LordOrion

Members
  • Posts

    1608
  • Joined

  • Last visited

Everything posted by LordOrion

  1. Actually I don't think my problem is a bug in the campaing: I saw similar issues using JDAMs o JSOWs, which usually are due to wrong target point altitude, but I checked the mission in the editor and (surprise!), user-points altitude is not editable: per default they use the position elevation, which obviously make sense. So, either I messed up something in weapon configuration or might be a bug in LS-6... Heck no! I'm playing this campaign to practice with the Jeff and now I'm curious to understand what went wrong. I've already created a simple training mission in the NTTR and this evening I will practice with the LS-6 untill I'have sorted out the problem. Plan B might be to change the weapon payload with LGB-s and try my luck with the SAM, but no way I'll leave those nuke to soviets ok!
  2. I had a problem with mission 9: I launched both the LS-6 in PP mode on PP1 pont (channel 36), leaving all other parameters (except fuzing) to default but both weapons "gone long" and missed the targert... What went wrong?
  3. @JonathanRL I confirm that the SA-3 now locks the player and hence can be engaged with LD-10 is ACT or SP modes. Thank you! However, I found (and fixed) another problem: Eager to play mission 7 tomorrow
  4. Thanks! Actually, your Desert Thunder is the next on my play list.
  5. Nice campaign so far (I'm at mission 6 now), pity there are not too much other campaigns for the Jeff. BTW, @JonathanRLthere is a problem with mission 5:
  6. Non so che dirti, magari fai un giro nel thread dell'hornet in inglese e guarda se c'è qualche post a riguardo. Inviato dal mio iPad utilizzando Tapatalk Pro
  7. Indubbiamente molto utile.
  8. Usually global settings have the priority, however, mission authors can choose to force a setting from the editor (i.e. he can force labels on). Try turn off labels in global settings and see if they are off in the campaign. if they don't, then the author has forced them.
  9. For an user-made campaign you can manually modify a specific mission and change the settings status in the mission editor. Paid campaing are encrypted, so you can't edit them.
  10. Per la parte teorica ti consiglio le Chuck's Guide (se te la cavi con l'inglese), qui trovi quella dell'Hornet: https://www.mudspike.com/chucks-guides-dcs-f-a-18c-hornet/ e qui tutte le altre: https://www.mudspike.com/chucks-guides-dcs/ Puo' sembrare un malloppone di n-mila pagine, ma usa un approccio "passo passo" per spiegare tutto quello che ti serve sapere per usare l'Hornet ed e' molto piu' chiara ed immediata del manuale vero e proprio. Io le uso come primo approccio ad un modulo, per assimilare i concetti base e iniziare subito a fare pratica (mentre mi studio il manuale ufficiale con la dovuta calma) e successivamente come una sorta di check-list da portarmi in volo (virtuale) sul tablet.
  11. 1) Cambia veramente poco, semmai il vero fattore di decisione dovrebbe essere la capacita' del disco: DCSW richiede un botto di spazio se inizi ad installare moduli e mappe, metterlo sullo stesso disco dove installi il SO potrebbe alla lunga creare problemi di spazio. 2) No, ma ti consiglio di mettere il file di paging sul disco M2 o ancora meglio, su un terzo disco M2 per velocizzarne l'accesso.
  12. +1 Decisamente meglio usare l'interfaccia del gioco per configurare il joystick.
  13. Or maybe the manual... Just to start the theoretical training
  14. Cool story, but it It looks like a 80s cheap action movie...
      • 2
      • Like
  15. You can find some in the Caucasus. Dunno the actual position but they are there.
  16. This is exactly my same doubt, I can be enough accurate with CCRP is the target is moving!
  17. Ok, make sense, I will give it a try. Ok, but how to deal with moving targets with CCRP?
  18. AI "cheats" at all levels, not only at Ace. It has an almost perfect SA and it is not subject to the same physics laws as human players.
  19. I'm trying to deliver some CBU-97 in CCIP mode but looks like the plane cannot compute the fire solution and the PBIL line never become solid. Since the procedure works fine with low drag bombs I suspect something wrong on my side. Any clue?
  20. <same ot as above> Vivo a Massa MA sono NATO a Carrara, (cosa non si fa per amore)! Non girare il dito nella piaga per favore </same ot as above>
  21. I've checked the generated mission in the editor but I didn't see any enroute task assigned, this is the reason why I was asking.... Deh! Anche se, ad onor del vero, essendo di Carrara sono Toscano solo per una questione puramente geografica I'm keeping just one package only with a player assigned slot. AFAIK I'm not using Combined Arms in Liberation.
  22. Nice question, and the answer is: dunno! I've double checked the menu' but did't find any setting related to the ground uints stance. I think I will RTFM then (I should altrready have done it before ) EDIT: Nevermid, I found it, and it was set to defensive. I've changed it to aggressive. Ok, I will disable culling then. Same for me Frame rate dorps to 20-24, while on the ground but the rise to 50-60 when in flight. I'm not an expert of the Editor, but AFAIK, it it a good pratice to create an enroute task on the target waypoint ordering to engage, this seems to make the AI more keen to obey, probably cause they know what they should try to hit. I agree, but I think this might be caused by a problem on Ramat David taxyway data: IMHO the limits where the planes should stop are not set correctly so AI planes does that mess (I saw the problem again today). I've opened a thread in the Syria map bug sub-forum explaining the problem, maybe I can get the Ugra media Attention. Thank you again for your hel Gianky.
  23. Nice charts! Do you have the same for NTTR and Caucasus too?
  24. Hi Ugra, I've seen this problem playing DCS Liberation battle for golan heights campaing: In my last sortie, one of the AI controlled F-16 of the ATO, which was taxiing on the G taxiway, stopped straight in the middle of the crossing with the runway 09-27 ( the one between G and K segments, see diagram below) . That leads to a collision with a couple of F-15 which where taking off (probably the reason why the Viper stopped). It should have stopped before attempting to cross the runway, can you please double check?
×
×
  • Create New...