dsobbe

I ran through all four missions last night. I had to shut off the weather to keep the FPS at a functional level on my system. I avoided contact with enemies and landed at the destinations just to see how the settings (flight path and terrain) worked with the story. Very nice. Many challenging situations. Good story/tactical interconnections. Having several missions located in the same area allows the player to get familiar with locals and that helps situational awareness a lot. Going forward with the story. It would be nice to gradually move along the valley to maintain geographic relationships and introduce new settings. Nice work so far. I do have a general question for you, or anyone. I'm not familiar with the minimum weather criteria used by European military flight planners. It seems highly impractical and risky to conduct escort and low level mountain flights in near 0/0 (zero visibility/zero ceiling) weather conditions without radar and at least good charts. Granted, ABRIS and the radar altimeter are minimum necessities in the simulation. But, would these instruments alone meet the minimum real world military requirements to conduct these flights?

Perhaps you are right. Whenever I see posts where several people have the same problem, it indicates caution. Even though all of the particulars may be unknown at the time. After closely reviewing the 1.0.2 patch posts, I can see that there are actually less unknown failures than with most patches. And yes, many followup posts do indictate that the writer failed to follow instructions. Thanks for pointing that out. My apologies.

I have played the VG Demo under the 1.0.1 patch in Vista32 and everything works. I have no problem with VG. There seems to be a problem with the 1.0.2 patch on some installations or operating systems (??), preventing Black Shark from loading or running properly. I cannot tell from the posts whether that problem is related to all operating systems, just Vista or Win7. Can anyone clairfy that.

Congradulations! I guess. From what I 've read in this thread and the Patch 1.0.2 thread, it seems we have the classic Microsoft syndrome here. Vergeev Group only works correctly with Patch 1.0.2 and that patch has some very serious problems. In addition, there are apparently some problems with downloading and purchasing VG. I'm tired of being a lab rat for every software producer on the planet. So, although I would really like to purchase VG, I'll wait until both yourself "and" DCS sort this one out and get it right. Good luck.

Dusty, I'm into mission 4. So far I agree with Rhino4's comments. The .CMP file isn't working properly and the campaign started with the second mission. Mission One never ran. Also, the file names have no connection with the mission titles in the briefings, which becomes confusing when trying to reference a particular mission to its file. I edited each briefing title to include its file number for now. That made things clearer. The second and third missions have the same title and briefing. Two is correct. Three needs to be changed. Those are the big items as far as campaign operation. All in all I like the missions, there settings and the potential for a good story. When the briefings and background story are fleshed out I think this will be a very good campaign. Having a little experience writing my own missions I know how much effort it takes to crank something useful out of the mission editor. Nice work. Please finish this campaign. It's sorely needed. Additional info. All of the text in the "red" task box of each mission in the Mission Editor doesn't display in the campaign mission briefings. You need to place that text in the "blue" task box for it to display Also, you have several instances of text that should be in the Description Box mixed in with text in the Task Box. The Description box is for mission "background" info. The task box is for specific mission "instructions". The .cmp file isn't working correctly. You stated that it was to allow each mission to proceed one after the other. See the .cmp file in the Vergeev Group Demo: http://forums.eagle.ru/showthread.php?t=49490 to see how that is set up. Good luck.

If you could provide the mission goals in English it would be very helpful and appreciated. Thank you

Are there any English translations for the Descriptions and Mission Goals in the Operation Polonaise series. They are interesting missions that push the KA-50;s operating limits. But, I can only guess at what's supposed to be happening. Sometimes I'm right and sometimes I'm dead. Thanks

IgorMK, I just finished Georgian Havoc. Bravo! The campaign moved in a logical manner. All of its elements were varied and challenging, which maintained freshness and interest from one mission to the next. Aside from the few minor weather and enemy strength issues already mentioned on this thread I think you did a great job, especially considering the short amount of time you had to produce it. I hope you'll keep writing campaigns in this style. Thanks.

There have been many posts on this forum about the difficulties of flying missions in fog and bad weather. Reduced visibility and night flying are really the world of instrument flight. It requires a lot of knowledge and training to be proficient at it. But, one concept that will help anyone at any skill level in any flight situation is "prioritization". Simply put, you just need to Aviate, Navigate and Communicate. "In that order". First, Aviate: Fly the aircraft. Keep it under control. If you loose control the other two points don't mean anything. Second, Navigate: Aim the aircraft where you want it to go, both horizontally and vertically. Fighting a military aircraft would also generally come under this heading. Third, Communicate: Send and receive instructions, information and orders. But, only when the first two points are under control and you have time. When you loose control of one of those three points you have to simplify the situation until you can sort things out. Aviate, Navigate and Communicate will take the pressure off and give you a method to help you stay out of the bushes. :thumbup:

Thanks for the warning on the 1.02 Patch. I've found some use for the wingman's habit of running into the enemies muzzles. He can be used as a distraction. I let him run about halfway to the assigned target and then recall him. After he's on the way back I order him to engage the same target again. While the bad guys are shooting at my AI yoyo I sneak in and kill someone. Quite often I never get noticed. But, then there are always those other times when I get the paint scratched by a sam.

