Ryno1217

OK, I can not seem to get this to work. I have followed so many tutorials but no go. On the latest bout with it, I have discovered that the file "liberation_nexturn.miz" is not being written. The CMD window even states "No such file or directory." Don't know what to do from here. Any help would be appreciated.

If im not mistaken, the mission is set up with AI aircraft on all the catapults. You should simply have to wait for one of them to take off, then your aircraft should load in. If this is not true, then hopefully someone else can answer your question.

So recently I was play the F/A 18C Red Flag Iron Hand and noticed that there was different freqs for different aspects of the flight, ie AWACS, Strike, flight, etc....giving that there is 2 radios in the Hornet, I was wondering what a real pilot does as far as technique/procedures for monitoring/switching between all the different freqs? What freq is priority, AWACS, strike freq, flight etc? How often does the pilot switch between the less important freqs so one does not missed an important call on a giving freq? Im sure priority comms can vary from mission to mission, but one can argue that AWACS and flight are the priority comms for SA, as wingmen could call out missile launches and direction. But then there would be a risk of missing a call on the strike freq that could be mission critical -- for example, having to wait for a SAM site to be destroyed before you can continue your mission. But if your constantly monitoring the strike comms, you could miss AWACS or wingman calls and so on. So with the risk of possibly missing some form of vital info, how would the real world fighter/attack pilot handle the different freqs for a giving mission? Not saying there is a right or wrong way to handle this, I'm genuinely curious on how its done.. Thanks to anyone who takes the time to answer.

Thanks. I will try when I’m back in front the computer.

Im having trouble with something hopefully someone here can shed some light on. I want to set up an AI Escort that does the following: Escorts player/unit until a given way point then stops escort and flies to an orbit point Orbits until certain conditions are met once conditions are met, the AI restarts the escort on the given player/unit. Now I figured out the commands and triggers to get this to work, but the issue I have is that when the escort command stops, the AI flies to its original start point (way point 0) before going to the orbit point. Obviously, this doesn't work when the start point is 50+ miles away from the orbit point....so I'm drawing a blank on how to get the AI not to fly to way point 0 when the escort stops. Any suggestions???

I could be wrong, but I thought just putting flaps switch back to AUTO will trim the plane for 1G flight?? For instance, when I'm landing on the carrier, I trim for on speed. I very rarely land on the first attempt so i apply full power, raise gear and flaps and begin the pattern again. i dont retouch the trim until I lower gear and flaps again. Give it a try. Trim for on-speed then raise gear and flaps. Aircraft should fly like normal 1G flight.

YES! I am glad you got it working. It is in fact the name of the aircraft in my LUA file. I will set it up like you reference and all should be good! Thank you!

I have the same result with the F/A-18. No change in movements. I suspect its due to the name of the aircraft in the LUA file, but i tried all different ways with no change to the movements. i gave up after about an hour playing with the LUA file. i will continue to fiddle with it and reply back here if I get it to work. Best of luck with it!

I know I'm a little late to this thread, but I came across something similar today. I was trying to upload a sound file to use as background noise for the mission but for some reason when clicking on the "open" button to select the sound file, nothing happens...nothing at all. Not even a pop up where files would be save. The only way I was able to get it to work again is to completely exit DCS and restart the game. But then it only lets you select a file once. If you select the wrong file, or dont like the file, you would have to exit the game to choose a new file. Anyone else came across this?? Edit: I figured it out. I created a sound folder in my saved games folder to save all my sounds, but apparently that doesn’t jive. I deleted the sounds folder and everything is working fine.

Much better wording than mine! Thanks

Im new to the Hornet so keep that in mind but I never seen where the NWS H stays on. I've always had to hold NWS button for high gain. Could be intentional, could be a bug! As for as the rudder issue, the only time I've noticed something like that was because of NWS H after rudder input. For instance, I am pushing left rudder, then I push NWS H button, the jet will straighten out then slowly start turning right. It will correctly work after releasing all inputs, then holding NWS H, then use rudder input. Give that a try and see if it works.

I do not know if you can reset to 0 trim with the button. One thing to maybe try is use the autopilot with barometric altitude hold. Let the autopilot trim the plane as needed then disengage it to see if that works. Don’t know if it would but maybe worth a try. I used do that in the Mirage as I could never trim it out properly. So I would let the A/P do it, then she would fly nice and straight/level.

I did not see where this was said so keep in mind if you take off without takeoff trim set and flaps at half/full the plane will nose up relatively hard. So make sure your T/O trim and flaps are set before taking off. If you happen to take off without those set, lower your flaps to half and then back to auto. This will reset the flight computer to trim for 1g flight. If you did the take off correctly, then I don’t know what the issue could be. Hope this helps.

Just an FYI if you want to use AB on the carrier. Hold number 9 and number 0 (not keypad numbers. The ones close to the backspace key) to raise finger lifts while advancing the throttles to use AB on the carrier.

dude you were way off mark! I know this because I did not see a giant fireball at the back of the ship like when I try a CV landing! Seriously tho... good job!

Much appreciated!

I have a question which might be a dumb one, but I am relatively new to downloading and running missions, so please bare with me. I am interested in downloading the PG version for a private Coop mission. I see you have scripts involved. Do I need to also download and install each script or is that something that is included with the mission download? Thanks and apologies in advance if it is a stupid question.

I do not know if any are broken, but i believe flashing means that the system is going through its self-test stage. it should turn to steady after a few moments. Someone please correct me if i am wrong.

i didn't check in the mission editor, but i tried another mission and the mavericks worked. Thank you for the suggestion.

Thanks for the reply. I didn’t have time yet to test other missions so maybe it’s just that particular mission. I will look again tonight after work.

Let me start by saying I recently had to do a fresh install of my OS and DCS. But prior to this, I did not have the "bug??" I am about to talk about. So after the fresh install of DCS, I started up the Instant Action Nevada Takeoff mission for the A10 to set up my controls. After my controls were done, I started dropping random weapons to make sure I had everything assign correctly. The default weapon load out worked fine until the mavericks. I believe you have an H and D model and neither of them come off the rail. The mav screen flashes like it fires, but no joy. All master arm switches are armed. I tried manually selecting them in the DSMS page, using DMS to cycle weapons, and it happens everytime. Shows lock, press weapon release, screen flashes, and it does not come off the rail. Has anyone else came across this or is it my specific game that something is off? Any info/input would be greatly appreciated.

I have this same problem but mine is with 60 fps. I dont have a gsync monitor but the screen tearing annoys the crap out of me. So I use the in game vsync. For the most part I am able to run solid 60fps with jitter free TiR, but as soon as it drops below 60, jitter fest. Even 55 fps will cause the jitter. I have had this problem in 1.2 release version all the way till now with the 2.5 OB I always assumed it was something on my end since i could never find info about this. The worst thing about this is that it makes it even more difficult than it already is to track a target. The jitters are somewhat like a motion blur effect. Somewhat subtle but enough to notice. Very annoying indeed.

Man you asking a lot out of that 970! i have a similar rig (in signature) and even at 1080p and settings not quite pushed as high as you have it, I still struggle to maintain 60 fps in high populated areas. Lowering your res would help gain fps.

x55 and Windows 10 home here. Ive had only 1 small hiccup with the HUD software recently. I uninstalled and reinstalled HUD and everything works fine.