rayrayblues

Currently, the comms menu stays on screen most of the time after radio messages are sent or received. I wish it would automatically close. Example: I am in my Su-33 on the new Kuz. I call, "Request Startup" The tower responds and the menu is still there. I have to close it manually. I taxi to the runway and because there is as yet a Flight Director to guide me, I have to switch to F2 to line up behind the takeoff chocks. I then call "Request Takeoff." The tower responds, the chocks and JBD are raised and the menu is still there. If I don't remember to close the menu manually, when I press F1 to return to the cockpit, I get "Abort Takeoff" instead. :doh: Often when I am on approach either to a carrier or airfield, I will use F2 view to make sure my gear/hook are down, or just because I want to look at the external view, the tower will say something, the menu stays on screen and then when I return to the cockpit, I get "Abort Inbound" instead. :doh: It's bad enough that we have to navigate a menu in the first place, but it would be so much better if we didn't have to remember to close it manually after each use. How difficult would it be to have it close automatically? :dunno:

Not to mention WWll era carriers and associated aircraft, F6F, F4U, TDB etc. :thumbup:

+1 Just like the AI do it in F2 view. After taxiing to the right position, select "Parking" or "Pushback" and you automatically back up to the correct spot and the chocks are set. Actually, this mechanism will become necessary when the elevator and lower deck become active.

Yeah, that's the one I remember. Thanx :thumbup:

Sorry, it didn't work. All I got was English cockpit on the Ka-50. Voice is still Russian. Any other Ideas? I had it before.

That made it worse. First I had to wait until the helos started up and took off, then the wingmen started to the cats before me and everything got jammed up. Pic shows 15 minutes into mission.

I'll try it and let you know. It was doing it a few minutes before I posted.

I used to have English on my Russian planes radio comms, albeit with an accent, :D but had to reinstall DCS and now I can't remember how I did it. Anyone???

I am still quite new with the SC and Hornet so I set up a mission to practice takeoff and landings on both carrier and airfield. In my zeal to populate the mission with static and active units I added a couple of Blackhawks to take off from the carrier as well as an E-2D, a second flight of Hornets, a static E-2D and two static Harriers along with the usual static deck equipment. Mission start 12:00 hrs. off the coast near Khasab. I flew to Dubai and noticed that no one else had left the carrier. After landing and parking at Dubai, I heard my wingman call wheels up at 12:30:40. The same happens with the Russian Kuz only the delay was 9 minutes instead of nearly 31 minutes. I shared this mission with my friend Flappie and he concurs that it is a repeatable bug. If you remove the helicopters, the flight runs as normal. Same with the Kuz. Put the helicopters back on and the delay returns. 31 mins for SC and 9 mins for the Kuz. Ray SC Test 1.miz dcs.log Kuz Test 1.miz

Yes they are. I "love" the one where just as I'm lining up for a landing, the wing man zooms right past me at high speed. Scared the s*** out of me the first time it happened. Same happens at airports too.

All well and good, but it is such a pain in the a** to make that many waypoints over a long distance for both the Helo and support ships to follow like a real task force would. Even then, they start out ok and then the speed discrepancies creep in and after 15 minutes or so they are out of sync. I agree with northstar98, we need an advanced waypoint action for helos and support ships to follow the carrier.

Yes the bindings are there, thanks. I re-flew the same mission as described above and the comms were almost 100%. The only issue was after landing at Dubai. There was no "taxi to parking area" message. I had to stop and re-start the engine to get taxi and take off instructions. A minor detail. The wingmen and AI planes still took 34 minutes to leave the ship. What good is a wingman who is 34 minutes behind you. :D It's probably an issue with this particular mission. I made another similar one and the flight took off right behind me. I think I'm good to go. Thanks again for your invaluable help. Here is the mission. SC Test 1.miz

How does this look?

Thanks for the missing files. I was wondering why I had an input folder in my input folder. I followed your instructions and even did it twice just to be sure. I just did a fresh install 4 days ago. I've heard that 2.5.6 is buggy so anything is possible. Attached is the input folder in the input folder. Several other missions were working just fine so, I made a new practice mission and deleted the other one. That file was f....d up. I have another practice mission on the PG map that has other issues. The comms are messed up like I said in my other post and my wingmen and a couple of E-2's took over 30 minutes to launch. I took off from the carrier near Khasab and flew to Dubai. The comms menu wouldn't come up while in the air so I couldn't call inbound. I landed at Dubai and was able to refuel but the comms never said taxi to parking. It was stuck in arrival. About 5 minutes after taking off I hear my flight call wheels up. 34 minutes after I left the carrier. Again, while in the air, I couldn't bring up comms. By the time I got back, the ship was clear and I landed. There were no problems with KB & JS controls, just the comms and the flight tying up the ship for 34 minutes. I think I'll delete that one too. I really appreciate you taking the time to help me with all of this. I owe you one. :beer: :drunk:

I did as you suggested and these files are not in the input folder. aircraft.lua modifiers.lua unit.lua I did it twice with the same result.

Thanks. I know it's getting late in France, so I'll do what you asked and will continue this conversation tomorrow. Sweet dreams. :D

Ah Ha, no modifier file where you told me to look. What now?

I sent the JS config in the last post. Yes I can esc. and pause. I obviously can type on the KB without any problems. Other JS functions work as well, like hat switch for views and axis commands.

Remember, it's not just the keyboard. The JS buttons as well. T.Flight Hotas X {5617F830-6572-11ea-8003-444553540000}.diff.lua Keyboard.diff.lua

Yes I did. The only other thing I can think of is a USB port problem, but it's not all bindings that are affected. Just the ones I mentioned. I'll check that anyway. I have tried clearing and re-setting the bindings, but no luck. I did cleanup and repair several times. BTW, this is a new install just last week.

anything's possible :D

I've never had to tune the radio to any freq with this plane. It's not just this one mission. It's all missions. It was working fine yesterday. I haven't made any changes. It is a simple practice mission for take off and landings. Here you go... SC Test 2 .miz

I have this stick and I use the slider for the rudder in planes and tail rotor in helos. I can't hold a beer with my feet either. :D

In addition to the comms bug I reported under general questions, all of a sudden some of my commands stopped responding. View Center mapped to button 3 wheel brakes mapped to B zoom in mapped to LShift+Z zoom out mapped to LShift+X nose wheel steering mapped to button 9. They show good in controls page, but when I tried to taxi my Hornet to the catapult, I ended up driving right off the side of the ship (Theodore Roosevelt) I couldn't steer and I couldn't stop. After that, I didn't bother to try anything else. My stick is a Thrustmaster T Flight HOTAS X. :helpsmilie: dcs.log

FA-18 C Khasab Theodore Roosevelt