Chief1942

"So Leatherneck, hear this; Thank you ":thumbup:

WhooHoo! Got it and most importantly the "key" to drive it.:music_whistling: Come on 18th!:pilotfly:

Always felt that since it takes literally years for a real pilot to become proficient with every aspect of the particular aircraft they fly, it stands to reason that a similar amount of time will be required of those attempting to master a PFM simulated aircraft. One has to crawl before they can run, and there are any number of assists to help that "crawler" get their feet under them. But remember, it is also rewarding to be the provider of those "assists". That's simply what "Old Timers" do:smilewink: Wisdom is useless until you share it;)

Thanks again. That was a very informative thread. I don't know why I missed it when I did a forum search regarding ILS procedures. I think it's one of the "truisms" of flight simming, "We ALWAYS have more to learn!":smartass:

Hey, good to hear they are aware of the problems and are willing to make the required adjustments. Should be fixed in "a couple of weeks";) On a side note, it must be a real PITA trying to address all the niggley issues we keep coming up with. Not a problem with some modules as we accept that they are in the "Beta" phase, but for final release modules, these things should get their attention in short order.

Thanks Flagrum, I read about that doing a search of the forums previously and had tried to make sure I turned off the "steerpoint" button when pushing the ILS and/or the TACAN buttons on the Nav Panel. It still didn't appear to work so I thought it was something different between the DCSW A-10C and the CD version. Seems that there is a difference visually/functionally between the two iterations as the horozontal steering needle is always present at the bottom of the ADI in the CD version and not in the DCSW version. Probably due to updates and the pursuit of more realism and accuracy in the DCSW version since they no longer update the CD version. Long story short, I think I have it down now, so off to practice, practice, practice. Again, thanks for the feedback.

Something amiss? Watched the video that Mike posted to help with ILS use. Fortunately, if I am using the A-10C standalone (CD version), it works as advertised. But when I fly the A-10C in DCS World I have yet been able to get the horozontal steering needle even to appear at all. With the standalone A-10C it is "parked" at the bottom as it should be until it gets a signal. But it simply is not there in the DCSW A-10C, the verticle needle is present. Anybody have any suggestions as to how I get it working correctly in the DCSW? Getting tired of bouncing back and forth between the two iterations just to practice ILS approaches.

Thanks Eddie. Considering the model you had to use, this resembles the a/c very closely to the one in the picture I posted. I'm sure you have many more great skins to come and we all look forward to yours and the rest of the fine work that is coming forth. Take care and "Watch your six!"

Strut, You did a fantastic job on that skin. I especially like the way you did the intake and the number on it. Was much easier actually painting the real a/c with all that stuff than trying to do it on a computer.;)

Thanks Crazyeddie. The reason you can't find anything on VMA-343 is it was a squadron commissioned specifically/only to draw new aircraft (the A4D-2N at the time) and then swap them wholesale for the older aircraft in an operating squadron, that were then transitioned to the reserves. In the case of VMA-343 we swapped brand new A4D-2N Skyhawks for VMA-223's older and being phased out FJ4-B's. Once we had sent all the FJ4-B's to the reserves, VMA-343 was disbanded and all the squadron personnel were assigned to the various operating squadrons. I personally went to VMA-121, an A4D-2N squadron. I/ve attached an image of the squadron patch.

Hey Semper FI! and thanks for the response. The plane in the pic I posted is an FJ4-B. If that one Marine's head wasn't in the way you could see that stenciled on the fuselage above the BuAIR Number on the aft fuselage under the "flying elevator". We had about thirty of those birds in VMA-343 and in the picture you can see the number of pilots we had (I recollect 10) in the squadron. We had pilots fly one plane, park it and simply walk to another and take it for a hop. The actual number of flying hours was important to those pilots and they availed themselves of the opportunity that came with being in VMA-343. I have a couple of our sqaudron patches around somewhere. You might want to use one as a "graphic" add-on to the fuselage although the aircraft in the photo is what they all looked like. Pretty plain and straight forward. If you go here you can get more info on the plane plus some line drawings. http://en.wikipedia.org/wiki/North_American_FJ-4_Fury#Specifications_.28FJ-4.29 I appreciate whatever you can do with this in light of having to use the F-86F as a model, but with these old eyes if I squint real hard I can actually see the planes I crawled all over in my youth. The confusion between the F4 and FJ4 I've corrected. My fault. We did get F4 Phantoms while I was at El Toro. Massive aircraft! but I never was in one of those outfits. I await your return and look forward to your efforts.

