Gianky

Hey Silverdevil! As rob stated, the Hornet has a momentary switch to control radar elevation and Tpod zoom. In the TWCS I think the best thing you can do is to bound that control to the paddles in front of the throttle, or to the two way button near the analog stick. I'm using the first way and it works fairly well (but keep in mind that, when using the Tpod, you have to stop the zooming in or zoomin out using the opposite command - i.e. when you zoom out and want to stop, tap the zoom in button -)

Hey guys! First of all, thank you all for your replies, and sorry if I didn't show up sooner, it's been a busy week. As for the topic of this thread, as Deano correctly said, I wanted to know if I can deliver LGBs in CCIP while self-lasing, as I'm used to do in the Hornet. I prefer to drop in CCIP because I can do it further away from the target and avoid getting close to it at all, while on CCRP/AUTO you have to fly straight to the target and the system allows you to release the ordnance only close to the target, so that most of the time you fly nearby or have to overfly it. Also, dropping in CCIP, with the Bug, I can "save" some bad pass, diving in on the target and lasing while I climb out and away. With the Viper, all of the above seems to be impossible, since, as said, when in CCIP the Litening is slaved to the pipper and there seems to be no way to decouple it. Of course, I could just release the bombs in CCRP, but it forces me to get closer to the target and lately after I overfly the target or pass by it, when the Litening camera rolls to track the target, it begins bouncing around and loses contact and the bombs go awry. I noticed it in the third mission of the Arab Spring campaign, dropped 6 GBUs, only 2 hit the target, the rest of them fell away because the Litening would lose the target after swivelling back. If I could drop in CCIP, I could keep the target in front of me and painting it with the laser till impact. Maybe I'm missing something, maybe it's just a bug of the Litening, maybe you guys can tell me how to work around it.

Hey guys! Is it possible at the moment to drop LGBs in CCIP? When I select it, the TGP is slaved to the pipper and I didn't find any way to "un-slave" it... So, is it possible, or CCRP is the only way to drop LGBs?

Not a daft question at all.... I must be the most stupid dumb guy in the world! I was actually taxying to the wrong runway! Thanks Florence, I'd never had gotten that. And thanks for the campaign, too, I'm glad to be able to unleash the Falcon in one!

Anyone? I tried again tonight, reinstalled all the missions, but nothing changed, wingmen are not moving yet.

Hey guys! I just tried to fly mission 2, but my wingmen are stuck on the apron, they don't move when I taxy to the runway. Any idea why this is happening or how I can fix it?

Aside from the fact that we don't know when it'll be delivered, I honestly don't think that's gonna help, it's a lighting issue, not a targeting pod one. Yeah, unfortunately DDIs, unlike HUD and AMPCD have only two settings for lighting, that doesn't help either. As for contrast and brightness, not sure if it's how it works in real life, but, yeah, not much effect in here, for this issue.

:megalol:

Hey guys! Since 2.5.6 flying in a dark night in VR is a bit of a trouble, since the lights blind me. Lowering Gamma level from 2.2 to 1.5 helped with almost everything, but one, very important thing: using the Litening. Especially on the DDIs, using the Tpod at night is a PITA. The best workaround I found is to use FLIR view in BH mode, but even so, when some white spot comes into view it glows too much. Anyone else is having troubles with this? Has anyone thought of any other kind of solution?

That's the marker beacon, it illuminates and starts beeping when you pass over the ILS beacon (bet you were landing when you heard it, weren't you?) ;)

Hi there Kengou! First of all, thanks for your efforts, your spreadsheet is a great resource to have. Secondly, some time ago Bailey made a utility to calculate the weight and balance of various DCS modules, including the Hornet. Here it is https://www.digitalcombatsimulator.com/en/files/3305863/ You may try to contact him and ask about more data (for example, I noticed you don't have twin GBU-38s in the spreadsheet, he does in the app). He hasn't updated his program since last August, maybe you two could start working together and give us the definitive W&B utility for the Hornet (and, why not, other modules!)

Hey Mike! You don't have to replay the whole campaign, just the mission you failed. At the bottom of the debriefing screen there's a row of buttons. To immediately fly again the mission you just failed, press the third (IIRC!) button from the right in the debriefing screen, labelled "fly again". If you don't feel like flying again immediately and want to do so in another session, press the first button on the left (I don't remember what's it called), the system will warn you that you will lose all your progress, ignore it and go ahead, you'll find yourself in front of the campaign window and you'll just have to press the green button to replay the mission you failed, when you want to do it. I hope I'm remembering the correct position of the buttons, I'm at work now and going by heart!

Thank you, Mbot! Is there a way to replace a mission without advancing the campaign?

Hey there! Thank you for another pearl I didn't know about the Hornet, Andrei, now I can store TACAN stations coordinates in the MC! :) Unfortunately, that didn't help. Yesterday night I fired up again the next mission in the campaign, another strike mission, started the aircraft and took off without passing to the INS the coordinates of WP0. Once in air, I used a ground based TACAN station (ironically enough, the closest one is an Iranian station, Bandar-e-Jask) and got the INS aligned and working, then immediately set the Mk-83s for release. Alas, the CCIP was broken anyway, so it looks like INS alignment in not the culprit. If anyone has any idea how to try to understand what's wrong, I'm willing to test it. Another question, if I don't want to fly bombing misions for now, will using the SkipMission.bat simply generate a replacement mission, or will it move the campaign forward and make miss one mission?

