

bonesvf103
Members-
Posts
1275 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by bonesvf103
-
cannot reproduce and missing track file George Not Following Commands
bonesvf103 replied to bonesvf103's topic in DCS: AH-64D
See around 3:25 and 12:00 in particular. Thanks. v6, boNes -
missing info George Not Following Commands
bonesvf103 replied to bonesvf103's topic in Bugs and Problems
That track was overwritten since I flew a different mission since, but here is video. See at 3:40 and at 12:00 in particular. Thanks. v6, boNes -
I have all the George keybounds for Pilot, CP/G, and George AI. In the 30mm gun training mission, he won't execute any commands. WE are in a hover. I hit CTRL V to bring up the interface, I use WASD to change his altitude, airspeed, and heading. He will acknowledge "Roger, going faster" etc, but he does nothing, he just stays in the hover. Can't figure out why. I watched Wags' video and as soon as Wags gives him a command he does it immediately. Mine doesn't. v6, boNes
-
Same v6, boNes
-
AIM-54 Hotfix PSA and Feedback Thread - Guided Discussion
bonesvf103 replied to IronMike's topic in DCS: F-14A & B
This is true. v6, boNes -
AIM-54 Hotfix PSA and Feedback Thread - Guided Discussion
bonesvf103 replied to IronMike's topic in DCS: F-14A & B
And that being the case, well, if the best place to be is at 35,000+ feet to fire a Phoenix and it runs out of juice because the target is at 10,000 ft, then what is the point of having a Phoenix at all? If I shoot it at 10,000 ft so that it doesn't have to drop down a huge altitude difference, then it is losing energy by being in thicker air/having higher drag. Why not just shoot a Sparrow at around the same altitude and have a higher chance of killing it? oh, if you're shooting at low altitude then get in closer range since the air is thicker. Then again, what is the point of having a Phoenix then? I might as well use a Sparrow. Just seems to me that everytime there is an advantage that the Phoenix is supposed to have it is negated by something, making it just as lethal and effective as a Sparrow or AMRAAM, if not worse, so I don't really see the point of carrying a Phoenix then. Shoot it at high altitude...but then it doesn't have the energy against a low target. OK, shoot at a lower altitude...but then it is in thicker air and doesn't have the energy to hit the target or wastes it in an unnecessary loft. The results always seem to ne to be inconsistent and mediocre, especially when fired under the same conditions. I can shoot at the same conditions as say IronMike, and the missile will perform differently than from his test, or not perform the same way in my own after repeated tests. It's a bit frustrating. v6, boNes -
AIM-54 Hotfix PSA and Feedback Thread - Guided Discussion
bonesvf103 replied to IronMike's topic in DCS: F-14A & B
Hmm. I wonder how these F-4s know these missiles are coming to drag them down low when they didn't go active until a few seconds before. It's almost as if they could see them coming before they even went active. The number to the left of the up/dopwn arrow is what? And to the right of it is mach number? v6, boNes -
AIM-54 Hotfix PSA and Feedback Thread - Guided Discussion
bonesvf103 replied to IronMike's topic in DCS: F-14A & B
How about this? 6 shots of AIM-54C Phoenix at 40,000 ft at F-4s ranging from 20000 to 35000 ft launched at about mach .95, head on with valid locks in TWS-A, range about 44 nm. Only 2 hit. What went wrong? v6, boNes Tacview-20220315-143310-DCS-Six-shooter KB.zip.acmi -
I think you can have it execute a keystoke in the profiler (see attached) but I've never used it or had to. v6, boNes
-
Jester and TWS (Hooking, Switching Range & Targets)
bonesvf103 replied to bonesvf103's topic in DCS: F-14A & B
Yes, PH was selected. I just would like for him to hook a target, DL or otherwise, and have the target info show up so I know what I'm up against and he doesn't always. v6, boNes -
Haha...I should add that I'm using VAICOM Pro. v6, boNes
-
Jester and TWS (Hooking, Switching Range & Targets)
bonesvf103 replied to bonesvf103's topic in DCS: F-14A & B
Yup I think that is what it is...Jester using TCS. Thanks, wasn't aware that he does that. As for changing/adding target priority, now that I think about it, I think that was something I was able to do on...ahem... Fleet Defender....haha v6, boNes -
Yes I find also that between the Forrestal and a Super Carrier, the sight picture is very different, so it takers some getting used to. Also the deck of the Forrestal seems darker and so it's more difficult to see details on it such as centerline. So yes, it takes some getting used to. But you'll get there. v6, boNes
-
Any updates on this? Iceman is basically useless ATM. v6, boNes
-
I've been noticing lately in TWS that Jester may hook a contact (it is bright) but no data comes up on it (Altitude, Range, BR, TA, nor target number). It is our contact, not a datalink one. Since it is bright and highlighted, shouldn't that mean he hooked it and thus shouldn't that data come up? This doesn't happen all the time but enough for me to notice it. Also, when Jester does something like change the radar range display, the TID repeater in the HDI blanks out for quite a long time (3 sec+) before coming back in the newly selected range. If I'm trying to track the target while cranking, this messes me up. Why does the screen blank out? When I have a human RIO and he switches range on the TID, it doesn't black out in the front like when Jester does it. Is Jester learning to IFF contact? So many times he will hook a friendly contact or allow the TWS to assign a target number to it because he either didn't IFF it or change it in the CAP. If he has a target number assigned to a friendly, is there any way to tell him to drop that one? Especially if it is say #2 out of 3 rather than #1 u t of 3 or even by itself? I recall that when in TWS-M, you are able to designate and assign target numbers arbitrailty but can't seem to remember how...anyone able to refresh my memory? Can't find it in the manual either. v6, boNes
-
I had the X52 and have since gone to the X55 but programming it is basically the same. Here is what I do and what you have to keep in mind. The mode witch really is not meant to be another button or function. It is to select another set of keybinding that is set in the same profile. So if you didn't have a mode selection knob and as an example only had 4 buttons, you only get 4 buttons to do 4 things. But with the mode selection knob you would have only 4 buttons but you would now be able to have your HOTAS do 12 different things (4 things per mode). So what I do is I have mode 1 set up with a bunch of pilot key commands. If I switch to the RIO seat, then I turn the knob to mode 2, and I now have RIO commands. If I use LANTIRN, then I switch to mode 3 and I have RIO LANTIRN commands. Something else I do is actually use the profile software to generate keystrokes and then in DCS, for a function, I put the keystroke in under "keyboard" rather than pressing a joystick button under "joystick." Otherwise, I am limiting my button to only that function. For instance if I had it in mode 1 and I wanted button 1 to fire the gun, I can't have button 1 do anything else because DCS doesn't sense that I am in mode 1, it just receives commands from the mode the HOTAS is set to. So if I have mode 1 button 1 to fire the gun and mode 2 button 1 to open the canopy but in DCS I set button 1 mode 1 to fire the gun, if I try to enter open canopy under "joystick" as button 1 mode 2, it won't be able to tell the difference in modes and will say that that is already assigned to firing the gun. The other advantage of using the profile software is that you can set macros and advanced commands. So for instance, if you want button 1 to release weapons, go to external weapon view, then back to the cockpit view in one push, you can have it do that. You wouldn't be able to by just putting it into DCS as a button 1 command. The last advantage of using the profile software is when a new patch comes out that wipes out your keybindings and you can't find your DCS one or didn't make one or back it up. The HOTAS profile is independent of DCS, so if your key bindings get wiped out, you can just call up your profile, got to DCS, and for each function you have listed in your profile, go to it in DCS under "keyboard" and hit your button. The HOTAS will transmit the keystroke you programmed into your HOTAS and DCS will think you are keystoking and fill it in the "keyboard" column. Within a few minutes or less, you can have everything right again. v6, boNes
-
He's really starting to hurt my feelings but he says "OK" when I ask him to do something like "head straight" and then he does nothing. I'm trying to do something in the backseat and he is rolling right and diving. So yeah, Ice ignores pretty much any command I give him but he always acknowledges them. What is the problem? v6, boNes
-
When I use eyeballs and head control to point out a target, then tell Jester designate, I hear the beep, I see the command get accepted, but Jester does nothing. No symbology comes up for the drop and no talk on. What's wrong? Running V 2.5.27.0 v6, boNes
-
I did that but after I told him to designate, no symbology or talk on occurred v6, boNes
-
I was bombing a powerplant last night in MP and using eyeballs and fine tuning it with head adjustment, I had Jester designate the powerplant, but the symbology never came up so I had to drop manually without laser guidance. What's the best way to have Jester target "non-traditional" targets such as buildings? Thanks v6, boNes
-
In the cases where VAICOM Pro wasn't working, if I tuned ATC normally or use the menu it would work. v6, boNes
-
Yes, I do. AS for the scan range thing, when saying 2-5 it does work. v6, boNes
-
Thanks for your response! OK let me try saying 2-5 instead. I did not have import new module checked, but I did now and restarted it but it didn't do anything. v6, boNes
-
I have radios set to realistic and "select" function is activated. Whenever I say, for instance, "Nellis, select" it doesn't tune Nellis and I get a message from VAICOM Pro saying "Recipient Nellis AFB is currently not available." Also when I ask Jester to scan range say 25, he leaves the display at 50. It's hard to get him to scan the right range sometimes. What am I doing wrong? v6, boNes