bonesvf103

Does anyone know what the light signals on the fuel pods on the S-3 and the IL mean/tell you? Thanks. v6, boNes

I think so, I can upload it later today, and a track if need be. v6, boNes Cool, either we are correct or we will be cellmates at Arkham Asylum. v6, boNes

This is not necessarily a bug but just something I noticed with the new S-3 model. First of all, it looks great, I love the fuel pod propellers working and the lights. The issue I am having though is the hose seems to be awfully short. So short that I have to get my nose pretty much right up to the fuel cell to plug, and then when I do, I have to get so close to the Viking wing to maintain the plug that stick and throttle inputs have to be microscopically tiny or else you will fall out of the basket. Even these nano adjustments in stick/throttle can induce PIO in an instant if you're not careful. It didn't seem that difficult before but I think the hose was longer before 2.9. It's not impossible, I can still take a full drink, but it will take multiple successful plugs adding up to that and I used to be able to just stay in the whole time with what seemed to be a longer hose. Is this how it really should be? v6, boNes

Thanks so much! v6, boNes

I don't know if this helps any but I have had this happen in the past and it seems like it depends on the mission being run. I don't know if it's a script thing or not, but, as an example, I was flying an Operation Scarlet Dawn mission in MP on a dedicated DCS server and none of the AIRIO commands were working. However, if I went to a different MP server, or if I hosted an MP server, or if I played SP and/or used a stock or downloaded SP mission, AIRIO always worked. So it led me to believe that it was something about the way the Operation Scarlet Dawn mission was written, and with the new DCS updates, got broken (AIRIO used to work on it). Aside from AIRIO, I have also noticed that uncheckmarking "disable menus" is sometimes ignored depending on the mission. If I say "Options" and the list comes up and then I say "Take 2", the menu will disappear as soon as I hit the PTT button to say Take 2, and I can't choose that option. Unchecking "disable menus" will keep the menu up so that I can say "Take 2" and that usually works, but on certain missions it will not and the menu will disappear regardless of VAICOM Pro's disable menus checkbox is left unchecked. So, keep that in mind. It is also probably why people like Reflected advise against using VAICOM Pro/VA with their missions because it messes with it, or doesn't work well with VA, so you have to kind of just run a mission and hope it will be OK. Sometimes, it's just a mission that doesn't play nicely with a third party app. v6, boNes

I don't doubt that TACAN always pointed at the boat. I'm just saying that this is the first time I noticed that the range was changing in a different but realistic way than a shore based TACAN--which I thought was a pretty good feature. v6, boNes

Another. See after the trap. Track included. shade test2.trk

Is it true that selecting quantity of chaff and flares in the ground crew arming screen doesn't work, that you have to use the ground crew>select AN/ALE-39 menu? If you do that do the chaff/flares load instantly or do you have to wait a few seconds/minutes? v6, boNes

Video showing shading phenomenon on the deck (see toward end of video) and corresponding track attached: shade test.trk

OK, I used a Caucasus map and spawned a carrier, set its TACAN to 75X. Spawned a KC-135MPRS and set TACAN 36Y. Spawned an F-14 as player. Saved mission, started mission. F-14 spawned with TACAN set to 16X. This is understandable since I did not set it when I spawned a Tomcat. Its TACAN was set to AUTO and X so it started with 16X. Tuned in the carrier at 75X. TACAN range was changing appropriately. Never disappeared. Same with tuning the tanker. Tried it with the mission set to spawn the Tomcat with 36Y. Same thing, all TACAN ranges were working. v6, boNes

Very useful info, thanks! What about if you are in an ACM mode, or gun mode? I always seem to have to hit the RWS button (PB5) to get it to dump ACM and go back to RWS. Will reset do anything? v6, boNes

On the Radar MFD, what is the logic on the reset pushbutton? It was mentioned a little off topic on a previous post so I haven't been able to successfully search for it so I figured I'd ask to the point instead. So if you had set up radar parameters and hit "SET" and then say you had a TWS soft lock or a STT lock and then hit the reset button, what is the logic of the button function? It doesn't necessarily reset back to your original set parameters, it seems to cycle instead. Thanks! v6, boNes

