sthompson

Did you do the FINISH step? What happens when you push the "TEST" button. (Be sure to wait until it completes. It doesn't put anything in the log right away.) Do you have extensions enabled? If all else fails you might want to go to the reset tab and reset your database. (You may need to run FINISH again afterwards.)

Text formatting in Chuck's guide is definitely a bit weird. This is most noticeable when you do a text search and find that search hits occur in strange places. There seems to be a lot of hidden text. To see this further, try opening the Guide in Acrobat Reader, then copy some of his text and then do a "paste special" into a blank Word document. Select "unformatted text" as the special method to see what I mean. Each word appear multiple times. Opening the document properties for the Spitfire guide document in Acrobat Reader and then looking at document properties it appears that it was created using PDF-Xchange. Possibly if you use that software to export to PNG you will have better luck. You might also have better luck if you capture an onscreen image and paste that into a Word document (then Save As pdf) rather than trying to import Chuck's Guide itself directly. I've used that method for some of my custom kneeboards.

I tried it out for the first time yesterday. If you slew TDC over a contact while in RWS mode and then press and hold the TDC switch the radar scan changes to a narrow beam directed at that contact for as long as you hold the switch depressed. When you release the switch you will find the contact bugged in SAM mode. It isn't clear to me what advantage there is to doing this. I found some F-16 documentation that suggests that the narrow scan lets the radar build a more accurate track file. But I can't verify that this is the case for the JF-17 simulated implementation.

In the current version, page 130, HOTAS throttle controls, the column headings for AA master mode don't make any sense. That is, there are two groups of columns both labelled for INTC mode. Furthermore, four of the column headings are labelled the same thing. I think these are probably supposed to be the same column headings as on the previous page (i.e. for HOTAS stick controls).

As documented in the readme file.

That's the first thing I tried. Didn't work. To be clear, if I cold start the plane with bombs already loaded, start the plane, then do a full alignment (either FAST or entering coordinates from the kneeboard), then set HNS to INS+GPS, then power up the bombs and do a full alignment until the timer reaches zero, and only then start to taxi, I get the same results as in the video I posted. However, if I start with the plane hot but unarmed, then ask ground crew to add the bombs, then ask them to update the DTC, then reload the DTC, then go through the entire alignment process for the jet again, then taxi, takeoff, and do the bomb alignment in the air, then the bombs hit their target. They also hit their target if I start up with the plane hot and bombs already loaded (e.g. hot from runway), or in the air, then no further alignment is needed and the bombs are accurate. EDIT: I realized after writing this that what I described is not the GC alignment. I was unfamiliar with GC alignment because it does not appear in Chuck's Guide, and I had not seen it on any of the tutorial videos I watched. I since found some information about it and tried it out. It does appear that the bombs hit accurately if I use GC alignment and then align the bombs themselves before taxi. I'm aware of that. But if you watch the video you will see that the alignment countdown timer for the bomb alignment is zero well before I release the weapons.

The latest OB change log indicates the following new features for the JF-17 Thunder: Added: 8 new liveries. Added: AA radar SPOT when T5 pressed and hold (need to rebind T5 press) under INTC master mode. Added: AA radar BS/NAR and HA/WIDE modes toggled by S2 press when no target locked under DGFT master mode: NAR is same as BS, but radar scan center can be controlled by TDC. WIDE is same as HA, but radar scan center can be controlled by TDC. Added: AA radar won’t re-lock same target within 1 second after unlock it under DGFT master mode. Added: manual (DIR) submode of AG master mode (for unguided weapons) when T2 pressed and hold (need to rebind T2 press). Could someone explain to me what SPOT is?

I've tried pretty much all possible combinations for doing the jet alignment and HNS settings. None seem to make any difference in results in my test mission. The bombs always miss if I start with a cold jet and always hit if I start with a hot jet.

And here is a video showing that bombs miss when the mission is started from a cold and dark jet. https://youtu.be/7l8hCLtlDOY

Hot ground aircraft with no weapons at start. Ground crew added the LS-6 bombs and updated DTC. Reloaded DTC and flew mission. Bombs delivered on target! I will try to post a video showing the problem when I start cold with bombs already loaded soon.

This does not work for me. The LS-6 persistently overshoots the target. The only thing that works for me is to start the mission hot (either on the ground or in the air) so that the weapon is already aligned at mission start. Very frustrating. Furthermore, I can't make a track to demonstrate the problem since you now need to remove the Inlet covers before starting the engine. That requires interacting with the Ground Crew / Configuration Panel. But it does not appear that clicks on the Configuration Panel are recorded in track files and so the engine dies in the track playback.

Unfortunately, interaction with the Configuration Panel does not seem to be recorded in Track files. So it is now impossible to create even a short track that requires starting the engine.

Not true. It does it even if it can find the DCS folders. So there is no point in deleting the "scripts" folder in the root drive. It's just going to come back next time you start VAICOM PRO.

Coming to this late. First of all "recognized" in the log means that VoiceAttack recognized the word. It does not mean that VoiceAttack knows what to do with it, or that the command was passed to VAICOM. To see whether VAICOM is getting the command it would be helpful if you would turn on debugging and then post the log after you've had some trouble. Personally, I leave debugging turned on all the time since it adds only minor overhead. Second, if you were missing 500 commands then you definitely had not properly done the "Finish" step in the installation instructions.

Does anyone have any tips for completing Mission 9 "Broken Arrow" successfully? I've tried numerous times using the default LS-6 glide bombs in TOO mode using either the PP1 (waypoint 36) preprogrammed target point as SPI, or else setting my own waypoint in the mission editor smack on top of the bunker. So far no kills. I've tried different release altitudes and speeds. I've tried turning on INS+GPS in the HNS settings. I've tried aligning the bombs on the ground before taxi. Nothing gives me any hits on the bunker (at least not reported by DCS or Tacview). It's pitch black at the target site and I'm not sure how to view the damage so I have no insight as to how the bombs are landing.

True, but be cautious about this following a DCS update. VAICOM PRO modifies DCS files, and this must be done before DCS starts to be effective. Now if the files are already modified because you ran VAICOM PRO previously then this doesn't matter. But it comes into play when DCS updates, because the update is essentially an "undo" for the VAICOM PRO modifications. This is why it is important to start (or restart) VAICOM PRO (and let it complete its initialization) before you start DCS after a DCS update. At other times the order is not so important. It would help to provide more information. How is it "not working?" For me VoiceAttack and VAICOM Pro have been working just fine with the MT version. But I don't use Steam.

No you do not need to do that. Those files are copied by VAICOM into the DCS main directory structure (not Saved Games). If you check you will find that they are already there and you don't need to do anything. Apparently these copies are created at the same time as the ones in the DCS directories. It isn't clear why.

I went looking for a setting like this and couldn't find one. Can you be more specific about the setting in question and how to find it?

Yes. My mistake. See edited post.

AG radar MAP submode issue. On pages 179-181 the guide says that S2 left will cycle between the MAP submodes RBM, EXP, DBS1, and DBS2. I think that used to be the case. However S2 left now cycles between the major AG modes: MAP, GMTI, SEA1, SEA2, WA, TA, and (sometimes) AGR. This also affects the HOTAS chart on page 129. Personally I liked the old function and wonder why this changed. I can't find any mention of the change. Now the only way to access the MAP submodes is through the corresponding OSB button. It would also help to have some documentation for AGR mode. I keep finding the radar in this mode and do not understand it. I don't seem to be able to turn it off if there is a designated SPI. Hope it doesn't sound like I'm complaining! Chuck's Guide is especially indispensible for the JF-17 since there is no official manual in English. EDIT: I realized after posting this that the cycling I described is what you get when you use S2 left from one of the AG radar modes while in NAV master mode. It works as described in Chuck's Guide if you go into AG Master Mode first. I'd still like to see some description of the AGR mode however. Is there any documentation?

This is super impressive. Wish there was something like it locally here in my part of the U.S. Congratulations!

Which other weapon? Direct hit with a pair of GBU-16s gives me no points!

I have the same problem. Also the cloud cover makes it impossible to do the recon using the Targeting Pod from altitude. Overall the included campaign needs a lot of work. The little movies at the start of some missions appear to be underground for me. Can't see a thing. And I don't think this was updated since ED made major changes to weather.

336 pdf pages in the Chinese manual. Now if we can only get it translated

The third and fourth route points for the mission are both labelled RP4 in the mission editor. This means that there is no third route point when flying the route. As a result, the missile is heading towards the beach instead of towards the target area when it reaches the last RP. Renaming the third RP to RP3 fixes the problem.