Jump to content

Speed_2

Members
  • Posts

    194
  • Joined

  • Last visited

Everything posted by Speed_2

  1. Nope, I think you just have to make an individual trigger for every unit. This mission editor desperately needs improvement, BTW. And how do you change the AND to an OR? When I need to do ORs, I have to just create a set of multiple triggers that all enable or disable a specific flag. Wouldn't be nice if we could directly edit a trigger file so we could just use something like Notepad to write triggers? Holy god, that would be so much better than this GUI nightmare. You could even create your "own" trigger actions and conditions, if you could be passed information such as unit locations (x any y) on the map. Like, at a certain time, pass the x and y coordinates of a tank to the trigger file, convert that to lat and long, and then pass that information into a text message that says "Enemy units are now at <XX XX.XX> North, <XX XX.XX> East!"
  2. Hey, what size do you need to make an image to make it fill the mulitplayer briefing screen without first alt-tabbing? You can put any size image in there, but there's a bug where it won't stretch it to fill the entire image pane until the game is alt-tabbed and remaximized. And yes, I've tried matching the image size to the native briefing image window size, doesn't work. HOWEVER, there must be a certain size you can make this image that causes it to fill the screen without having the minimize the program. How do I know? Because other people's multiplayer missions (like Dragon's) I have flown have full-sized briefing images without having the minimize. So what is that size?
  3. As far as the jettisoning weapons to get more g's of manuverability- You don't have to pull 9G turns most of the time to evade missiles... also, anti-radiation missiles are usually kinda light and streamlined, so not THAT heavy. Another problem with the AI doing SEAD is that they only will launch one missile at a target at a time. Even if you put two SEPARATE flights to hit the same target, they somehow still communicate with each other and will only launch one missile at a time. This means that over half the time (or course, this depends on the quality of the SAM), their one missile will just be shot down- over and over and over again, until the SEAD aircraft run out of missiles.
  4. If you have version 1.0.1a or b installed, how can you patch to 1.0.1c without uninstalling the game? I think I've got 1.0.1a or b installed- but I have never seen a way of checking what version of 1.0.1 I have installed. There exists no 1.0.1a/b to 1.0.1c patch, and the 1.0.1c patch says it must be installed over a 1.0 version of Black Shark... Do I have to use one of my deactivations and uninstall BS?
  5. I didn't think laser burnout was enough damage to get the ground crew to repair your chopper... I always go to a hover about 10m over the pad and then drop the collective to zero so that I make SURE I break something.
  6. There's some system that needs spooling up before you can use autohover. If you don't see your airspeed on the hud, then it's not safe to use autohover, and trying to do so will cause your autopilot channels to disable. It's really stupid, why not just disallow use of autohover?- but that's how it works in game. This kills many new pilots. To anyone who knows, what is that system, and how can I check to see if it's online yet without having to check to see if I am getting an airspeed on my HUD? Edit: Ah thanks, "Einstein" :) But any other indications anywhere else?
  7. Hmm... my Saitek software is version 6.6.6.9, and it also doesn't recongize RShift (I think it also has a problem with RAlt or RCntrl too). I just had to reassign RShift keystrokes to something else in the BS UI to get it to work.
  8. It is very common for someone it say "Yes I have the icing system on" when they don't. You must turn on FOUR anti-ice switches- two pitot anti-ices, rotor anti-ice AND engine anti-ice.
  9. I reversed my throttle so that when I pull back on it, it increases collective. I find it more realisitic!
  10. Grimes, The moderators do not seem to think that this is worthy of being a sticky. See my attempt to start a mission editor wishlist sticky back in October: http://forums.eagle.ru/showthread.php?t=45768
  11. Does anyone have a good objective/mission/message sound? I like the radio static that Dragon puts in his missions every time a message appears, unfortuantely, I do not have any sound anything like that, so I have no sound effects. Thanks for the comments, but I doubt this is really that more complex than others. Oh, and it's something like 50 armored vehicles you get attacked by. It can be won with just three people, but even if you lose the city, in the current version I didn't put in any consequences/penalties. If I made a penalty of not being able to rearm and refuel anymore from the city farp after you regain control of it, that would be simply annoying.
  12. Hey, I just got done (I think) with the first version of a fairly large and long mission I am calling The Battle of Zugdidi. Though it's got spots for 12 people, it can be completed by as few as three or four. I'd personally recommend five or six. I'd would be highly appreciative should any of you fly this that you report any bugs you might find! WARNING! due to the large number of units in this mission, some users with older computers will experience low frame rates at the beginning of the mission while the enemy is attacking. Here is the briefing: SITREP Ground: NATO has attacked our army in Georgia in an attempt to push us out of the country. Our last major stronghold in the Samegrelo region is Zugdidi. We have detected a major NATO armored attack coming from the south. Frontal aviation will be tasked with repelling the enemy attack and then providing close air support to friendly forces in an attempt to break out from Zugdidi and capture positions to the south. Enemy ground composition includes armored vehicles from the US army, armored vehicles from the remnants of Georgia’s army, and a scattering of air defense vehicles (mainly Rolands) belonging to the German army. Air: Currently, neither side enjoys much of an advantage. Our forces have deployed SA-10s and SA-11s that are preventing enemy air from operating over the battlefield. Likewise, the enemy has deployed Patriot, Hawk, Roland, and short range IR guided missiles to prevent us from supporting our ground troops using fixed-wing assets. Frontal aviation will be tasked with opening up the air war by approaching the Patriot SAM site in NOE flight and destroying it, allowing our Fixed-wing SEAD aircraft to get close enough to take out the Hawk and Roland sites. Once all long range radar guided SAMs are destroyed, we will launch CAP, SEAD patrol, CAS, and other strikes using fixed-wing aircraft. FARPs: Currently, we have two FARPs in operation: one located in the Zugdidi central park area, and the other located 16 km to the northwest, south of Gali. KA-50 aircraft groups 1 through 6 will be based out of Zugdidi, and groups 7 through 12 will be based at the northwest FARP. INTEL Army units: A major enemy offensive against our forces in Zugdidi is expected in the very near future. The enemy supply level is good, and their morale is high. The enemy has deployed defensively near major bridges and at opportune ambush locations. Total enemy strength in the area is estimated to be from 150-250 armored vehicles, and 50-100 AAA, SAM, artillery, and support vehicles. Air defenses: Patriot, Hawk, Roland, Stinger (Avenger, Linebacker and MANPAD), SA-9, SA-13, AAA, small arms Air threats: F-15C, F-16C, AH-64D, AH-1W, A-10A Air threats SHOULD be neutralized by our air defenses early; later, once enemy air defenses have been disabled, our fighter aircraft will assist in maintaining air superiority. However, the possibility of encountering enemy air threats remains. Enemy airbases: F-15Cs, F-16Cs, A-10As are operating out of Batumi. Enemy helicopters have been detected from time to time over the battlefield, mostly near Senaki. Our low altitude SAM coverage mostly keeps them from operating near Zugdidi. An enemy FARP remains unaccounted for, and needs to be disabled/destroyed if found. CAS Aircraft# 51 through 58 (Sorties 1 through 8) Task: Support friendly ground forces Loadout: 12xVikhrs 10xS-13 rockets Cannon 50% fuel Details: Between 30 and 60 armored vehicles, believed to be of the US army, have been detected approaching from the south. Frontal aviation will attempt to eliminate these attackers before they take Zugdidi, and if Zugdidi falls, will attempt eliminate all the occupying enemy forces. Once these attackers have been dealt with, our ground forces will wait till we have eliminated the long range radar guided SAMs and achieved air superiority over the battlefield, and then begin a frontal attack on enemy postions. Our army commanders want fixed-wing support overhead as well as rotary-wing assets before they feel confident enough to proceed with the attack. Warning! Until the two Hawk sites and Patriot site have been dealt with, the maximum safe altitude in the Zugdidi area is between 500 and 600 meters. A large hill to the south blocks low altitude LOS for the Patriot and Hawk sites over the Zugdidi area. GROUND ATTACK Aircraft# 59 and 60 (Sorties 9 and 10) Task: Attack enemy reserve forces Loadout: 12xVikhrs 10xS-13 rockets Cannon 100% fuel Details: The enemy is sure to try to launch a counter offensive some time after we advance. To delay this as much as possible, it is necessary to strike enemy armor units that are being held in reserve in the rear. This attack should be attempted towards the late stages of this mission after a significant portion of the enemy air defenses (including all Hawk and Patriot) have been eliminated. GROUND ATTACK/SEAD STRIKE Aircraft# 61 and 62 Task: Disable PATRIOT SAM site and destroy targets of opportunity in the rear Loadout: 12xVikhrs 10xS-13 rockets Cannon 100% fuel Details: The long range of the Patriot SAM is preventing our fixed-wing SEAD aircraft from getting close enough to it or the Hawk sites to destroy them with ARMs. The only way to take out the Patriot is a NOE approach using rotary-wing frontal aviation assets. Intel has identified a low altitude route that can be used to approach the Patriot control radar safely. In addition, a critical flaw in the enemy’s defense has been found: no short range defenses protecting the Patriot have been identified. The route to the Patriot control radar has been marked precisely in ABRIS with waypoints. Aircraft must follow these waypoints exactly or face additional risk of getting shot down. NOTE: Command has also asked us to destroy any enemy targets of opportunity along the route we are using. There is evidence of an enemy FARP somewhere behind enemy lines, and if found, it must be disabled. We cannot allow our tanks to be destroyed by AH-64s! EDIT: Added updated mission attachements. v1.1b is recommended over v1.1a unless everyone is running the fastest i7 processors and very good graphics cards. Battle of Zugdidi v1.1a.miz Battle of Zugdidi v1.1b.miz
  13. Yep, sounds like a trimmer problem. You can also go into /Eagle Dynamics/Ka-50/Scripts/Aircrafts/_Common and open FMOptions.lua, and adjust the Timmer Zone pitch, roll, and rudder to new, larger values to reduce the amount that you have to return the stick to center to regain control of the aircraft. I multiplied all default values by 4 and I am pretty happy now.
  14. DXDIAG attached! Wow, it has a lot of info in it! DxDiag.txt
  15. Just as in the thread title, the multiplayer briefing system doesn't work. I just got done slaving over a 14 page (mostly graphical) briefing for my mission, and for some reason, only the first page opens, horribly distorted. It works fine when I open the mission in single player. Is this just my computer or is this a general problem?
  16. About the only thing that is relavent in this case might be the DXDIAG, whatever that is. The game doesn't crash. It doesn't say it generated an error. This problem will not show up in a track. I will check out DXDIAG tomorrow, but if that is related to directX, it's probably worthless in analyzing this problem as well.
  17. I've had this bug for quite a while, and it's VERY annoying. After respawning back to a chopper in a multiplayer game, or watching a missile in external views, upon returning to the cockpit view DCS sometimes no longer responds to key commands. I can move my head around with track IR, I can move the joystick and watch the stick move in game, look out my cockpit and see action going on, I can even click on switches in the cockpit, but key commands no longer work, including keystrokes activated by buttons on my X52. I have to use control-alt-delete to close the game. Sometimes, unplugging my keyboard and plugging it back in restores the ability to enter keystrokes, but sometimes not. HELP! THIS IS INCREDIBLY ANNOYING WHILE HOSTING GAMES!
  18. Well, I tried to pull it on-topic, what about my question:
  19. Well, I just got done making a mission with 50 tanks that were attacking a Russian-defended town. The idea was to make a more fun, less static mission. However, about half the people are unable to play it, it gets so framey. DCS needs some improvements to help handle large numbers of units attacking each other. This may be part of why you see so few missions like this.
  20. I donno, I disagree. I find DCS Black Shark to be a fairly simple game, once you LEARN some things. I guess anything is simple once you understand and know it- well, ALMOST anything. So yea, once you have a certain knowledge base in DCS Black Shark, it DOES become a "just hop in the cockpit and go fly with my buddies" type game. Alot of the advanced knowledge on subjects such as Abris and ADF is not needed 99.99% of the time.
  21. Well, in my squad, we have people who enjoy training other folks, and we don't really expect too much reading... I find the manual very hard to digest at times, for two reasons: 1)It seems to be lacking on tactics and employment and generally, how to do things. 2) The pictures are still for a Russian cockpit! This makes things very slow and confusing when trying to learn switches, buttons, etc. That said, if you wanted to train with us, you'd have to join us. I don't think any squad out there will train you if you're not going to stick around and fly with them.
  22. I am having a hard time seeing how FC2.0 will NOT necessitate at least a small DCS patch. You cannot currently set a fixed wing aircraft that is flyable in LO: FC to be "client" in the DCS mission editor.
  23. Duke49, It may help to realize that some of the improvements being made in FC2.0 may carry over to DCS- such as the mission planning screen. Also, some people who are flying DCS will get a realism improvement while flying with pilots in FC2.0 because a human controlled aircraft overhead is much more realistic than an AI controlled fixed wing aircraft. Still, as a fellow study sim fan, I agree or partially agree with you on many of your points. But after waiting over 10 years for the next jet fighter study sim, I'm not going to begrudge ED for making FC2.0 and making me wait a few additional months. If they can make a profit from it, and they obviously think they can, that just improves the health of the company which in turn improves the likelihood we will see more advanced study sims from them, right? Just don't expect me to buy it or really care much about it.
  24. Well, just for the record, I also couldn't care less about FC2.0... I only fly study sims. However, I'm not going to begrudge ED for developing a product that alot of people want! I just hope they get back and start focusing on DCS only soon. Mission planner sounds like a nice improvement. How about a better mission debrief system as well? On a side note, this is the ED forums where FC and LOMAC have had a home for many years now. The vast majority of the people on this forum might be screaming for FC2.0, but don't see how you guys can claim that the majority of DCS: BS flyers want it. The population of this forum is LOMAC/FC biased. In fact, I'm hoping that the FC2.0 doesn't come for quite a long time because I'm afraid that all the missions we've spent so much time building will become incompatable with DCS/FC2.0. Does anyone know for sure or not if this will happen?
×
×
  • Create New...