[ Crazyeddie, I know this is a big request, but could you possibly do a skin for the attached FJ4. This is VMA-343. It was the first squadron I was assigned to at MCAS El Toro in 1960. It was a "transitional" squadron, that's why it was so small. We were sending the FJ4's to the reserves at Olathe Kansas and when it was all done the squadron was again disbanded and we all went to other operating squadrons, most with A4D-2N Skyhawks. If it's not a task you want to take on. I understand, but it would make this old Marine's DCS involvement even that much more enjoyable. By the way, that's me 5th from the left 2nd row standing. Hard to believe I was once 18 years old:D Thanks.

Although it was the navalized version of the F-86, the FJ-4B Fury did have the ability to refuel inflight. I know, I was an airframes mech on those birds and the probe was affixed mid-length under the left wing. Since the Navy/Marines usually had different requirements for their aircraft due to their operating environment ie from carriers and out over the ocean and such, I don't believe I ever saw an Air Force F-86 with the inflight refueling probe. The differences between the FJ-4B and F-86 wern't that noticable at a distance, but up close one could definately see all the Naval operation requirements that were added. The arresting gear and beefed up landing gear struts for just two.

As happens so often from the Pentagon, weapons systems are scrapped before there is actually an adequate replacement. I think they would be wise to keep the A-10 until such time as they have something as good or better to take it's place. Currently they are claiming that the F-18 and other combat aircraft can fill the vacancy left by the A-10. Anyone who knows aircraft knows that one of the strengths of the A-10 is loiter time, which is simply the main weakness of those other systems. Yes it is "dated" but I personally don't see anything in the current inventory that can replace it. And that includes the Apache Longbow.

It needs attention I know some are admitting to a discrepency between "visual damage" and damage that inhibits performance, but look at the screenshot and tell me if you've EVER had your P-51 look like this and still fly like it just came off the factory floor. There has to be some relation to reality in the 1 vs 1 arena or it is simply an exercise in futility. By the way, according to the debriefing, this bird took 160 hits and it never phased it.

I think you hit it! Initially I felt like I was never going to be able to effectively fight the Mig-15's with the "86". But like you, after each sortie, I find myself getting more and more in tune with not only the limitations of the Saber, but more importantly, those of the pilot:smilewink:. Never has been a real world replacement for Practice, Practice, Practice. Muscle memory is an amazing attribute.:joystick: Still end up dead a lot, but at least now I manage to take a couple with me:thumbup:

From what I've seen so far from DCS, I'd probably buy a Snoopy Flying Doghouse if they could get the flight model done correctly:thumbup: I don't know of any other venue where I can have as much enjoyment for such a moderate investment than flight simming DCS modules.:pilotfly:

Try this. Open Mission Editor and select the mission you are working with under the "Open" tab which opens when you click on "File" at the top of the page. Select the "Player" aircraft symbol and when the panel opens to the right screen you will find a icon for "communications" on the same line with the loadout and other icons. Should be the last icon and looks like a transmitting antenna. Select it and in the dropdown menu see if Batumi (Channel 3) is set to 260.00 Mhz. If not you can simply highlight the current freq., delete it and type in the correct one. You may have to do the same for all the air bases/airports. The radio channels for the F-86F are tied to the channel selector dial on the right rear panel in the aircraft and are unique to each airbase/port. In other words, to contact a particular "Tower" you must have that towers channel programmed to the Channel Selector Dial in the a/c. And that assignemnt is done via the Mission Editor.

I had that happen to me. I saved all the controller presets folders that were in the "Saved Games" folder for all my other aircraft, deleted the folder, rebooted the computer, reinstalled the saved folders and the "Controller" page in the Options menue repopulated itself. Then I was able to create my F-86F contoller profile. You might try that approach.

Like anything that is mass produced, some "lemons" make it out of the plant. I'm certain Amazon will provide a replacement, and when you get one that works properly, you will be happy with the kit. It makes simming a pleasure.

Just so that you are aware that someone else has had the same issue. Until I read your post, I simply attributed it to my lousy flying skills. But I definitely cannot roll left with any authority. It's as if it goes into slow motion.:noexpression:

You're not alone. After reading the beginning of this thread, I jumped into the 1v1 with the 190 and although the changes are notable regarding the aggressiveness and accuracy of the 190 AI, I made him look like Swiss cheese and yet that plane was able to perform better than the day it came off the assembly line.:megalol: Perhaps later they (ED) will have time to work on the damage models for the AI to the degree they have with the planes we fly.:thumbup:

Chalk this up to "Old Brain". It seems ALL my issues were tied to the fact I did not delete my "Saved Games" folder before or after all the re-installs and it was simply staying with the previous mess I made. All seems well now and I'm off to set up my controls and options. Sorry for the confusion.

Okay, I did a re-install of DCSW and all my modules. Of course it wanted to update to the current 1.2.9.30604. I still get the "DCS has Stopped Responding" whenever the de-briefing screen tries to load. I also get a complete hang when trying to access the Logbook. I know there were some issues noted previously with the Logbook not keeping individual stats on the various A/C, but at least I could access it. No longer. I hope there is something I can do to fix these problems or do I simply wait for 1.3.0?

Tried "Repair" twice and it still loads 1.2.9.30604 and I believe the current release is 1.2.8.27915. I updated the Beta install when I downloaded the F-86F and it is working fine. Not sure why it installed the 1.2.9 in my non-beta release .