zamboni

Here is a post I did last night explaining some things in the mission The reason why JTAC says no tasking is available is because you hit the CP a little too early. Most likely (because of mission triggers) the convoys will only start to roll 20 minutes after mission startup (there is a small chance they roll earlier). If you call JTAC before they start to roll he will say "no tasking is available". I've had no problems getting the data triangle when I set my Groupd ID to 01 right before I contact JTAC. If he doesn't send data with ID at 01, check out and change the ID to what it give you when you take off, contack JTAC again to see if it works. If it still doesn't write down the coordinates and manually enter them in the CDU :). If all that fails, you still have plenty of time to try and find the columns. Even with the "updated missions" after they patch, they are still screwed up for the first devil's cross mission. A C-130 cant figure how to taxi and blocks the taxiway for the tornados that return. They block the runway and you cant get clearance from the tower when you want to return home. They also block the runway so CAS flights 2 and 3 are prevented from taking off. I tweaked the mission a bit last night and did the following: 1) Moved the C-130 to a place where he will taxi correctly and take off 2) Moved all the landings away from your airport because they won't properly taxi off of the runway 3) Edited the waypoint heights for CAS 1, 3 and 4 so they will not crash into the ground at WP 3 (They may help you delay both of the columns) 4) I added a message (with a sound) to notify you when each of the columns of tanks start to move. Think of it as a message from JTAC saying "They're rolling, I am now available". JTAC will say there is no tasking available if you call him before the columns start to roll. 5) I also added messages to tell you when the column delay triggers trip. They happen about 50 minutes after the columns start to roll. You get points for the delay when these messages pop up. Hit your ' key to show what % of the mission is completed. If you end the mission before 50 minutes after they roll, it is impossible to get more than a 51 on this mission. I'm attaching my tweaked mission (mission 01B I believe is the same as the 01A mission except that it is raining (?)). backup your old campaign mission and drop this on in your campaign folder, or load it up as a single mission.

