Jump to content

Nealius

Members
  • Posts

    8608
  • Joined

  • Last visited

  • Days Won

    2

4 Followers

About Nealius

  • Birthday 01/02/1988

Personal Information

  • Flight Simulators
    DCS 2.7
  • Location
    Tokyo
  • Interests
    Jets and airsoft
  • Occupation
    Foreign Language Instructor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Incorrect. The issue is that in this situation it should be displaying the livery named "default" yet it does not. Correct behavior can be seen with the F-16, where the "default" livery is chosen by DCS when the livery cannot be found on the local drive. This has been explained exhaustively throughout the thread.
  2. I was trying to narrow down why it's always my Marianas and PG missions that get hung up, and the only three points of commonality between them are a combination of supercarrier, static tugs/cranes/crew, F-14A client slots, and F-14A statics on the deck. In all my other missions that are unaffected, I have F-14Bs instead of As on the supercarrier.
  3. More testing: If I have a group of 3 client Tomcats and 6 or fewer open spawn points, only 2 of the client Tomcat slots are usable. It seems that in order to avoid this, you need greater than twice as many available spawn points as there are Tomcat slots. CORRECTION: Even with only two Tomcats and 7 open spawn points, only one Tomcat slot is usable. The other one, and it's totally random whether it's the #1 or #2 slot, gets delayed to start. THIS IS GAMEBREAKING FOR MULTIPLAYER. Round 2: 9!!!! open spawns and yet I'm only able to slot into a single Tomcat! This is getting rediculous.
  4. Not even barrel rolls or high altitude, AI will rock their wings at low altitude and low energy states, and AMRAAMs fired within No Escape Zone will fly right past them without fusing.
  5. That's a weird one. I have no hidden units, and "show hidden units" is unchecked, but still get the hang on two specific missions, one in Marianas and one in Persian Gulf.
  6. Strange, last few flights I've done the light never illuminated. I had all CBs in.
  7. I've been here for every release since the P-51D. My only criticism is when developers overpromise on delivery.
  8. Ordered Phantom shirt day 1, still not received in Japan. Typical shipping time is 10-12 days from anywhere in the world to here, even on the slowest forms of shipping.
  9. Still happening. Client track attached: https://we.tl/t-r3p0tryZgj I have five VF-154 Tomcat slots on the Supercarrier, with seven open spawn points on the deck. Jet 112 always gets delayed to start. In some sessions I'm only able to spawn into jet 100 and 111, with the remaining three Tomcat slots INOP because of this bug.
  10. I haven't had it happen in the Anton, but I have had it happen in the Spit a long time ago. One thing I noticed in the Anton is that the probe heat lamp on the left of the dash only ever illuminates when connected to ground power. I haven't tried an engine start with ground power on, but I wonder if that could activate the probe heat and serve as a workaround.
  11. That as well. When we first got the Forrestal there were no statics on it. At some point we got default statics in a patch.
  12. Literally at the end of his post: REQUEST Make the mules/forklifts visible on the mission editor view so users can avoid them when placing their own statics.
  13. This is the nighttime signal for runup. This question gets asked so many times here and in other communities I'm starting to wonder if it's been forgotten in the manuals.
×
×
  • Create New...