Jump to content

Slice313

Members
  • Posts

    184
  • Joined

  • Last visited

Posts posted by Slice313

  1. I though the issue was fixed but I started getting crashes back on second mission load. I repaired the game  (slow method) and deleted the FXO folder, but still crashes (less than before but sometimes crashes)

     

    Also, now, crash logs and dumps are never created.

     

    Pd: I was flying the Tomcat

    FAQ

    I have everything working but, I have one doubt, with the Tomcat:

     

    In my dedicated server with Easy comms OFF, using SRS and Vaicom, I can only transmit voice over SRS when I map the DCS controls "Mic Button UHF1 and UHF2 (SRS only -No menu)" over the Vaicom TX1 and TX2 (Same TX buttons mapped for SRS), that way everything works nicely, SRS and Vaicom. But the manual says it is not recommended to map DCS buttons overlapping the Viacom controls, I am so confused...

     

    I already enabled "Radio switch works as PTT" and the Vaicom multiplayer, SRS integration and SRS PTT mapping...

     

    Why do I need to map also the DCS Mic Buttons for everything to work together?

     

    thanks

     

    PD: SOLVED, SRS "Always allow SRS HOTKEYS" was OFF by default after the installation,  The VAICOM manual should include that info. All working good now!

  2. 35 minutes ago, draconus said:

    @Slice313 Whatever you try to do here is poor tactic, but let's continue.

    Fox1 - when properly launched and lost the lock - reverts to flood mode to look for any radar reflections. Pilot has to keep the target in the flood area by maneuvering the aircraft. Idk if you can Fox1 without radar lock and then turn it on later, only relying on the flood mode, which is pretty unreliable anyway, but it may well be what happened to you.

     

    On TCS lock:

     

     

    This pretty much solves all my doubts 🙌

     

    Thanks to @Lurker and @draconus for your help

     

  3. 1 hour ago, Lurker said:

     

    You can lock with just the TCS if you know where to look. (Or rather your RIO can). However you can't launch a FOX 1 with the radar off. That's not how it works. The TCS can be slaved to radar, I don't know if it can even work the other way around. 

    In any case, FOX1 launches on the TCS lock without a radar lock are a no-go. What you can do is get a slave TCS lock, then turn off the radar, sneak up on the enemy and then launch a Phoenix with the ACM cover up (hot-off the rail). Should do the trick. 

     

     

    Thanks for your answer 😃

     

    Regarding FOX 1, I understand what you are saying, but I already satisfactory launched with radar off and turned it on a few seconds later, missile got on path and still got the kill. I get what you are saying, TCS cannot feed any info to the AIM-7 and the TCS, if anything, would only be useful to calculate an approximate lead prior the missile launch. Mad dog Phoenixes should work about the same way (well much much better), thanks for the tip. 😍

     

    However I still cannot get the TCS to lock on anything with the radar off. The only way I get a TCS lock is when the TCS slaved to radar and I get a radar lock.

     

    If the acquisition is on auto, only putting the enemy on the piper and tracking dots should start the lock inst it? or there is anything else I am missing? In this case, the manuals are not helping me. 🤔

  4. Hello, I have been hitting the manual and Chuck's Guide but I still have trouble using purely the TCS to lock on an enemy.

     

    I turn on the TCS, acquisition mode AUTO, Slave Radar, put an aircraft in the middle of the tracking dots of the TCS but nothing happens. Although I have been successful locking with the radar (Slave TCS) and then turning off the radar (My TCS lock remains).

     

    What I really want to do is to slave the radar to the TCS, lock a target using the TCS with the radar off, FOX 1 to a target with a little bit of lead and finally turn on the radar to guide the missile on its last seconds. But for whatever reason I cannot lock using just the TCS.

     

    Anyone know how to?

     

     

    Much appreciated

  5. 14 hours ago, MrExplosion said:

     

    Not responding for years after years of people asking is their subtle way of telling us "No"... or rather a less friendly worded variant of No, given ignoring ones question is seen as rather rude by some people. 

     

    I think they wont release a skin template until the new external model is done.

  6. This inst a DCS bug per se, but a Nvidia drivers one. If you install the latest GeForce 466.47 drivers, you may notice a constant flicking in the game's menu and also in-game.

     

    I found the drivers responsible and anyone encountering this flickering bug should downgrade to 466.27 for now.

     

    Tested with a 2080S. I believe the bug might have been caused by some issue related to Gsync, but sadly I didn't think of testing it before downgrading drivers.

  7. I had lots of engine degrading problems just flying around for short periods of time (less than 30 minutes). I thought I was missing something but reading this post reassures my belief.

     

    I also experienced that the MW-50 inst increasing the performance of the plane, seems to be broken?

     

    -If I fly at sea level, leveled in straight line, with or without MW-50, I get the same speed, even MW-50 seems to worsen it by a tiny bit.

     

    I was wrong, not truth, without MW-50 I get 550 km/h, with MW50 600 km/h.

     

    If I dare to touch the radiator flaps, my oil temps rises beyond 130 and the engine is destroyed after 2 or 3 minutes, but that is just my fault I guess, I gotta read the manual regarding Oil temp management.

×
×
  • Create New...