Although ED had changed the mission some with this patch, it is still a bit screwed up. At the beginning of the mission there is supposed to be a CAS A-10 flight already in the air, but the waypoints are screwed up in that after WP3 that flight just crashes into the ground. (There is also a C-130 that gets stuck on the taxiway and blocks the tornados from clearing the runway at the end of the mission also). On my machine I have edited the waypoints and moved the C-130 so it doesn't get stuck...have yet to fly the modified mission to see how it goes. I have a feeling that the CAS flight that doesn't crash will be able to help hold off one column while your flight goes after the other. From the way I read the triggers and scores in the mission, both columns are forced to start rolling 20 min after the the mission starts. There is a random chance each column can roll earlier than that though. (I'm writing this from memory since I dont have the misison opened up right now). I believe for each column, every minute after the mission starts, there is a 10% chance they will start to roll. A clock starts running when the column starts moving and if it takes the column 50 minutes to reach their assembly point you get 5 points. An additional 5 points are awarded for every 2 minutes more you delay them (up to 25 points for each column). Thing is with this mission is that JTAC will assign your only one of the two columns as a target. With the default loadout of 4 mavs for your and your wingie is is nearly impossible to take out your target because there is a total of 10 tanks as your target. (Note: I was able to take out all of the tanks once by loading up with 6 mavs and 4 CBU-105s but JTAC didnt have me target the other column and told me to go home). Unless you ignore JTAC and stop one column and then seek out the other column, there is really no way to score max points without help from the other CAS flight that ends up crashing into the ground at the beginning of the mission. Also note that because there is a timer going on that you cant really go, shoot off your mavs and immediately return. The mission needs to run for nearly an hour before you can score above the 51 you get for starting the mission and returning to base. I'm thinking of editing the mission so it sends a message every time one of the delay triggers is tripped and 5 pts are awarded just to give some feedback during the mission (of course you can always hit the ' key to show the mission score when flying).

just to make sure that I wasn't hearing things. I went ahead and reinstalled the release from scratch and then applied the patch. Before and after patching I made a vid recording with all of the sounds at max to compare. Attached is a video showing the difference. (Note, I was wrong about the engine sound, in both release and in patch it is controlled by the in cockpit sounds). The engine sound isn't really louder, it is basically the same....but all of the other sounds (in cockpit and radio and voice-overs are not as loud. It makes it really tough to hear the radio calls. To hear the radio calls better I have to turn down the in-cockpit sounds, but when turning down the cockpit sounds, I can barely hear any of the cockpit switches.

Nope doesn't look like anything made it into the changelog. There is a new sound for opening/closing the canopy and that didn't make it into the changelog either. I noticed the engine sound immediately after patching because without changing any of the sound sliders (after the patch) the engine sound was drowning out the radio. Something has changed...and I would like to get the sound back to the levels I was comfortable with pre-patch.

I'm not sure if the change in the engine sound is more realistic or not with the new patch (never actually flew a real A-10 :) ). Right now the engine sound totally overwhelms most of the in cockpit switches. I thought previously that the engine sounds were controlled with the world sounds, but it is now controlled with the in-cockpit sounds. If the volume of the engine relative to the cockpit sounds is realistic, then so be it.....but I would like a way to independently control the engine sound because I rely on the in-cockpit clicks to confirm if my keypresses or mouse clicks. Is there any way to change the engine sound only so I can hear some of the other in cockpit sounds a bit better?

In that mission you need to delay the tank column(s) a bit. I've opened up the mission in the mission editor and looked at the mission goals. You get 50 pts for just starting the mission. You get 1 pt for landing. There are two columns of enemies and you can get a maximum of 25 pts for delaying column 1, and max of 25 points for delaying column 2. Delay them for some time and you get 5 pts, delay them longer get another 5, up to 25. Thing is unless you destroy all of the tanks in the first column JTAC assigns you to attack, I dont think you will get targetting for column 2. With only a single wingman, you will be lucky if he survives and you get destroy the first tank column. If you only delay a single column for the max time (I cant figure out what the max time is though), you can only get a max 76pts. To be honest, with this mission...anything you can do to advance to the second mission I would consider to be a success :). I personally was able to get a 76 out of this mission by being able to kill the first tank. All of the following vehicles bunched up, fired off a bunch of mavs at the tanks in the big clump, and then used some CBU-105s to kill off a bunch more from above the clouds. Of course I changed the loadout to give me a TGP + 6 mavs + 4 105s. (I targetted the standing clump from under the clouds, circled back and then climbed to like 9000ft and dropped the 105s from a safe distance). On some of the missions is is difficult to tell just what you need to do to advance. The mission briefing sometimes doesnt help. Sometimes you need to open up the mission editor to find out just exactly what the mission designer wants you to do.

Kinda had a "doh" moment last night. Was flying an easy quick mission with the wingie. Got to the tanks portion. Told the wingie to attack armor with guided bombs at my SPI he rolled in and dropped his bomb. After he dropped, I was waiting for him to say "rejoin" and got tired and ordered him to rejoin. As soon as I did that I remembered, he is dropping an LGB stupid, he still has to lase the target and wait till the bomb hits. He replied that he was rejoining...two seconds later I see the bomb miss by a couple of tank lengths. My rejoin cost a LGB kill for sure. Nice to see this modeled :)

I was messing around with the ME last night and was wondering just what determined the group ID number for aircraft. I have a sneaking feeling that it is determined by the order that aircraft are added when creating the mission and there is no way to manually change the group ID in the ME. BTW...I was flying a SP campaign mission last night and I noticed that my ID #s changed when my Wingman's wheels left the ground and not my wheels lifted off the ground.

Just noticed tonight (I think it may have been mentioned in a different thread). 1) I have had success in getting the JTAC data by making sure my Unit ID = 01 and my Group ID = 01. 2) What I had read somewhere was that the UnitID & GroupID gets reset when you take off....but that may not be correct. During a campaign mission tonight it reset the moment when my WINGMAN took off. so....make sure you have your IDs set to 01 AND all of your flight has taken off before you contact JTAC.

