

captflyby
Members-
Posts
206 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by captflyby
-
NVG good for ground operations. I do not believe I like them for carrier landings. NVG are out now in DCS with this update 07-18-2018
-
If it is a regulation, it is a good one. Bobbing up & down in a vast ocean, I'd want all the reflective tape I could get for them to spot me before the sharks did.
-
Thanks Doum, I'll do as you suggest and report back. Edit: Follow up: I still don't know whether it is in the DCS or how the mission is put together by those who do so, but I did manage to get the lights to function, every time. Still do not know if time of day is a factor, but when dark they do come on. Would like them on in bad weather as well, but that is for another day. The planner of the mission, needs to include the carrier tower frequency in the briefing. If not there, you must ask, or if they did not include it, I guess 127.500 AM is the default. SRS simple radio has nothing to do with this. Use voice or keyboard, contact atc on the correct carrier with the correct frequency and the lights come on BRIEFLY. Upon touchdown they go out almost immediately, as others here have already stated, frustrating I'm sure, for the guy coming in behind you. It is very helpful to have guiding lights on a dark night, low visibility, or foggy day. Thanks to all of you who helped me figure this out. Someone needs to make a sticky for this.
-
I am told that if the mission editor has a freq for the Stennis like 298.000 AM that the freq is NO longer 127.500 AM but 298.000 AM. You must call (or use keyboard) inbound each time, and that the lights go out the minute you touch down. Sounds all very reasonable, except that it does not function. I have edited the freq, the time 2AM when any sane person would be landing WITH lights, and nothing works. I think this must be a bug in DCS - mission editor or something. I follow exactly all the instructions, and yet, no lights - carrier or field. This is VERY frustrating as I have seen the carrier lights - the landing box - lit up exactly as a runway should be just one time - and can never reproduce it. Very frustrating. I cannot see to land - in VR.
-
I am glad you have been able to bring up the landing lights. I cannot. Once you have comm 1 on 127.500 (FM).....what do you "say" to get the lights to come on. Just clicking the frequency does not do it.
-
VR Shaders mod for better VR experience
captflyby replied to Kegetys's topic in Utility/Program Mods for DCS World
Install text is not clear for someone that doesn't know how. Tried 2 x to install exactly per directions. Comes up consistently with a loading error and game will not run unless I remove it. Those who know what he's talking about in the install file...if you could help us with the "long hand" explanation, filling in the gaps that are assumed knowledge. I would be most grateful. Love VR and would really like the opportunity to try this mod. But directions as they are now, are for me, mod is unusable. -
FOSS, It's all good. I don't mean any criticism to anyone or DCS. Just verifying that I found a bug work around for some at the moment until DCS can get it fixed.
-
I should mention, following the training mission last night, that I logged into a different squadron training server, used an entirely new/updated training mission for deployment, and tried the auto start. Same problem. Then I tried manual start, all worked fine for me. Still a bug though. You can change the frequencey in any preset you choose, once I do like 250.450 for Al Daphra, then I notice that several other of the presets have the same frequency as the one I just entered. ...but that is another issue altogether. ...for me, no auto start, can enter manually radio frequency on com1 or com2 ok..consistently so far.
-
Thanks FOSS, yes I should have made a short click, and then a long click. I can assure you I did both many times. Nothing... for me at least.
-
I contacted DCS technical support, and here was there very quick response and immediate closing of my ticket: " Konstantin Kharin 06/26/2018 18:52:43 Quote Hello. Hello, we are only technical support and can't answer for in-game questions find more on forums about F-18 https://forums.eagle.ru/forumdisplay.php?f=557 Best regards and many happy landings ! Konstantin "MotorEAST" Kharin Eagle Dynamics IT Team " Here is the response after I immediately filed a 2nd support ticket request and they immediately closed it a 2nd time: Konstantin Kharin 06/27/2018 17:15:19 Quote Hello. use support ticket system for technical, activation, purchase trouble etc. Reporting about bugs on our forum (http://forums.eagle.ru/index.php) will more effective for feedback and lessen the load support service. It's not our competence. Thank you for understanding Best regards and many happy landings ! Konstantin "MotorEAST" Kharin Eagle Dynamics IT Team "
-
I agree with Hippo, it would make things a whole lot simpler - all lights on all airports & carriers - on all the time. But, if you have to make it complex, or make it sort of real. Lights on for all night - no ask, and on when bad weather, low ceilings all day - no ask.
-
Will the 127.500 freq work for Al Daphra as well? Does anyone know?
-
I just landed at Al Daphra - pitch black out. Called inbound on ATC - no runway lights. What I noticed that I had not noticed previously, was that in pitch black, with no runway lights, and bright HUD lighting - you cannot see the runway throught the HUD. I landed the plane (in VR) looking to the left and to the right of the HUD. Next time I will shut HUD lighting off prior to final, or better still find out how to get the lights on. Pitch black, lights should be lighting both runways automatically - shouldn't have to call and ask - that is for small backyard landing strips. That's my mileage - yours may vary.
-
In conclusion: 1. I am convinced this is a DCS bug. That is evident, but what is not so evident is that each seem to have their own variant of the problem. 2. For me, each time I use autostart the bug appears. Each time I manual start, no problem. 3. For some it is the opposite. Some in my squadron have no problems, regardless of how they start the jet. 4. DCS tech support told me it was beyond their technical expertise. If they can't figure it out - how am I supposed to. Give me the source code and I have guys that can...but I don't see that happening. 5. Thanks to all for input. Keep posting results. It could be I'm wrong, and tomorrow I have the same problem "regardless" of what start method I use. In the mean time, I am having a great time learning to fly this jet. Thank you DCS.
-
Here is the update as promised. First, thanks to all you guys for your input. My squadron, also, has had much input as well. I erased everything and reinstalled completely fresh. (2 days). Nothing. I did not reinstall SRS. Completely uninstalled. Nothing. I did make sure that "Easy Communications" is now turned off. Nothing. But I am really excited. Too early to say for sure....but I think I may have discovered the bug... I tried this in single player, and then got really excited when I found it copied the same behavior in multi player. Here it is: Every time, single player or multiplayer, switching aircraft, that I use the auto start sequencer, the bug appears. I set a frequency like 250.450 and it jumps back to the 305.000 But then I started the same plane, same mission, with manual start. Frequency changes and stays 250.450. I then tried this in multiplayer, with the same results. Looks like there "might" be a but in the LWIN / Home auto start feature. Just saying maybe...too early to know for sure. Will keep testing and post results after this weekends training missions.
-
I have decided to completely uninstall DCS and start from scratch. If that doesn't work, I guess I fly without radios. Will post results.
-
How do I set AM ? found it...
-
Thanks guys. I have video of this problem in single player and multi player. YouTube Videos * Single-Player Example: https://www.youtube.com/watch?v=GSzmpuSowPY * Multi-Player Example: https://www.youtube.com/watch?v=XQHOsdyXeKw Here's what I do: With both engines running: 1. Turn up vol and brightness knobs. 2. Select com 1 button - comes up in 1 preset 3. Rotate com to "M" position 4. Hit "CLR" button 5. Enter frequency desired ex. 250.450 for Al Daphra 6. Select "ENT" button I would normally think it was just my computer and redo the whole thing, but I have two (2) flight sims. One at work, and one at home...and BOTH do the same thing.
-
After last weeks beta patch, Wed 06-20-2018, I noticed that my comm 1 and comm 2 would no longer set frequencies manually. Normally not a problem because in single player you can simply edit the missions frequencies and off you go. But in squadron missions or training, in multiplayer, I do NOT have access to the missions to edit frequencies in advance. Frequencies are often changed at the last moment, making the manual setting important, or you don't have communication during the flight. It also means no inflight refueling, or work with LSO for carrier ops. So for a week I have tried: DCS Repair. Nothing. SRS complete uninstall. Nothing. Changing to another hornet aircraft in the mission. Nothing. (some said that worked for them.) Holding down the "ENT" button for a longer period. Nothing. Running under administrator. Nothing. Setting the frequencies directly into the presets. Nothing. I have TWO VR sims, at two different locations. Both are beta. Both have the problem. So after a week of frustration, I find, NO PATCH this week to resolve the issue. I contacted DCS technical support, and here was there very quick response and immediate closing of my ticket: " Konstantin Kharin 06/26/2018 18:52:43 Quote Hello. Hello, we are only technical support and can't answer for in-game questions find more on forums about F-18 https://forums.eagle.ru/forumdisplay.php?f=557 Best regards and many happy landings ! Konstantin "MotorEAST" Kharin Eagle Dynamics IT Team " Obviously they don't have a clue. Is anyone else experiencing this glitch, or am I in uncharted waters. I know several are experiencing it in my squadron, but no enough for anyone to care about the issue. Any help would be appreciated. Thank you.
-
Thanks for the info. The F-15E definitely has my vote. Those engine have the punch needed for a good A2S contender.
-
Would be good to have refueling 'easy" mode to learn how, then "med" for normal and "hard" for the hard core types that are bored with the learning process.
-
Not a fan of making any air to air refueling any harder. Can't even get hooked up as it is.
-
Forget the names. Not possible to put in all that someone might want. Just give the mission editor the ability to add whatever call sign(s) are needed when creating the mission.
-
the pullup after cat shot is a bit exaggerated?
captflyby replied to WildBillKelsoe's topic in DCS: F/A-18C
I reduce thrust a bit once the airspeed is manageable, nose comes right down within acceptable range for normal climb. -
Trying to find info on VOICE ATTACK and the F18
captflyby replied to Turnip's topic in PC Hardware and Related Software
Use your voice to control your aircraft I use VA. If a file in the DCS control config panel is mapped to a keyboard command, you can use your voice to control it. Ex. Gear up / gear down is controlled by the letter "G" on the keyboard. I programmed "G" in voice attack, so that when I say "gear", the landing gear cycles up or down. You do not need Viacom Pro to make voice attack work with the Hornet. I have the Viacom Pro, but I find it much easier just to use voice attack directly. An example of where you CANNOT use voice attack is the autopilot. There is no way to "map" a keyboard command in DCS, to make the autopilot function. You just have to use your mouse. So you cannot use voice attack.... unless there is some way Viacom Pro can overcome this ... that I do not know.