Jump to content

bonesvf103

Members
  • Posts

    1275
  • Joined

  • Last visited

Everything posted by bonesvf103

  1. Well what I did actually was take the original lua and rename it export.lua.bak. Then I deleted the line and saved the whole thing as export.lua. Even after the integrity check and running DCS and Voice Attack and factory resetting Vaicom Pro preferences and unchecking plugin support in Voiceattack settings, it still worked for every aircraft except the Hornet. When I llok at that export.lua file, no Vaicom code has been written to it. So, I dunno why it only affects the Hornet. I'm trying one more integirty check and restart and trying again. v6, boNes
  2. Just want to add that at least for me, the Hornet is the only plane affected by no radio comms menu. EVen with VAICOM Pro not working anymore, I atill can bring up the comms menu in the Tomcat, Falcon, etc, curious as that may be... v6, boNes
  3. Well I deleted the Vaicom Pro line in the export.lua and I did an integrity check, but still no comms menu in the Hornet. Works fine in the Tomcat though, and even in the Falcon! v6, boNes
  4. Thanks Jayhawk. Wish me luck. Some of the problems people reported, I for some reason have not experienced. No matter how many patches were done, I always got a comms menu, this is my first time losing it. But you and others have. That's curiously interesting. Other people said that while using Vaicom they could access the Jester wheel, and either see a flash of it or see it in another screen. I never have had either happen. I could hear the radio chirp and feedback as if the Jester wheel was on but I never got any screen flicker or another wheel elsewhere etc. Odd that I have such varying (and at that moment, beneficial) results when using my Vaicom Pro compared to others. Hmmm v6, boNes
  5. Update. I did a Steam integrity check and the radio menus are working again for the Tomcat but not for say the Hornet. I also have a Jester wheel. I haven't started Voice Attack though to see if it will change anything or if Bailey's profile will work instead. SO I dunno.... v6, boNes
  6. I too am hugely disappointed. Even if I go to Bailey's profile, it was nowhere near as robust and had as many workable functions as VAICOM Pro did. But until then, I need to know what to do especially since it not only doesn't work, but I now have a DCS with broken comms--I can't make radio calls via keystroke at all. I am too squeamish on messing with lua lines. I don't want to break anything further and end up having a full reinstall to fix things. I don't think a slow repair is my answer as I am running the Steam version. MAybe I'll try the integrity check first. But I may need help doing lua line things (guess it's time to learn), or even to uninstall VAICOM Pro, which I hope will come back. Best scenario is getting my DCS radio functions to work again while leaving VAICOM PRo intact just not started or plugged in in case Hollywood come back to fix things. Jayhawk, I may be emailing you about this since you seem to know what you're doing... v6, boNes
  7. Hi, OK I tried it with the patch. On the one hand, I did get another Phoenix killing Phoenix instance. On the other hand, when I fly it a few more times, the Phoenixes so far appear to behave much better now, I got 90-100% kill every time. What I didn't kill I got with Sparrow or Sidewinder. The bandits sure do know how to maneuver and smartly defend now! He had my Sparrow and Sidewinder in a tailchase for a while before turning back at me and I had to take him with the gun, it's scary! Thanks! I'll let you know if anything else comes up. v6, boNes
  8. Sounds good, thanks v6, boNes
  9. So I was doing the PG BVR mission and I fired 2 AIM-54Cs at 30000 ft, flying as fast as I could, at Fulcrums that were 25-30 miles away (closer to 30). As I monitored things, Jester called splash. I thought, OK, one Fulcrum dead. BUt when I merged both were still up and unscathed. As it turned out, my 2nd Phoenix killed my first Phoenix! How is that possible? In addition to that, the Fulcrum had deployed chaff to trash the Phoenix. I would think that a countermeasure resistant AIM-54C would fare better against that than it did. TacView attached, missile on missile kill at 12:02:20. Also shown in results at 15:32:40 I dunno, but after the last updates, I basically can't get a single Phoenix to hit even though it's the same mission and I attacked the same way where I was getting 90+% kill ratio. I even went in as close as 25 nm and shot from high altitude and highspeed and they still missed. They get dodged alot, no matter if they were As or Cs. And now they are killing each other. Puzzled. v6, boNes Tacview-20221026-231141-DCS.zip.acmi
  10. Haha with the "Damn Bugs" patch! v6, boNes
  11. I've hit a few maneuvering fighters with Phoenix active off the rail. To be honest, I did not think they would hit because they flew a straight line path and as mentioned before, they were slow. But then to my surprise, they turned hard to lead the target and boom. I fired 2 because I thought the first one was messed up, and they both hit! Best $3 million I ever spent! v6, boNes
  12. Ak ok, guess I was being impatient. Thanks! v6, boNes
  13. I fired Phoenix with ACM cover up and it still took a half second or so to come off the rail. I thought when fired that way they are supposed to come off the rail immediately? It did track as advertised though. v6, boNes
  14. That all is what I was experiencing, yes. It is purely visual. Thanks v6, boNes
  15. Does this include the emerg oversweep flag? I've noticed with wings set to auto, cover down, and you go fast renough so they sweep back to 68 deg, the emerg oversweep flag comes on. Is that a bug? v6, boNes
  16. You can also switch to ground stabilized display on the TID and estimate the target's course since north will now be oriented to the top. v6, boNes
  17. What about external fuel tanks? I heard somewhere that they don't like you to jettison those when they are empty even though it would help your fuel endurance but the only reason why they didn't like it is because they cost money--well, also probably because they can be reused too. But why haul around empty bags when fuel is critical, right? v6, boNes
  18. Another thing I keep meaning to mention is Jester's inaccurate clock code calls. The only time he calls the bandit in a correct position is if I'm straight and level, otherwise, his calls are lagged and I look where he tells me to and the bandit is already elsewhere, and not just because he flew elsewhere quickly. He just gets so lagged and makes his calls in chronological order it seems. I'll hear about a missed missile long after it had already missed, for example. v6, boNes
  19. I might add also to ignore the E brackets in the Tomcat HUD. It is ratchety and inaccurate, even in real life. RL Tomcat drivers even ignore it. v6, boNes
  20. I know that in the real world alot of aircraft will jettison their unspent Mk82s or other iron dumb bombs before trapping so that live ordnance doesn't get knocked off onto the carrier deck and cause a disaster. But what about if the ordnance was something more, well, pricey? Like a GBU-24 or a GBU-38? Do they still want you to jettison those before trapping? What about missiles? Especially the $1.5 million Phoenix? v6, boNes
  21. In DCS, if there is an E-3, is it also broadcasting in Link 4A? So link 4A is one way and that is from the E-2 to the Tomcat? So the Tomcat can't send anything to the E-2 or an E-3 for that matter? Also in DCS, OK Link-4 is available and you can use it, but how does that help you in the big picture if everyone else is on Link 16? How did they mitigate that in real life when the Tomcat was still flying and had to do so amongst Hornets and Falcons etc? v6, boNes
  22. So I'm trying to figure out the benefits and use of these links. Link 4A goes between fighter/AWACS/etc assets whereas Link4C is only between the Tomcats. The two links can't be communicated on at the same time. So, if two Tomcats are sharing radar contacts with each other on Link 4C, and they want to pass that info to the E-2 or say an F/A-18 nearby, when they switch to Link 4A, do they lose their Link 4C contacts since they can't do A and C at the same time? What if the F/A-18 is on Link 16, how does it get contacts that the Tomcat sees on Link 4? The Hornet has to switch to Link 4A? Why bother with Link 4C between Tomcats if they can get an arguably better picture from the E-2 on Link 4A? What good is any of the data Tomcats or Hawkeyes have/give on Link 4 if everyone else is on Link 16? I'm just a bit confused. Thanks. v6, boNes
  23. When you tell Jester to lock a target, does he by default do it by PDSTT or by PSTT? I'm pretty sure he does by PDSTT but am not entirely sure... v6, boNes
  24. I used to have that problem, but then I found that when I did tell him to track QDES, he would snap back to it just fine. I have done this in the last few days and it still works. So, I guess my only question is, are you sure that you properly designated the target? v6, boNes
  25. Yup, I was just about to come back here to update you all on that when I saw your reply, thanks. So yes if you tell him QDES (or, in my case with AIRIO, "track designation"), he will bring it back. Thing is, I wish he didn't switch to begin with. If in the thick of things he switches and I can't get him to go back to designation on time, then the run was needlessly trashed. I don't know why he would need to switch to begin with. As for the TCS thing, still a problem. Even if you have wingmen nearby to take out the bandit so you can do your run, Jester still switches to the TCS. The only thing I can say further on this is that I noticed that if you drop even though he switched to the TCS and stayed within drop parameters, as long as the target is designated in the LANTIRN the bomb will still hit. You just can't monitor it from the front to make sure you aren't masking. But, it's still annoying that he switches v6, boNes
×
×
  • Create New...