I was messing around in the Devil's cross campaign and in the debrief it showed two A-10 crashing 3 minutes after mission start. I watched the track and proceeded to see the two planes in the flight just dive straight into the ground. Looking at the mission in the editor, I see that when the plane reaches their waypoint three they are told to go from 3200 MSL to orbit at 2600 MSL, which is below the terrain height. They followed orders to their death. May wanna fix that :)

I read the stuff about the nationality also, but I have my nationality set as USA in logbook....so unless there is a different USA somewhere, then it should be the same :). Its not just the logbook, the kills aren't showing up in the campaign window either. Also in the debrief screen, the score is always 0, and it shows "no name" in the mission name line.

Same thing happened to me, There is another thread that says the datalink is borked in multiplayer. It has something to do with the Group ID # I believe.

Found a couple of more minor errors in the mission 1) the ONCE (US CAS3 SPAWN) trigger is missing the condition GROUP DEAD (US CAS 2) condition at the top also 2) CAS 2 and 3 have the callsign BOAR, but in the radio menus they are listed as UZI EDIT: also CAS 2 has a mission start time showing as 10:15, and it should be 2:15 (I really hope I didnt actually screw this one up myself but don't think so)

I opened up the Push - 3-1 mission to understand a bit about how to create a mission (and figure out a way to beat this mission! :) ) and I found a minor mistake in the triggers. The Trigger: 1 ONCE (US CAP2 SPAWN) references as a condition UNIT'S SPEED LOWER THAN (RU CAP 1.1, 2) and UNIT'S SPEED LOWER THAN (RU CAP 1.2, 2) It should actually read: UNIT'S SPEED LOWER THAN (US CAP 1.1, 2) and UNIT'S SPEED LOWER THAN (US CAP 1.2, 2)

Same thing has been happening to me in campaign missions (See my other thread...ED personnel or testers have not replied in it though). None of my kills are registered in the campaign screen nor are they being recorded to my logbook. I am credited for flying time and missions flown in both the campaign screen and logbook, but none of the kills or missions scores are being recorded. In the debrief screen, it shows my kills, but they dont get transferred after the flight ends to the logbook or the campaign screen. I'm not sure if posting a trk file would help, it seems like post mission file updating that is a problem. EDIT: this happens even though I may have gotten a 100 and "Mission Complete" notification during the mission

I just want to check in to see if any ED testers have noticed the mission scoring/logbook problem with campaigns. I played a mission in the Georgian Hammer campaign (Push - 1-2.miz), took out the bridge and also took out some enemies that JTAC handed over. Debrief showed me with 6 kills, but my score was 0 in the debrief. The kills did not get transferred to the opening campaign screen (nor my logbook), but the opening campaign screen shows me with a 100 success rate with 1 mission completed.

Went back and flew some more. Even thought I didnt get any credit on that mission, it went to the second mission. In that second mission I contacted JTAC got the info and went in for some kills. I fired off two mavs, both hit, but I got in too deep and took a SAM up the tailpipe and had to eject. Has something like a 20 score got credit for the kills. On the third campaign mission I started up the AC and got ready to taxi out of the hangar, and because the taxiway out of the hangar is too damn narrow one of my wheels got stuck in the mud. I gunned the engine, it broke loose and almost crashed into the hangar ahead of me. Couldn't turn around so I quit. Got the same mission again and was able to get off the ground. At the IP I got targets from JTAC. Target was AA, told 3-4 to anchor and then let the wingman loose at my SPI (I had a hard time trying to tell armor from AA and let him have a go). He took out one, and told him to rejoin. As I ready to start my run, JTAC told me to abort. Then told me he had new tasking, and then immediately told me to abort again and that there were no more targets and to go home. There was no use to leave Mavs on the rack when there were still armor and personnel carriers in the area so I went in and shacked 4 with my mavs and I unleashed my wingie to get targets of opportunity. Told 3 and 4 to do the same. They expended their ordinance, and unfortunately #3 didn't make it back..Told them all to rejoin and headed back to base. Landed, found a spot on the tarmack next to a C-130 and quit. Score = 0. Debrief showed all 4 of my A/G kills Got no credit for them on the campaign screen Got no credit for them in my logbook. Not sure what I am doing wrong. Should I wait for the rest of my flight to land before I quit?

