Jump to content

EagleTwoThree

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by EagleTwoThree

  1. So, update. I was able to finish the mission after about 15 tries. I could never kill the enemy fast enough, so our guys always died and mission failed. I tried, in order: mavs, guns. mavs, cbu 97 ccrp. mavs, bdu mk82 ccip. mavs, rockets, guns. The last was successful, mavs, rockets, guns. I used a mav on the BTR, then kept a close eye on what was going on with my nvg's. Since I did the mission so many times, I got to learn exactly where our guys were just using the nvg's. I did have to dodge the AAA, but as long as I didn't overfly the buildings to the north, I was ok. A combo of rockets and guns killed enough of the enemy to allow our guys to escape. I'll post a vid if anyone wants it. Eagle. *edit: FWIW, I ignored the "kill the trucks with weapons" part in order to focus on anything I saw shooting at our humvees.
  2. Hey Jim. I'm having the same issue. I've tried the mission 9 times now. As you said, hitting the BTR is no issue. After that, ignore what he says about the two trucks with the guns. Go back to WP 2, and watch for the vehicles leaving. The ones being chased are your guys, kill everyone else. I've been trying that using NVG's and the guns. I just can't kill all the enemies fast enough. Usually, our guys die before I can take enough of them out. A couple times, the AAA that's not in the brief, not on the mission planning map, or talked about by our guys on the ground, magically spawns and shoots me to the point I can't be effective (guns go out, cicu goes out, etc). I think this mission is timed badly is all. Currently, the way it works, you get about 30 sec to kill the guys chasing our guys, or it's mission failed. If you take the time to shoot at the magic AAA, you will still fail, because your guys will get killed so fast. You just have to take the AAA and hope you kill enough bad guys fast enough. I'm seriously thinking of finding out how to skip this mission. And it is ridiculous. I've finished the Georgian campaign and the Red flag campaign. At most, I had to repeat 3 or 4 missions, but only once or twice max. This mission? Silly. Good luck.
  3. Uhh...so I'm going to upgrade my vid card. No action req'd. Got it. But after that, I'm going to do a clean install of Win 10 (coming from Win 7). I'll then have to re-download Steam, re-download DCS etc. Do I have to de-activate in that case? *edit: the activation guide implies you have to deactivate/activate if you 'reinstall' your OS, so I guess if I'm doing a clean install of Win 10, I'll have to do the de-activate/activate thing.
  4. Thanks for posting your results. I was running with the one 32" at 1920 displaying the game and the second 19" only displaying the MFCD's and RWR. I just added 2 32" monitors and now have 4 (3 same size/res and 1 smaller). With the added monitors, I'm looking to find the best way to run DCS. Since I only have one 780 Ti, I've got all 4 plugged into it (DVI, DVI, HDMI, Display port). Given that, I can't use the 4th monitor with surround due to its different specs. So I'm forced to try DCS with surround off. It would be interesting if you could run (enabled/enabled?) with 3 monitors off one card with SLI disabled. It would show real world how much benefit you get from SLI in DCS. Eagle
  5. Archer, Good enough. You should check out multi monitor though, since good 1080p monitors are so cheap now (<$400). I never did multi until very recently, and I was worried about the seams too. From having tried it out now in several games, it's not much of an issue for me because I'm focused on the action. Eagle
  6. Apparently, you're not a hardware guy either. I'm not going to claim to be a "hardware guy" like you did, but what you essentially said was that you have no idea if the guy needs more than 2GB of video ram for DCS. You also said "2GB graphics memory is considered a minimum for video gaming today". Source that please (or did you POOYA that like the rest of what you said). Just because some higher range vid cards have 2GB, doesn't mean what you said is remotely true. And your statement "Water-cooling sets are not one bit more efficient than air cooling" couldn't be more wrong. The specific heat of water is something like 4x that of air at temps we care about. I think what you meant is that unless you are overclocking your cpu, you don't need to consider using water cooling. You could, but don't need it.
  7. If you're trying to move the MFCD's including the bezel (OSB's), then I think you're looking for Helios. Search on that and see if that's what you're trying to do.
  8. If all you're doing is exporting the MFCD's, you don't really need EMC (and it's broken for 1.2.8 anyway). There are many other posts on this, but basically make a copy of a lua in your monitor folder and change it with notepad++ to suit your set up. Then go in to DCS and enter your total screen real estate and select your new lua. My setup is similar to yours, so my lua is below ( you can delete the reference to the rwr, or leave it, it won't change anything). I also recommend you start here before asking a ton of questions if you run into trouble: http://forums.eagle.ru/showthread.php?t=89282
  9. So, I got it to work the third time around. I started from scratch with PeterP's instructions, and it worked. I'm not sure what I was doing wrong before.
  10. Ok. I'll go another round with it, and if I'm still stuck, I'll post back with more info/questions.
  11. *edit: The answer to the question is Yes, it works for 1.2.8. Hi all, I used PeterP's "Dummies Guide for Monitor setup" a few months ago and got multi-monitors set up with MFCD's exported (Thanks PeterP!!). I am messing with his guide found here http://forums.eagle.ru/showpost.php?p=1541311&postcount=68 mainly to add rwr export, and I'm having some trouble. Before I get ahead of myself, I wanted to ask a simple question. Is anyone running PeterP's guide from 1.2.5 (link above) for exporting views and having it work in 1.2.8? Thanks, Eagle P.S. I'm aware of EMC, and that it's not currently working unless you were using it from before 1.2.8. I saw a post by icemaker saying a new version is coming, but that was from mid May of this year. http://forums.eagle.ru/showpost.php?p=1541311&postcount=68
  12. While it appears that the OP didn't search the forums at all, referring him to a thread with 70 pages of changing information isn't as helpful as it once was. What works with 1.2.8 is no longer clear. The post by Peter P is from 1.2.5. As an example, I started playing in April this year, and while I was able to get the MFCD's to work when I started, but I have not been able to add the rwr recently. Changing to the code shown in PeterP's post made the MFCD's stop working. Anyway, what I'm saying is that as a community we've got a bit lazy with what the *current, 1.2.8* way is to run multi monitor and export views. If I knew what it was, I'd post it in a clean thread with 1.2.8 in the title. Eagle
  13. You have to have a Track IR or it will be like you smell funny or something and no one will like you. Just kidding of course, but it is extremely helpful as the others have said. If you get one, IMHO, don't bother with the "pro clip" thingy, as the clip is weak and prone to breaking (do some searching to see). I use the IR that comes with just the reflectors, and it works great. I also think the IR5 comes with a key for 60% off a module from ED, at least mine did. Eagle
  14. That may not work in low contrast situations. I just flew the 'sunset sierra' mission, which is at night, and the JTAC wanted me to kill a jeep with a mav. The contrast in the TGP was so poor, I could barely see the jeep. I slaved the mav to that point, but the mav (D) wouldn't lock. The contrast was better though, and I could clearly make out the jeep. Still, the mav would not lock. I tried force correlate, which I imagine would work, but it didn't. I think only G/K can do FC.
  15. That was my problem. The VHF radio sw (am/fm/man/pre) was in am or fm depending on if I wanted them to use am or fm. Apparently, that's not how it works. You have to have them set on man or pre. Once I set the lower (fm radio it turns out) sw to "man", JTAC responded. I also checked the upper (am radio it turns out) to contact Awacs, and that worked as well. So, anyone know what the function of "am" or "fm" does on the VHF radios?
  16. *edit 2: OK, I just reviewed a good comm video, and my problem may have been the am/fm/man/pre switch. I had them in am or fm based on which one I wanted, rather than having them in man. I'll try that and see. comm video:
  17. Right. I was using easy comms, and I saw in another thread that easy comms were broken with 1.2.8, which is why I asked. Funny part is, I had been setting up my radios not knowing that I didn't have to because I was using easy comms. I was using the "\" key to bring up comms and went from there. I flew last night and remapped VHF AM/FM and UHF to the arrow keys, since I'm using the Cougar F16 stick (using comm switch as china hat). When I used the UHF (mapped it to arrow key down), he did respond on that last flight and went at them. The problem is that I'm not sure if it's because I was using the arrow keys to select the radio (UHF in this case), or because he reported the AAA before I told him to go kill it. I'll have to run it again and tell him before he sees the AAA and see what happens. *edit: So, Easy Comms is not checked in options. Apparently, I was never using easy comms. Anyway, I set up both VHF radios to the JTAC freq 65.500, and had them on TR and FM. In the "Sunset Sierra" mission, I can't get JTAC to respond. I've tried flying at WP3 and contacting them, no reply. Tried killing arty, then going back to WP3 and contacting, no reply. My wingman will reply and attack the AAA when I tell him to *IF* he's already told me it's there. JTAC just doesn't reply. Ever. Can someone please try the "Sunset Sierra" mission and see if JTAC responds to them?
  18. Yeah, I had the SPI shared as indicated on the TAD. It was as we were approaching the area, so he wasn't damaged or anything. The SPI was a point on the ground at the area known to have some AAA. I told him to attack air defenses at my SPI. I got no response. Is it possible that if he has not "seen" the AAA, and I don't have it specifically marked, he would do nothing? Shouldn't he at least say "unable" or something?
  19. So are comms still broken? I can't my wingman to do anything. He likes to call out targets and tell me when he's getting shot at, but if I have a SPI designated, and go through the comms to tell him to attack air defence at my SPI with missiles, he ignores me. *edit. BTW, I'm playing the single missions. Not even to the campaign yet.
  20. I made a thread in the 'payment and activation' forum about this, but it seems like a money grab by Valve to force us to buy stuff from Steam. It just makes me want to use Steam less. So now since Valve is being pissy about letting us use keys from the ED store, it means I will have (choose) to install DCS world stand alone if I want any future modules. That's because I don't want TWO places to install stuff, and I don't want to have to remember "oops, keys from ED site won't work in Steam." Way to drive me away from Steam, Valve. Eagle
  21. So, being an outsider and not having all the information, I have to guess at why Valve doesn't feel like merging ED keys anymore. It's a money grab by Valve. They want to force people to buy the software via steam so they can get their cut. If you buy it on ED site, Valve gets nothing I suppose, and the added 'hassle' of having to merge keys from the ED site. How much money could we be talking about here? So much that Valve would care? Doesn't seem that way, but I'm not a bean counter at Valve. Eagle
  22. Yup. I'm already simming with A10C and Huey. Today, I picked up FC3, P51D, and Blackshark 2. I'd get the Mi-8, but it's just too damn ugly. Eagle
  23. I don't have an answer for you, but the premise is completely unrealistic. Instead, how about there is a local source jamming or spoofing GPS (very realistic, unfortunately), and until it is destroyed, GPS can't/shouldn't be used. then
×
×
  • Create New...