zamboni

I've figured it out. I have wheel brakes on an axis of my VKB stick. I also have toe brakes configured on the rudder. I brought up the control overlay and watched things. On landing, I hit the wheel brakes on the VKB. When slowing enough I hit NWS (but still have the wheel brake going). I drifted to the left a little and hit the right toe brake. That straightened me up. The problem is that if you hit the toe brake and the wheel brake axis at the same time.....when you release the toe brake it also releases the brake on that side. Net effect in the end is full left toe brake and me sliding off the runway cuz I couldn't figure it out. Lesson learned, don't use toe brakes + full wheelbrake at the same time, you may not like the end result. Also, you are right about the caster effect on the nosewheel. It will turn even if the plane is moving only slightly. Its almost like the nosewheel turns more than it should for the movement. At least I figured out what not to do

Ya, I do have it as a slider. When I was testing. I was basically standing still when turning NWS on and off and checking things., that Is why I don't think the caster wheel thing fits. Its almost like pressing the wheel brake is turning the nosewheel by itself. Will have to play around with it some more. Also should mess with the plane in the air, gear down, NWS off and see if the toe brakes also cause the nose wheel to move (that is how I think I ended up off the runway to begin with.....i.e. nosewheel was pointed to the left on touchdown).

I'm a bit unsure on how things are supposed to work, but after doing a search on forums and elsewhere I haven't seen this addressed anywhere. After landing on a couple of missions, I have had the plane start to pull off the side of the runway. Trying to correct with rudder didn't help. I slid off the runway and after hitting NWS I was able to get back on and taxi back to parking. After I got out of the way I went to the external view and started messing around. This is what I found: 1) with NWS on, rudder left/right seems to work right with the nosewheel steering 2) with NWS off. If I press the right toebrake, the nose wheel turns right. If I release the toe brake the nose wheel remaisn right and I can only turn it back to the left using the left toe brake. Should the toebrake be causing the nose wheel to turn at all? I'm guessing my problem with skidding off to the side of the runway was a result of hitting the toebrake with NWS off before landing. and when I landed it caused it to slide off. This doesn't seem to be right. But not seeing it show up as a problem for others, I am wondering if it only happens to me, or if it is a "feature" and I am not careful with my toe brakes.

This mission can be a frustrating one if you want to contact JTAC, mainly because, once the enemy armor gets into range of the allied tanks, they just get tore up. JTAC may give you the target, but by the time you do a run in, they may be totally obliterated. I usually just look at where the smoke is coming from then point the TGP to the road leading back to see if there is anything else coming and then target that. If you try to fly over where the tanks are, the SAMs and MANPADS will just tear you apart. It is best to just hit them with Mavs or if you want to bomb. Hit with clusterbombs via CCRP at 15K and above. As for the "extended info" on the radio menus, that is probably just the frequencies that are added when you use the Easy Radio option. I still haven't weaned myself off of it :).

I had already uploaded them. You can find the link for the mission files at the end of this post.

The mission is a bit screwed up in the JTAC target assignments if I recall correctly. The Mission editor has targets assigned that never spawn. When you contact JTAC it gets stuck because it is waiting for a unit that isn't there. I went in and changed things in the mission. I should post it, but it is on my other computer. I'll post it a little bit later.

Nice list of changes there. I haven't been flying much recently, got the itch to take my telescope out and so some astrophotography and has cut into my stick time. That will have to change sometime soon though :). I would suspect that if they are included in an "official release" then end users would expect that ED would have to support bugs and problems with the 3rd party campaigns. Remove them from the "official in game" campaigns and put them on the website for download, then it would be on the onus of the 3rd party to fix and update their missions instead of ED. Also it may lead some of the end users to hep fix bugs in the campaign themselves and post them to the site if it didn't seem it was an official part of the sim. Some people (me included) might have felt they were stepping on toes by uploading fixes. Also, frees up more time for ED to quash bugs and release more features in the sim :)

^^ This For those missions in that campaign, I always thought that the JTAC(s) included were for other flights. You have your objective, and if the briefing didn't specifically tell you to check in with JTAC....frag the enemy target and then check in with JTAC if you have left over weapons and want to help out a bit. There are some campaign missions with two or three different JTAC units, they cant ALL be meant for you, right?

I'm pretty sure it is up to the mission writer. JTAC may not have any targets for you, but he usually only deals with armor/vehicle threats. If your mission has you to take out a bridge for instance, JTAC can't help ya out there. Some missions have a score based on 100, you can bring up the debrief screen with the ' key and it may have your score there. But it is all up to the mission designer if you end up getting a message saying "mission complete" or not.

I was playing one of the campaign missions a couple of days ago and in addition to the target bearing missing, a lot of the radio calls were not being put up on the top left in text. Its like two, two, two bugs in one!

