Jump to content

RedeyeStorm

Members
 View Profile  See their activity

  • Posts

    553

  • Joined

  • Last visited

 Content Type 

Everything posted by RedeyeStorm

  1. RedeyeStorm
    That is not what I mean. This happens when the AI reaches a waypoint, switches to next waypoint but cannot make the turn so the effect is it continuously tries to hit the waypoint but that waypoint lies inside the plane turn circle and the result is that AI ends up circling the waypoint. This can happen when two waypoints are too close together with a big angle like having to turn 90 degrees as an example. I hope I explained it a bit clearer now.
  2. RedeyeStorm
    Have a bug with Falcon over PG. You fly out of Al Baghda (or something like that). The airfield has two runways and the briefing reports an ILS frequency for all four directions. On the F10 map there are only two freq mentioned, one for each direction, and the frequency’s do not match the briefed freq’s. No big deal of course. Another issue that sometimes happens is that AI-flights cannot turn towards a waypoint and then start to circle the waypoint. This is usually the waypoint after the egress waypoint. The one that is pretty close to the egress point. Last one. The last couple missions where night missions. AI flights didn’t attack their targets. I know that has been an issue in the past so it is possible that ED never fixed it. As usual having a blast.
  3. RedeyeStorm
    Thanks Migual
  4. RedeyeStorm
    Will do. Okay tried the mission. Two F16, Avion 1-1 and Avion 1-4. could not talk to tower or Awacs. Saw in the editor that the calsign was Python. Changed it to Enfield and Dodge respectivly and the radio's worked.
  5. RedeyeStorm
    Well manual didn't work either @Miguel21. I did find that I had some setting issues where different mics where selected by default. Will try that out now. And that isn't it either. Just checked the dcs.log. It gives this error: 2022-02-21 19:45:34.058 ALERT WRADIO: Error in wMessage::buildSpeech(), event = wMsgAWACSBanditBearingForMiles: [string "./Scripts/Speech/common.lua"]:586: Callname 13 not found for Pack 8 - 13 TFS - Escort 1-1 ! stack traceback: [C]: ? [C]: in function 'error' [string "./Scripts/Speech/common.lua"]:586: in function 'make' [string "./Scripts/Speech/common.lua"]:700: in function 'make' [string "./Scripts/Speech/common.lua"]:1078: in function <[string "./Scripts/Speech/common.lua"]:1074> (tail call): ? [string "./Scripts/Speech/common.lua"]:1155: in function 'make' [string "./Scripts/Speech/common.lua"]:3214: in function 'make' [string "Scripts/Speech/speech.lua"]:180: in function <[string "Scripts/Speech/speech.lua"]:166> I appears in the log every time I call Awacs (either of them) or the tower.
  6. RedeyeStorm
    Hi Miguel, I wil try to change the frequency manualy through the upfront display. The odd thing is that in the first couple of missions it all worked fine. I'll let you know.
  7. RedeyeStorm
    Hi Miguel, Here is the mission: Falcon over PG_ongoing - Copy.miz
  8. RedeyeStorm
    Hey guys. I am having an odd issue with the radio’s. I am not sure if it is a DCE issue I just experience it with DCE. The problem is that I can only communicate with my flight. Tower and awacs are impossible. I do not hear my pilots voice at all. I get zero respons from awacs. Dito from the tower but the comms menu does show the next respons like when asking taxi clearance you get the option to abort. This is with falcon over PG. I am using the preset channels through the backup so I can easily switch between the channels. It could be a Viper issue as well. Anyone have similar experience?
  9. RedeyeStorm
    Check the ‘specials’ tab in DCS menu, it already has the option to use rudder for steering.
  10. RedeyeStorm
    Great Miguel, looking forward to it.
  11. RedeyeStorm
    Hi guys. Got an issue. I have started a 'Falcon over Caucasus campaign' but in the first two missions I allready ran into trubble. On the first mission friendly AI did not attack any ground targets (Hornets with JSOW) and one of my package flights did not take off. The same happend in the last mission. Both flights where from my own squadron 13 TFWS, In the first mission I was escort and the SEAD package did not take off. In the second mission I flew SEAD and the package that did nothing was a strike mission. I checked both missions in the ME to see if I could see anything. I noticed in both cases of the flights that did not take off that they had crazy speed demands in there flightplans. LIke having to fly wiht 400,000 knots. Mayby that's why they didn't take off?? Have one mission included due to size. Falcon over Caucasus_first.miz
  12. RedeyeStorm
    If you are being locked up with stt for missile launch the radar are specifically directed at your plane. So you would get hit with a lot of radar energy sufficient for guiding a missile. So the tone changes. With missile like the AMRAAM which can be launched in TWS your plane is not singled out. So launch and lock warning only starts when the missile radar picks you up and starts guiding.
  13. RedeyeStorm
    Yes I have to do that regularly but not always.
  14. RedeyeStorm
    Well that would explain it Duh. I suppose reading is a lost art at least at my end.
  15. RedeyeStorm
    I am surprised I haven’t read any comments on this. Before the last patch any time a red plane locked a blue plane my RWR started screeching. Now it only starts screeching when I am actually being locked up. Very grateful for that.
  16. RedeyeStorm
    Yes Quaggles mod is running. In Saved games it adds the scripts data.lua file. Saved Games\InputCommands is also there including your F16 joystick default.lua. So in my book it ‘should’ work. There is no InputCommands error in the log. Will enable Quaggles logging for my next try. I haven’t modified your lua files in any way. There is nothing wrong with the commands. As a work around I added them in the original ED default.lua and they work. So that I believe is not it. I am running open beta and standard a few mods. VR reshape, Tazz smoke and labels. I cannot see how that should be an influence. Those mods are applied to DCS main folder and not Saved Games folder. Further more I manually changed/added default.lua file for a few modules that I apply with JSGME to the DCS main folder. This does not include the F16. It didn’t make any difference with these mods enabled or disabled but I thought I mention it just in case disabling with JSGME does not remove them completly.
  17. RedeyeStorm
    Okay I am officially stumped! I wanted to add the laser command, just like Bones1014, but the only F16 command in the customs menu was the stores config switch that I had already programmed. That is not right, it should be way more. I disabled all mods, ran repair but the community keybinds do not show up. As said previously the data.lua is present but does not seem to merge with the official keybinds. Anybody any ideas? PS when I copy the relevant lines out of your default.lua and manually add them to the original default.lua the commands work.
  18. RedeyeStorm
    Yep me too and no repair or rearming of the bird. Only fresh planes will do!
  19. RedeyeStorm
    Thanks man that is fast!
  20. RedeyeStorm
    For some reason the random civilian an militairy traffic is not spawning for me. Am I the only one? Rest of the mission works fine though.
  21. RedeyeStorm
    Hi I have that at times as well and not connected to having Viacom running when updating. Solution search your folder in save games for export.lua. You will find two. One will reside in Viacom folder leave that one alone. Delete the other one and problem is gone. DCS wil rebuild the export.lua so no problems there.
  22. RedeyeStorm
    Hello, I am trying to use your files with the F16 but no luck. Quagles loads fine with OVGME (I have his data.lua in the scripts folder of Saved games) but it doesn't load any of the commands in any module. The logs show nothing event logging set to true in Quagles. May not be something on your end but if not then Quagles work may no longer be functional?? Or it's my brain that is shortcircuiting. Never mind. As soon as I loaded into a module the keybinds where there. dcs.log
  23. RedeyeStorm
    Well personally I have no issues but do you guys know that in the ‘specials’ menu you can select the option to steer with the rudder.
  24. RedeyeStorm
    Can confirm. The Huey is not identfied I. The control panel for me.
  25. RedeyeStorm
    Can confirm that the Viggen is not recognised but I can use it with VIACOM. When I use the manual radio though it uses UHF so prety close range. The presets work without problem. In the CTR+ALT+C window I have Multi selected. In DCS no easy comms.
×
×
  • Create New...