So, in the Hornet mini-updates thread, Wags wrote: "We are adding the ability to mount the targeting pod on the station 4 cheek station. In order to do this correctly, we must first recreate the 3D model of the pod because the current model does not support this (cooling intake is on the wrong side of the pod)". Now, I'm a bit confused, because our pod has the cooling intake on its right side, just as its real counterpart have (see at 3:58 and 4:28 ). On the other hand (no pun intended), I've seen pictures on the Internet of Litening with the cooling intake on the left side, pictures that are clearly not mirrored, since the writings on the pod are in the correct way. So, what am I missing here? Have the different Litening versions got the cooling intake on different sides? Can the pod be built with it on either side, according to the user preferences of the type of aircraft on which it will be used? And, if there are indeed different versions, can't we just use station 6, instead of 4?

I was thinking before about where I started the aircraft. In my custom mission, I started from the ground and CCIP worked correctly, while in campaign I start from the carrier and it doesn't. Can you confirm that the issue happens only if you start the aircraft from the CV? Also, if I have the time, tonight I'll fly the next strike mission in the campaign aligning the INS when airborne, using the TACAN. Regarding this, one question: step one to align the INS using TACAN is "TACAN beacon data must be saved in MC" How can I check if the CV data are saved in mission computer? Thank you Scotch, if we can't find another workaround, I'll have to change the date in the campaign. However, I was wondering if I had set the date in the right way in my custom mission, not how to do it in the campaign.

Hey Andrei! First of all, thanks for your reply. On to the matter, if you're referring to this thread I've seen it, but it has been tagged by BigNewy as [NO BUG] and closed, just because people said that changing the date solves the problem. I'd say it still qualifies as a bug, since it should work even before 1994, with properly aligned INS. I see you're part of the ED testers team, are you guys working on this issue, or is it better if I PM BigNewy and ask him to reopen that thread? Beside that, there's something more than just the date, because, as I have written in my previous post, modifying the date to 1990 in a mission I made, everything worked alright, it just in the BG Delta campaign that I'm seeing this issue. To be clear, in my custom mission, I changed the date in the weather tab, and verified in mission, in the briefing window, that the date was indeed set to June 1st, 1990. Is that enough or did I have something more to modify? If you guys need me to test this issue more, I'm game, just tell me what I have to do to get to the bottom of this.

Hey guys! So, last week I tested if the date is affecting the workings of CCIP. First, I modified a practice mission in Caucasus I normally use to drop dumb bombs, changing the date to June 1st 1990. I added some waypoints, took the same loadout I had in the campaign mission and went up, doing exactly what I did in the aforementioned mission. Everything went smoothly and CCIP worked normally. So, I decided to fly again the strike mission in the BG Delta campaign.... and, well, CCIP didn't work, again. As you can see in the screenshots (sorry for the resolution, they're taken in VR), INS was aligned and working (as you can see in the first 2 ss, WP distance is diminishing), I setup the 83s for single bomb CCIP release, and when I selected the bomb the CCIP line was slanted and totally unuseable... Anyone has any idea why the systems are working this way? Next mission is another strike one...

You aren't the only one: https://forums.eagle.ru/showthread.php?t=261141 Thread was closed and dubbed as solved, I hope I'll have time to try on a custom mission tonight, I'll let you guys know.

I'm going by heart here, so something might not be perfectly accurate, but here's how it went down. Yes, I did the INS alignment, and everything worked correctly, map was there and HSI was showing the correct distance to the WPs. The other thing I did was to write down the coordinates of the targets I wanted to hit with my bombs, then create new WPs to use as targets. I got to the IP, turned toward the mission generated target WP, then switched MA on and A2G mode. Already at that point, IIRC, the CCIP line was askewed; then I selected the first target WP and WPDSGed it, system switched to AUTO and, IIRC, event the AUTO bomb line wasn't at the center of the HUD, aligned with the target diamond, but on the left side. After that I deselected the target WP, switched back to CCIP and tried to bomb the targets guesstimating everything (needless to say, it was a disaster...) EDIT: Tonight I'll modify a training mission I did, chaging the starting date to 1990, to see if it happens again.

Hey MBot, sorry to pester you, any idea on the above? Anyone else, actually, any idea why CCIP doesn't work?

Hey MBot, could you check this thread, please? https://forums.eagle.ru/showthread.php?t=261141 It looks like somehow CCIP is not working in 1990....

That's more or less what I'm seeing, the only difference being that in my case the bomb line isn't perfectly horizontal, when in level flight, it has a 20-30 degrees of downward inclination, to the right of the flight path marker.

Yeah, exactly that SMN

I had the same issue, in the Hornet battle group delta campaign, before the last patch. I'm pretty sure I had aligned the INS correctly, map and navigation directions were functioning well. No idea if the issue is related to the mission date. I had Mk-83s, set for CCIP, nose MFuz, inst Efuz and single bomb release.