Decided to play around with a some campaign missions tonight. Decided to Go or the Devil's Cross campaign. My first time around tonight I opened up the mission in the editor. Added a WP to where the NME was going to be coming from (as a reference point) and also gave myself and wingie 6 Mavs + TGP. After hitting the first IP waypoint, I set the TGP towards the added waypoint to search for some tanks to kill. I found a column and fired off my mavs. I believe i went either 5 for 6 or 6 for six on the hits. When I was getting ready to find some more targets for the wingie to engage, I ended up flying into the side of a hill/mountain...DAMN LOW CLOUDS! At the mission debrief, I had a score of 83 got credits for the kills, and remember what it said for average score back at the campaign screen because I decided to restart the campaign and fly the mission again. On my second go, I did the same with the mission editor in adding a WP and giving me and the wingie 6 mavs. On ingress after I got to the CP, I headed straight for the WP I added searching for the NME. I never crossed the first IP. On the way towards the NME, I ran across a MiG-24 and decided to try some sidewinders....he fired off a couple of missles at me but I dodged them. Unfortunately the wingie didnt fare too well and he had to eject. I got some standoff distance and came around and found a nice column of tanks coming down the road. I was coming at them from the side and was able to target the lead tank, fired off the mav at him and then rippled off the rest in a single pass....nice of them to line up for me! On egress I looked at the TGP view and saw that I went a nice 6 for 6 on hits and then headed towards base. Landed at base, not sure where I should park, I taxied and then parked in front of one of the bunker/hangars and shut the plane down. In the debrief, it showed I had a 0 Score and it did not even credit me with any kills at all. In the events window, I scrolled down and it showed the log of the 6 missles firing/hitting/killing the enemy tanks, but I wasn't credited with them in the debrief. When I went back to the campaign screen, it showed me with 1 mission completed, average mission score as 51. In my logbook it had credited me with the mission, time in the mission, but with none of the kills. Not sure if this is a bug or if me not going through the first IP caused something not to register. Any help here would be appreciated.

How about this: Go to the Official updates forum and open up the "Beta 6 Update" thread that Wags started. On the top click on the Thread Tools drop down and choose "subscribe to this thread" and then choose "Instant notification by email" and then add subscription..... So when Wags updates that thread saying the new beta is available you will be sent an email! (that is if Wags remembers to update that thread!)

Last night I tried practicing some refueling for the first time. The main problem I had was matching the tanker speed. For some reason it seemed like the tanker was flying at 246.5 and my plane would either fly at 246 or 247. My old cougar has a little slop at the middle so it was causing a slight bit of problems. I had everything trimmed as good as it could get and I would creep forward at 247 level, then try to drop back and match at 246, but that 1 kt difference was enough to cause a slight bit of lift loss, so it was a fight. The best I could do was instead of working the stick up and down, was to use the throttle to do the work up/down + forward/aft. When I had everything lined up well I creeped in at 247, and at the point where I seemed to get a slight bit too far forward I would then drop throttle slightly and pump it back forward to try to stay stationary (to match that 246.5 the tanker was going). I basically took my hands off the stick so I wouldnt screw things up. When I started pumping the throttle to keep pace, it would connect. When connected I would train my eye on the point where the pipe came out of the tail boom. On the stick I would only do left right slight corrections, and if I would get high/low I would use the throttle to help correct....I tried not to move the stick up and down. I got it to the point where I could get maybe a 3/4 top off before it would disconnect, but I am getting better :). Also, I need to take my throttle apart because the AB detent for my stick is right where I needed to move my throttle back and forth to match the tanker.

