Jump to content

escaner

Members
  • Posts

    758
  • Joined

  • Last visited

Everything posted by escaner

  1. I find that Snakeyes in CCIP always go long, contrary to the slicks in CCRP that are very accurate. Video: Always aiming at the first dark truck under the pipper. Tried throughout the speed envelope, at 500, 450, 400 and 360 KCAS. Track also attached. m2000-mk82hd-long.trk
  2. I don't have a crash log because my instance does not crash. AFAIK, he sent the automatic crash report.
  3. Anyone having this problem? I have modified Cage the Bear mission #2 for multiplayer, selecting the plane as Client instead of Player and launch it with my computer as MP server. Then I join as RIO and my friend selects Pilot. When I give an order to our F-14 wingman, my friend's DCS crashes. When he gives an order to our wingman, there are no crashes. We are running the open beta version. I saw a fix for something similar to this in a recent patch release, but it still happens to us.
  4. Video showing the problem: Mission attached Loadout: 8 x GBU-12 + TGP + 1 x AIM-120C + 2 x AIM-9X + 1 Fuel tank Steps to reproduce: 1. A/P - BALT 2. Select weapon 82LG 3. Select Master A/G Mode 4. Bomb MODE: MAN 5. Pickle 3 times to drop 3 bombs 6. Deselect 82LG 7. Deselect Master A/G Mode 8. JETT STATION SELECT: LI, RI, LO & RO 9. SELECT JETT - STORES 10. Press JETT -> DCS hangs F-18 jett crash.miz
  5. I would definitely use it to get rid of the ladder, which is misleading. Actually was trying it from time to time to see if it was finally implemented.
  6. Thanks for your thourough reply QuiGon OK. In this case, TWS Auto is supposed to automatically change the azimuth width and bars if necessary (e.g. several missiles on the way with aircraft separating one from the other) or should I still do it? I don't think it is that because actually there can be several flashing contacts at the same time in TWS. I wonder if it means that they have arrived to some range (maximum, optimal, etc.) or that the computer has a valid track to launch or something like that.
  7. Yesterday I tried flying RIO in the F-14 with a friend and had a few issues plus many doubts. I hope someone can help me. I was server for the session: 1. In TWS Manual, every time I fired a Phoenix it changed to TWS Auto. Is this normal? 2. In the previous scenario, if I changed back to TWS Manual and changed the azimuth from narrow to wide, the tracks disappeared (only did it once, didn't want to happen again). Anyone experiencing this too? This was happening to me some time ago changing range, or between TWS and RWS, but I though it was fixed. 3. The manual says: "The launch zone vectors are activated manually by the RIO or when time to maximum launch range is less than 60 seconds and replaces the normal track velocity vectors." How does the RIO manually activate the launch zone vectors? 4. What exactly means when the contacts flash in TWS? 5. When as RIO I select the TCS view, the pilot radar screen (TID) goes blank. Is this normal? 6. I could not hook my contacts (hafu on top), but I could hook datalinked contacts (bottom hafu). I would say that some time ago I could hook my own radar contacts and then STT with the radar mode button. This cannot be done anymore? 7. Is there a way to move the display to see more airspace behind my own aircraft in the TID, eg my position in the middle of the display? I can move it forward, but not backward with hook + HCU offset. 8. After some time, datalinked and radar contacts seem to appear at different positions, no longer correlated. This is INS drift? Can it be easily fixed? 9. Both times that I talked to our AI F-14 wingman, my pilot's DCS crashed. I think we were not even in the correct frequency, not sure if that matters. Anyone has experienced this? When this happened, my aircraft stopped in the air and I was dumped from it even when I entered the aircraft first. I hoped to pause and wait for him to reconnect, but obviously it was not possible. Thanks a lot!
  8. I have tried in flight alignment (IFA GPS) as per points 5 and 8 on this message: https://forums.eagle.ru/showpost.php?p=4458377&postcount=1 At first glance it looks like it works, with the advisory INS message disappearing, but then you can notice that the velocity vector behaves weird (e.g. it goes side to side with just a slight bank) and AUTO and CCIP cues are wrong. Track attached. PS: Initially reported it in that thread, but I am not getting any further feedback from Santi871 so I figured it would be better to report it here. f18-ins-ifa.zip
  9. Did you have the opportunity to check my track in the message linked below or should I post a new thread in the bugs section? https://forums.eagle.ru/showpost.php?p=4470555&postcount=44
  10. Attached a track, it is the Nevada Cold & Dark start instant mission. When IFA GPS alignment finishes, the ADV disappears. Slight banking moves the velocity vector around from side to side. I also select AUTO and then CCIP with same problems. ins-ifa.trk
  11. I have tried in flight alignment (IFA, points 5 and 8 on first message) and at first glance it looks like it works, with the advisory INS message disappearing, but then you can notice that the velocity vector behaves weird and AUTO and CCIP cues are wrong. See attachments
  12. These articles are very nice, I hope they eventually make it to the manual.
  13. Pilots are human and they not always make the best decisions especially under stress. There was an article at tbo.com where MRT Fox explained his experience. Unfortunately the site no longer exists, but I keep a printed copy within his chapter in my Debrief book. After the AWACS call, he says: "Suddenly it was very obvious who he was talking about, so I went into a quick lock mode and got an immediate lock on a MiG-21, nose onto me at 10 miles. We were closing on each other very fast. Inside of 10 miles, you always select Sidewinder. Now, if I had been completely sane and rational at the time, after having gotten the lock... I would have gone to the Sparrow and taken a nine-mile Sparrow shot on him." What I interpret is that as the bandit was about 10 NM out, he selected Sidewinder to go into ACM radar modes. For sure he was surprised, excited, nervous, and with low SA thinking on their ground attack mission until they understood the AWACS call. With the high closure speed, probably the MiG was within Sidewinder range before he could even think of using a Sparrow instead. If missile misses or fails, you will see that pilots try to switch to another type when available and it is within launch parameters too. Look for "Cherry" Pitts kill (F-15C vs MiG-25) where he shot an AIM-9 (decoyed), then AIM-7 (missed), then AIM-9 (decoyed) and eventually another AIM-7 (hit) to the same aircraft in this order. Fox behaved just like Pitts: when he though that his AIM-9 was a dud, he just switched to AIM-7 and shot again.
  14. Thank you for your prompt replies guys. I guess I will try to program a few of those commands in Voice Attack, but I really would expect for him to do that by himself. About the dropping of contacts, I don't think he was going to RWS. My thought at the moment was that he was switching from TWS wide (2 bars?) and TWS narrow (4 bars?) and back. I was too lazy to tell him to change range.
  15. Yesterday I gave him another chance, but I cannot understand what he is doing. In a head on TWS engagement, the guy keeps changing modes between wide and narrow, dropping the tracks every single time, even with AIM-54s launched towards them. When I try to crank, he will not change azimuth to keep the targets illuminated, and when they or I change altitude, obviously he will not move the antenna in elevation to follow them. I keep reading comments saying that Jester is great, but I cannot get him to do his job. What am I supposed to do in these situations? Thanks
  16. Thank you, Kaba Sent from my Redmi Note 4 using Tapatalk
  17. I see that there are three versions of the Cage the Bear campaign in the sim. How does the standard one differ from the "hot start" and the "cold start" ones? Thanks
  18. Definitely the show of force had no effect at all for me in both tries. I did several passes before and after they start shooting. Sent from my MI PAD 2 using Tapatalk
  19. I have modified the levels in the texture file for the gauges (especially the altimeter drum digits) discarding some of the unused range in the whites. Quite easy to do and much more readable now with the increased contrast.
  20. Hi BD. I just did the mission again and this time it worked. The Blackhawk was also damaged but it never stopped the engines this time.
  21. Hello I had the same problem here, not sure whether it was a problem with a trigger or the Blackhawk was too badly damaged. I was told not to engage the troops and then to do a "show of force", so I did a low pass. But when the helicopter came in it was under heavy fire by them. Eventually I fired on the troops. The last message I got was that Charlie was captured, on the helicopter and to escort it, but it never started again.
  22. The head position was advanced a bit again in one of the patches. Sent from my Redmi Note 4 using Tapatalk
  23. I see that this was fixed in yesterday's patch. Step by step...
  24. Yes. I did it, moving the white point from 255 to 200 in the histogram and it is a nice improvement in daytime (about 25-30% of the histogram range is unused, but not sure whether the problem is this or low ambient illumination). I want to do it again with a stronger setting anyway. Look for a file named A-10C-2019-CPT-TXT.zip, they are in there. I had to install the Intel dds plugin for PS.
  25. I also find night illumination very lacking. These screenshots are with all backlight maxed out. The only correctly illuminated areas are the ones that didn't change: HUD, MFDs, clock, radio digital displays and counter-measures and CDU. The rest is too dim. Additionally the switch for the G-meter and compass illumination does nothing now. Those lights are bound to one of the other lighting controls. Is that a bug? I agree that the new head position has improved a lot, altough now I cannot see the whole HUD. Finally, in the daylight, the shadow areas are also quite hard to read. E.g. I am unable to see the trim reset and light test buttons as they are that dark.
×
×
  • Create New...