I had listed something about this in this post. Unfortunately it got moved to the Missions and Campaign Forum Purgatory where it will never be read. In that mission I had something like 10+ failures that didn't have details. In the debrief.log there are about 15 failures, they have the details. Several of the failures are listed multiple times. I included the .trk file and the debrief.log in the linked post above.

not sure why this got moved to the campaign/missions section. The problems I address here are not really campaign/mission specific (maybe one or two). I'm pretty sure that with the post moved it will get kinda ignored down here at the bottom of the forum list.

I ran through the first Devil's Cross campaign mission last night and ran into various problems/bugs. Since they all can be shown in one .trk file, I'll lump them all together in this post. A couple are old problems, but may need to be pointed out again to see if they can get fixed :) Big thumbs up with the improved .trk replay since it is a heck of a lot more accurate and I can just post the .trk so ppl can see what is going on (I replayed the .trk and the problems listed below ARE in the .trk...i.e. I dont crash on takeoff or anything :) ) 1) JTAC doesn't initially respond. When I hit the CP I called to JTAC and he never responded. When I called the second time, he did respond. 2) JTAC abort not quite fixed. I know there was a previous problem where you had to check out and back in when JTAC gave you an abort if the target assigned was destroyed before finishing the nine line readback but this is a little different. I had finished off my Mavs and CBU, I called in to JTAC to say "Attack Complete". If you are down to only guns, JTAC gives you an abort message if you are attacking heavy armor, and usually will assign you some softer targets to get with your guns. This time JTAC gave me the Abort, but I was still stuck in the Engagement menu. Had to check out with JTAC and check back in to get things sorted. I am not sure though if this had to do with the JTAC not responding in #1 above. Previously JTAC logic would get real wonky if you tried to check in a second time if he didn't respond the first time. 3) Wingman call outs do not include directionals. Wingman will call out "contact armor", when previously he would call "contact armor three o'clock". 4) Noticed that a lot of the wingman or calls on the guard channel are not showing up on the top left list where they usually are. When I was getting a lot of the "contact armor" calls from the wingman they weren't on the radio call list. Sometimes they do, sometimes they don't. 5) C-17 refused to land - At the end of the mission, when returning to base, there was a C-17 that just circled the airport. Didn't look in the ME if it was a assignment problems with his waypoints, but he just circled and never tried to land. Other AI planes could land though. 6) Debrief menu failure spam - I got shot up a little bit in the mission, I never got a warning light or anything, but I lost my guns. On RTB and mission quit, I had a list of about 10 items with "failure", but no detail on what the failure was. In the debrief log (that I included), it only seems that I had one failure listed (lost ILS or something), but no other failures listed (not sure if the guns that I lost would have shown in the debrief log or not). Something seems screwy here anyways. The rest in this list are kinda niggles that have occurred in the past and didn't get fixed or never really were called out as problems/bugs. 7) If you have radio on and set to the flight's frequency. When you call for engine startup the wingmen will call out "Rolling". Not sure why it is "rolling", maybe something like "starting engines" would be more appropriate. This has always annoyed me for some reason. 8) Still is a typo in the JTAC radio menus that reads "Ready to copy remakrs" 9) This one bothers me quite a bit. If you order a wingman to "attack with mavericks" and he DOESN'T have mavericks, he will "copy" will start his roll in and when about ready to attack realizes he doesnt have mavs, and then will rejoin. This is majorly annoying because unless you cheat and use "F2" to look at his weapons load you have no idea what weapons he has left. If you tell him to attack with mavs and he doesn't have mavs he should reply "negative".....then you will know he is out and he won't fly into danger and then rejoin without doing anything. 10) Ive noticed this especially with the DC first mission. It seems that wingman fuel burn is a lot greater than lead's fuel burn. In this mission, it seems all of the A-10 flights are loaded out with about 50% fuel. If you get into the battle area at a height of around 15K, your wingman will burn almost all of his fuel and will call out bingo and will RTB very quickly. I remedy this with my wingman by loading out around 75% fuel. This still happens with other AI flights though. In the first DC mission there is already a A-10 flight in the air that holds at WP3 (I usually check this with TacView). Right when they are about ready to push, that flight's wingman ALWAYS RTB right at push because he is out of fuel. Lead usually goes on and does some damage, but there seems to be quite a bit if difference in fuel burn between lead and wingman. OK, that is all I have for now :) Attached is the .trk file and log file all zipped up for your perusal. failure.zip

Coolio, no big thing, Ive gotten to a habit to check to see if DTS is selected, if not it is only a quick couple of button presses.

I haven't seen anyone mention it, so I am not sure if it got fixed or if I am not doing something right. I thought meant we no longer would need to change it to DTS when doing a cold start, but I am not getting DTS on the hud after everything is set. I still have to change it myself. Something I am doing wrong?