

bonesvf103
Members-
Posts
1286 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by bonesvf103
-
Of course you can also manually designate it a hostile with PLID, but you better be sure then, otherwise if shared to other aircraft, they might attack it and cause a blue on blue situation. v6, boNes
-
Update: I find that on this stock GBU mission in the Caucuses if you fly fairly straight in (follow the line from the WP SEQ to the WP) then make your IP inbound, laser, spot, then in hot call, you will get cleared hot. Deviate too much from that and you will get an abort. I also found that you can egress any way you want and it doesn't seem to have an effect (of course the preferred egress is in the direction the JTAC says). Last I found that even if your bomb hits and they clear you to re-attack, you have to do it quickly--they won't have the laser on forever even if they say you are cleared hot. To avoid this, after they confirm the kill, I check out, then check in again. I have to go through all of the 9 line stuff again, but I use that time to parallel my ingress route and then turn onto the ingress heading. By the time I'm set up, I am ready to tell them to turn the laser on. With the above, out of 6 bombs dropped, all 6 hit. Then I landed at Senaki and ran out of gas on the apron, haha. v6, boNes
-
[CANNOT REPRODUCE/NO TRACK FILE] JDAM Misses
bonesvf103 replied to bonesvf103's topic in DCS: F/A-18C
I wonder if they need some kinetic energy like the Walleye. I launched a JSOW once while flying at 400 KIAS and it fell short, but when I launched between 500-600 KIAS, they hit. v6, boNes -
I cannot stress enough how much trim is your friend! v6, boNes
-
[CANNOT REPRODUCE/NO TRACK FILE] JDAM Misses
bonesvf103 replied to bonesvf103's topic in DCS: F/A-18C
Playing around again and this time I added terminal guidance data. Didn’t change the hit or miss stats much but it made me wonder...how required is this? If I don’t enter terminal guidance data, it seems to guide and hit the target as often as when I do. Is TERM not functional yet? v6, boNes -
OK, so then my suspicions are correct...I have to set bullseye as an AA waypoint even though it's already on the map/in the mission. Too bad if there is a bullseye in the mission it's not automatically set in the Hornet...but I guess that's what data cartridges are for which I don't think is modeled in the DCS Hornet yet. Thanks. v6, boNes
-
So I was brushing up on things in the Hornet and I was watching Wags' video on AA Waypoints and bullseye. In it, in the RDR MFD, you have at the top left of the MFD, the position of the cursor from the bullseye. In the bottom of the MFD you have your position from the bullseye, and in the bottom left you have BRA from the cursor to you. When I try it in the sim, I don't get any of these positions displayed in the MFD. I might get BRA from cursor to me, but nothing else. I tried it in RWS and in TWS, in AA mode and not. But no dice. I checked to make sure the mission had a bullseye and it did show one on the F10 map. Is it that even though there is a bullseye on the map, I still have to make sure there is an AA waypoint assigned to it? Or it its present on the map mean it's already programmed into the Hornet's nav? Or am I missing something else? Thanks! v6, boNes
-
NAVGRID and LANTIRN in MP while Flying Solo
bonesvf103 replied to bonesvf103's topic in DCS: F-14A & B
Ah, yes, good point! v6, boNes -
So I notcied while flying MP that if you have Jester as your RIO, you are not able to do strike missions since he has no LANTIRN ability and you can't jump in the RIO seat to work it yourself. Also, I found that you can have him turn on NAVGRID but if you wanted to, say, change the range of the display or even HCU offset it, you can't, which makes it sort of unusable in MP. Is there a workaround? v6, boNes
-
OK, it's ongoing, thanks! v6, boNes
-
I've notice don occasion when starting an instant action mission that the needles on my altimeter are frozen in the 12:00 position right off the bat. The numerics in the windows showing altitude work, but not the needles. Is this a bug or is something else going on. Example is when I do the Case I recovery instant action mission in either Caucuses or Persian Gulf. It happens randomly. v6, boNes
-
I leave it in CCIP mode, find where the target is (by smoke or otherwise), and drop. It hits 90% of the time all the time. v6, boNes
-
I am dropping GBU without TGP because the JTAC is lasing the target. v6, boNes
-
I didn't write the mission, it is a stock mission from ED. v6, boNes
-
I heard about that, so I did it just to try it. Yup, good way to die! v6, boNes
-
Yes, the propeller is a wind generator to power the EO and steering vanes. And yes, that sucker is heavy. When I launch, I have to trim soooooo much to the opposite side. v6, boNes
-
Ohhh...thanks. Either that wasn't in the video tutorial or I missed it. I did however see in the video that the little propeller in the back is not for propulsion, but for powering the eye, so, yes, it should have occurred to me that the weapon is ballistic. v6, boNes
-
I noticed this has the "investigating" tag. Any news? v6, boNes
-
bump v6, boNes
-
I posted about this in another thread and several other people noted they have the issue as well: Whatever is your current waypoint, the Jester menu shows it as being +1 that waypoint. ie, if you tell Jester to select WP1, and he says OK and does it, the next time you open the Jester menu, it will show Current Destination WP2. So, is that a bug or am I missing something? v6, boNes _______
-
[BUG] Home base waypoint incorrect via Jester via F10 map
bonesvf103 replied to earnil's topic in Bugs and Problems
I also noticed this and posted about it in another thread and several other people noted they have the issue as well: Whatever is your current waypoint, the Jester menu shows it as being +1 that waypoint. ie, if you tell Jester to select WP1, and he says OK and does it, the next time you open the Jester menu, it will show Current Destination WP2. So, is that a bug or am I missing something? v6, boNes -
So I looked at this again and from my testing it seems that whatever is your current waypoint, the Jester menu shows it as being +1 that waypoint. ie, if you tell Jester to select WP1, and he says OK and does it, the next time you open the Jester menu, it will show Current Destination WP2. So, is that a bug or am I missing something? v6, boNes
-
I've noticed lately if I tell Jester to, for instance, set us to waypoint 2, then later open the Jester menu to the navigation menu again, it shows that he has set us to a different waypoint. Is this a bug? v6, boNes