IgorMK, After flying Georgian Havoc V1.0 "Secret Mission" ATO.S4.1 twice (and being shot down) I no longer get the comms call from Voskhod after takeoff with the the last known position of the target ship when I replay that mission. Also, I no longer get the call from the carrier that I am in site and can land. All other comms calls seem to be OK. Looking forward to version 1.1.

Is Georgian Havoc v1.1 (corrected version) available? If so, where? Thanks

I accept your explanation of how the ABRIS and PVI work. But, in other authors missions I observe that the waypoint number in the ABRIS displayed route, PVI and heading bugs in the HUD and HSI all agree. Maybe I'm just not seeing it correctly. Thanks

i have had locked targets blow up from previous hits after a second missile was launched. I then break the lock, move the shkval to another target and lock it. The second missile then hits the second target. You have to be fairly quick to do it, though. I have also routinely put the shkval on a target and commanded "Attack my target" without locking it. It works both ways. You can unlock the target, or move the Shkavl off of it, immediately after giving the command and your wingman will usually drop his vodka and go after it.

Thanks for the followup. Having done some beta testing for a software company working on aircraft structural layout software I appreciate how a small code change or correction can have a domino effect on development time. There may never be a perfect scoring method. But, at least its good to know that it is a known issue and being worked on by better minds than my own.

=FG=Schtuzer I may be wrong but, it appears that in the demo the waypoints selected on the PVI don't match the heading bug on the HSI. The heading bug incorrectly points to the prior waypoint. For example, if I select waypoint 2 on the PVI the heading bug will point to waypoint 1. So, if I want to fly TO waypoint 2, I must select waypoint 1. Then, the heading bug will point to waypoint 2. The "target points" in the PVI are correct and do match up with the heading bug in the HSI, which correctly points TO the target. These indications appear in all three demo missions. I staggered around the countryside in the fog for awhile before figuring that out in the first mission. Without the moving map plot line in the ABRIS and the DME as cross checks I might have flown off the edge of the earth.

I am a native American English speaker. So, I'll toss my opinion in on the translations. I had no problems with grammar or the communication of information. Some terms like "tug", used in the demo's first mission, were unusual. But, fairly easy to figure out. Most often, differences in grammar, style and terms, along with an accent, add flavor and a sense of presence to Black Shark. And to those who worry about their mastery of English, or lack of it, remember what the actor Ricardo Montlbond once said, "Whenever you are speaking with someone with an accent you are speaking with someone who knows one more language than yourself". Well said in my book. In the demo I noticed that if I failed a mission I had to repeat the previous mission to continue. That is the same format used in the original Georgian Oil Wars Campaign. It often resulted in seemingly endless former mission repeating, which gets stale real fast. I would prefer it if you used the format of the Georgian Havoc Campaign, where only the failed mission repeats until successful. That, to me, seems less punishing. Although, it would be great if someone came up with an even better failed mission campaign procedure than either of those. That's just my opinion. The demo missions and their envirnments are outstanding and I look forward to the campaign. Thank you for your efforts.

Tigerrrrr, In Search and Destroy my wingman recon'ed to the bend in the valley and attached the convoy before being shot down. By the time I got there the convoy was not in sight. Several minutes later I received a message that the convoy had reached it's destination. I was waiting in the valley for the convoy to round the bend the whole time and it never appeared. Is there another route that it could have taken? Very nice missions with tactically challenging terrain. Well done.

I stand corrected. They were flying taradacdyls when I was in the military.

Whatever happened to the "cockpit"? If it's the "flight compartment" why isn't there a placard on the outside of the "Flight Compartment Igress Device" (door) that reads, "Flight Operations, Navigation and Systems Holistic Management Control Center Ingress"? Hmm... Probably need a wider door. :doh:

Thanks guys. Missed that one int the manual. "If all else fails read the instructions. Again".

I've noticed that in some missions both the overhead hover and altitude hold indicator lights illuminate when hover is engaged. In other missions one or the other light will illuminate, but not both. Still, both hover and altitude hold do function. Anyone else notice that behavior? I just charge it off to a bad bulb. It actually adds to realism. Panel and indicator lights do occasionally fail, either due to vibration or burnout. Usually, just short of the marker at night in bad weather.

Just curious. Where is everyone reading the FPS. I'm reading between 12 and 16 FPS on the BS [Ctrl]+[break] counter. I'm using a lower end graphic card. To me, those frame rates are very usable and smooth unless there is smoke on screen. Then things slow down a bit. The large differential between what I'm seeing and what others report here make me wonder if they are getting FPS readings somewhere else. Thanks

It would be intuitively obvious to even the most casual of observers. Except me. Thanks again, Frederf.

Thanks Frederf, That makes sense. I'll give it a try. But I'm still confused by a part of the instruction. " Note that you should indicate N/S or E/W prior to entering the coordinate." How do I do that?