-
Posts
783 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Caldera
-
Jay, I don't think none of the above. There are no trees in the scenario. It is pretty clear to me that the AAR says: USA --> hit --> AGM-65D = AGM-65D USA --> kill --> AGM-65D = AGM-65D Then it says: RUS --> hit --> AGM-65D = APC-BTR-80 RUS --> kill --> AGM-65D = APC-BTR-80 It must have given credit for the missile kill to the Russian BTR-80. This only really gets me to wondering because the second missile was fired after a 7 second delay from the first. Yet they both hit at the same time. From my testing with the AGM-65L this was also (always) the case. I could not salvo those missiles, because they would always track the laser to the first target. And only the first target was ever destroyed and both would hit at the same time. I could never reposition the laser on the second target and get the second missile to hit it, I have not had the AGM-65D ever do that to me prior. I am wondering if something got changed. Other than that, these targets were really close to each other in convoy formation. So the explosion of the second missile hit the first missile a fraction before it hit the BTR and took it out. But that would mean, that the second missile after a 7 second firing delay actually hit first. This is what the AAR time sequence indicates. In the real world physics with missiles fired as I have describe above, will both hit at the same exact time? Caldera
-
Defi, I can't figure it out completely. If you notice the 1st missile targeted Ground-1-9 and the second missile targeted Ground-1-10. Which is what I recall doing. But, Ground-1-10 was the only vehicle that got hit (and destroyed). Logically, the first missile then had to have been taken out by the second. As the time stamps for both events occur at 19:07:31, indicating that everything happened at once. So it is like the second missile caught up to the first. The launch sequence was pretty fast. According to the AAR the second missile left the rails 7 seconds after the first. Never had that happen before. Caldera
-
Hey All, So take a look at the AAR below. Two AGM-65D's were shot in quick succession. The targets were really close to each other in convoy formation. It appears to me that the second Maverick took out the first one and a target (Ground-1-10). I have never seen that happen before so I am looking for feed back. Anyone else? Caldera
-
Thanks again Guys! I am a bit of a rooky at this, but once I figure out that I needed to EDIT vice OPEN I was able to edit the mission file. HAPPY HAPPY Caldera
-
Hey All, So... This seems to be a very discouraging problem (Let's call it a trap!) for the unknowing / unaware (Me!). I had built a number of SP missions based upon a repository of my squadron. My squadron administrators decided to change the repository and remove a mod (or two or more or so) that I had used in several missions. So, guess what? I have lost a few dozen hours building several missions that are now broke. I don't understand why the mission editor chokes and just refuses to load, but that is another topic. These are the Mods that once were: These are the mods that got pulled: Civil_OBjects NATO Ground Forces and units Does anyone know? How I can get the ME to load so that I can edit out these mods Know where I can find these two mods and download them myself Thanks in advance, Caldera
-
Asap, Thanks! Caldera
-
Hey All, What does the number represent to the right of the letters TN? Thanks in advance, Caldera
-
Hey All, The canopy open / close switch still does work for me, either by keyboard or controller. It only works by the use of right or left mouse clicks. After at least 2 patches, with ED knowing about it and BigNewy locking the original thread (because they know about it), it still no worky. Has some one came up with a "work around" to get the functionality of operating this switch by either keybind or controller? Thanks in advance, Caldera
-
Hey all, Frankly, I have no clue. What are these doodads for? Caldera
-
Thanks! I guess the solution was in front of me the whole time, but I couldn't wrap my brain around it. Caldera
-
Hey all, A new controller that has a three position switch. I can't figure out how to make the flaps work the way I would like. This is the three position switch in cockpit. This is the control options. Any way to directly place the switch in UP, MVR or DN? Thanks in advance, Caldera
-
cannot reproduce Left Mav Display much to dark
Caldera replied to JG11Preusse's topic in DCS: A-10C II Tank Killer
Hey Guys, The MAV screen seems beyond messed up... This is how it appears on my system. Caldera -
Hey All, After the update today the only way to raise or lower the canopy is with the clickable switch. Other controls don't work in Adjust Controls. Just me or anyone else? Caldera
-
Raptor, null A - I should read better B - I have not gotten to the point where I needed to use multiple channels C - Thanks Caldera
-
Hey All, The whole missile channel thing baffles me. I understand that a missile needs a frequency code for the seeker to lock on to. This is no help to me. When all it needs a the proper frequency setting, why does it need channels 1-4? What is the purpose? Caldera
-
Raptor, This is maybe the cause. Kharm, from the screenshot i see that both laser channels PRI and ALT are on A code. maybe that causes the issues? Yes, I noticed that too. I tried for some time to get ALT back to ALT B. in the list the B option was not present and the only choices were A C D D. Also the selected missile shows 'LS' which means (per manual): Missile standby, not set to a laser code. While others show 'AR' = Missile ready, seeker is in scanning for laser matching A code. And the active missile should be in 'AT' = Missile seeker in track mode, detecting laser matching A code. All the above, still a bit unexplainable. Did you fire as CP/G? Did you wait some seconds to check if the missile just needed time to "arm"? Yes I fired as the CP/G. I had just fired a missile less than 20 secs prior and destroyed a tank. Thanks, .Caldera
-
Hey all, I have no clue. I had just fired a Hellfire and destroyed a T-55, then they quit. The message was "MSL NOT RDY". To the best of my ability I did not mess with anything. Basically, one missile fired OK and the next wouldn't. Anyone take a stab at it? Caldera
-
Maybe... This screen shot shows what may have been confusing me. It was taken in the same general area as before. I have no idea why the radar altimeter quit. The VSI seemed to be working just fine. How is the VSI indication derived, from radar or barometric altitude? Caldera
-
Big, OK Thanks! I tried running the same mission this morning with the same results. On the third attempt to refuel / rearm the ground crew ignored me. I then shut down both engines and turned off DC power. The screen shot below is what things looked like after I did so. This is the second time I have noticed that the MPD's do not go black and at the same time the ground crew ignores me. Kind of ruined the mission I had been working so long on... Caldera
-
Floyd, Thanks! That all sounds pretty close to what I have noticed. Caldera
-
Big, It happened to me again this evening, On the third refuel / rearm attempt the ground crew just ignored me. To my knowledge I had taken no damage. If you mean by "exported displays" that I am running more than monitor, then yes I am running two monitors. I am running the main game one and one for the gunner MPD's. There are no mods being used. As to including a track file... I can only recommend that ED changes it maximum file size for *.trk files. Many times the mission track file is many times greater than 5mb. I think that it would benefit ED to do so as they are missing out on allot of good information that can not be passed along through this web site. Is there another way to pass large *.trk files to ED? Caldera
-
Scaley, Well hmm... I can understand why you are not seeing what I have seen. I took off straight from Batumi and headed west, just as I described above, and all seemed fine. However, running my training mission, which I have done many times, I do notice that it occurs. This mission forces me to land and rearm / refuel several times from a FARP located on the river east of the island that is just south of Batumi. Actually, the FARP is located in the river for the purpose of making spot landings more difficult for training. And... I have already noticed some goofiness in that process. In this mission I don't typically make it over to the coastal area until I have rearmed / refueled the 2nd time (16 Hellfires each time). All seems fine up that point until I fly near the coast or out over the Black See. I must do this to uncover some targets. When I fly back inland it seems to correct itself. At this point in the mission track file would be 30+ MB. I am not so sure this is a glitch or just some Caldera goofiness. I am attaching my SP mission file. It is really set-up to not use George AI as the gunner, but to let pilot George hover while the player is the gunner. The mission is designed to be pretty hard to learn and to be difficult. If you want to fly it be careful. There are no units actually hidden, but be sure to maneuver to a position with a view point where they can be spotted. I hope you enjoy the mission and thanks for your interest. Caldera 001 AH-64 CAUCASUS BUILD.miz
-
Hey All, Just wondering if any else noticed a phenomena with LMC and the TADS. The TADS just goes bonkers for a reason unknown to me. It will automatically and very rapidly slew to the top left corner of the HAD. Two conditions I notice that this can happen, both with LMC being used. Both occur at seemingly random times and only rarely. While stable on target with the Laser and LMC on --> As soon as I fire a Hellfire With the Laser on or off --> As soon as I turn on LMC Number 2 can occur 2-3 times consecutively before it will again act normally. I am looking for some feed back. Anyone notice this? Caldera
-
Same FARP and but a different day. I had already rearmed / refueled 3 times for the mission. On the 4th try the ground crew just ignored me. Caldera
-
Scaley, Thanks for the interest! I have built a training mission centered around Batumi, that is difficult and I have flown it many times. So yes, it has happened many times, but I just did not have the confidence to recognize it for a glitch or possible glitch until recently. I kept gaining allot of altitude for an unknown reason until I recognized what was occurring. I also noticed today that it is not entirely just over the water. There seems to be a margin along the coast line that I notice it occurs as well. For example, take off from Batumi and fly south to the river. Follow the river west out to the Black Sea and fly north along the coast or out into the sea. If you hold the VSI at zero you will gain altitude. To fly level the VSI will indicate a descent. Caldera