I had found a good TIR profile for myself, and then ditched it because leaning forward didn't make the HUD text any larger. So I mapped the z-axis to zoom. But that screwed up my head shift backwards so I could look at the radios. My Ideal solution....but I really think it would be impossible to implement: Head forward = zoom forward Head back = head movement back on the z-axis For now, I am just using snap views to get a look at the radios during startup.

I just wanted to add some input here... I have a set of Saitek Pro Flight Pedals and just found the Rctrl-Enter key to show my inputs tonight :). I was having problems and I didnt have it inverted (for the toe brakes). I changed the settings to inverted and they seem to work fine. What I want to add to the discussion is that the AXIS TUNE PANEL IS WRONG with respect to the settings that it shows in the graph and how it works in the sim. I think this is what may be causing people problems with their input controllers. (This is in Beta 4) For my pedals if I invert the axis it works correctly. The deadzone setting does what it should, and the saturation curves do what it should....but the graph is wrong. People may be trying to adjust settings based on what that graph looks like but it is wrong. You need to take that graph and rotate it 180 degrees to show what is actually going on. For example in my Beta 4.....If i set up my toe brakes like the what chokko has in the image above. THERE WOULD BE NO DEADZONE. toe brake, but instead my toe brake would give 100% braking at 85% of pedal travel. If I set the Y saturation slider to 50%, it would max out at 50% braking with the pedal all the way down. The sliders on the right are working as they should, the graph is 180 degrees off. On the other hand, I messed around with the throttle axis adjustment and it is borked there also, but in a different way. For my Cougar Throttle, If I set the deadzone to say 50, I only get 50% travel in my throttle before I am at full power. If I set the Y axis saturation to 50%, with the throttle at the idle position, the plane engine power is at 50% and will not go any lower. ED needs to check all of the axis tuning panels to make sure they are working right. There are definitely some bugs there that need to be quashed. For now, if you are having problems I suggest trying different settings in the tuning panel and then loading up a mission with the plane on the runway powered up hit rctrl+ enter and check to see if the settings you put in the tuning panel are working right.

Hrmmm...did I do something wrong because even if I ask for the NVG, I still cannot turn them on. I have to tell the ground crew to hook up DC power and then activate the ground power switches from inside before they will turn on. Am I missing something here?

I forgot to post this earlier, but after I read spooky's post, I did a little test with a mission. Tons of targets, unlimited ammo/fuel, starting at a hover in front of the targets. I did two tests. 1) Fire of Vikhrs as fast as the targeting computer will let me at targets (NOT rangefinding in between) and 2) rangefind or fire off Vikhr 16 times. wait half an hour (I fast forwarded time for 30 minutes in a hover), repeat, wait another 30 minutes, until the laser failed. In the first test doing rapid firings (I realized I didn't have to rangefind on other targets after the first lock, so I had maybe 2-3 rangefinds and the rest were Vikhr fires), the laser failed after about 40 uses of the laser. In the second test (with the rest every 16 laser activations) I was able to squeeze out a total of about 53 laser activations. My feeling is that time to laser malfunction is both a feature and a bug. It is meant to fail, but fails too early. Mainly because if I read Ulrich's explanation conservatively (meaning a "cycle" = single rangefind OR Vikhr firing), I should be able to squeeze off more than 53 laser activations.

Yea...at the time I was getting a range, but it still wouldnt do the alignment procedure. Weird. Another question about Shkval mode... Is it ok to slew the Shkval so the tracking lines on the ABRIS is over top of the nav fix point and align it that way? Supposedly it is linked to a landmark, but In a couple of the campaign missions it is over the water, no landmarks there. Since the ABRIS is calibrated by the satellite, it should be accurate doing it like this....right?