The only time I experience a sever pitch up on takeoff is if I had landed previously, rearmed, then took off again without resetting my trim. This is because when I'm landing, I have trimmed the nose up high as needed to get and stay on AOA with a minimum of backpressure on the stick. So, if I didn't reset that or compensate, when I take off, my nose is going to want to shoot way up high and I immediately have to correct and trim down or I will stall. So keep that in mind--I should before I do my takeoff, but I get lazy or too rushed and forget, haha. If you are running the Steam version of DCS you can do an integrity check by right clicking it in your collection, selecting properties, then integrity check (I think, I'm going off the top of my head). In Standalone, I believe you have that option in the launcher to repair files. Also, yes if you go to the RIO seat you have a whole new set of controls and keybinds that you must select in "adjust controls." However, I think switching seats is already set by default. But check anyway. v6, boNes To that trim thing--is there a trim reset button in the Tomcat like there is in other aircraft? v6, boNes

I meant to do this yesterday but didn't have time, I will try today. v6, boNes

I tried it again last night and wow, yes, you are right, I was able to see my trap in "3rd person POV" replay for once! Here's my "last track" replay--no desynch! Forgive the sloppy trap, I was wanting to hurry up and test the tracks/replay and get the footage so I nixed tings like radio calls and a proper marshall haha: v6, boNes

Hi there, I also fly the F-14 with the X56 but I do not have any problems. I have set curves for it, but I set the curves within DCS, not with the X56 software. My settings are: • PITCH (DEADZONE AT 4, SATURATION X AT 100, SATURATION Y AT 100, CURVATURE AT 10) • ROLL (DEADZONE AT 4, SATURATION X AT 100, SATURATION Y AT 100, CURVATURE AT 10) • RUDDER (DEADZONE AT 0, SATURATION X AT 100, SATURATION Y AT 100, CURVATURE AT 10) • THROTTLE BOTH – CONTROLS ENGINE RPM • WHEEL BRAKE LEFT / RIGHT These are actually the setting recommended by Chuck ala "Chuck's Guides" and they work well for me. But since you also report problems with other things such as not being able to switch back and forth in the cockpit, or switch views, it seems to me that there is something going on with your DCS and keyboard inputs. Maybe you should do an integrity check or file repair, and if that doesn't work, uninstall and reinstall? Also maybe check to make sure that your input hardware works--your keyboard, your HOTAS--they all have good input. Maybe a bad USB port? My X56 joystick has been exhibiting behavior where it stops working and the only thing I can do to get it to work is unplug it then plug it back into the USB (which I kind of expect since it's a few years old and I've given it lots of wear and tear but in the middle of a critical dogfight when you pull the trigger and nothing happens, that kinda sucks). Anyway, maybe check those things out? v6, boNes

I have not noticed the TACAN not working with the carrier. In fact, I found it a little more annoying in a good way. By that I mean, it became more realistic with the carrier and I was spoiled with the way it was. Before, if I put the TACAN symbol on my 3:00 position to fly a 10 nm arc, I would just have to keep it there and make slight adjustments to maintain 10 nm. Now, it could be at my 5:00 and instead of the range increasing (like it would if it was a shore based airport) it is increasing slightly. I think it is because the boat is also moving, and so I am catching up to it in a turn. That was an added bit of realism that I found interesting. Anyway, if you tuned the TACAN in the front seat, check also to make sure that your TACAN selector is set to PILOT and not NFO. Otherwise you may be tracking the RIO's TACAN radio and he might not have it tuned/on. Vice versa if going by the RIO TACAN if you ahve the pilot TACAN off or mistuned. v6, boNes

It works fine in my HOTAS too. What happens when you go to the controls page and then hit your HOTAS button? Does it jump right to the command in the list? If not, it might not be seeing that particular keystroke. Maybe clear it and then rebind it just to be sure. Also check to see if another key is blocking it, or an axis. I have a slider on my HOTAS that if I forget I have it on, it is constantly sending slider inputs and thus not allowing my, say, landing gear down input to go through. v6, boNes

I noticed that the practice missions that are meant to be Single Player standalone (not campaign) still install into the campaign folder then you have to move them to the SP mission folder. This has been the case ever since the campaign became available. Any plans to fix this? Also I noticed on the 1v1 Guns Only practice mission, that the bandit almost always goes for the hard deck and ends up breaking it, triggering a knock it off. I don't recall him doing this before 2.9. Is this something new or a bug? v6, boNes

Since the 2.9 upgrade I've noticed that shades will flicker on and off. For instance, see this (bad) refueling in the F-16 and in the underneath of the KC-135, you can see the fuselage shades coming on and off especially between 01:15-02:15: I tried with both anti aliasing on and off, but it didn't seem to make a difference. I'm running an RTX4070 OC edition with 12 GB VRAM. I've got pretty much all the video settings set to high in DCS. If this is too high, what setting should I decrease to remove this? The shading also can be a problem for when I'm landing ashore...it always feels like there are overcast cloud shadows making it harder to see where the airbase is, even though the sky has scattered clouds or is clear. Thanks. v6, boNes

Thanks!

BY profile name, I mean within VoiceAttack, when you select via drop down menu which profile you want to use, which in this case is the VAICOM Pro one. I had heard that the VAICONM Pro profile had to use underscores not spaces, but wasn't sure about that. And yes, I misspoke and when I said starting VAICOM Pro, I meant Voice Attack. So I remembered reading in the VAICOM Pro manual over a year ago that you had to wait for Voice Attack to start up completely and load your VAICOM Pro profile before starting Teamspeak or it might now work. One more thing I wanted to add: I have VoiceAttack set to run as admin, yet whenever I run it, it still brings up that dialogue box asking if I want to allow it to make changes to my computer. Why is that? Thanks. v6, boNes

I seem to recall hearing that VAICOM PRo has problems if your profile name uses spaces in it instead of underscores. I also recall that it is recommended to start Vaicom Pro as administrator and waiting for it to load completely before you start Teamspeak or it might not work. Were either of these true, or still true now? v6, boNes

I tried watching a replay in 2.9 afterwards and it was still out of synch. I had some pretty good guns kills on targets and when I watched the replay, it was shooting too late and thus missing the targets. v6, boNes

If you are at a far enough range, the Phoenix is supposed to loft up as it is seeking less thinner air at higher altitudes to enhance its range and end game performance. I haven't noticed anything different or worse about the other thing you mentioned. v6, boNes