Jump to content

rwbishUP

Members
  • Content Count

    159
  • Joined

  • Last visited

About rwbishUP

  • Rank
    Member
  • Birthday 08/25/1980

Personal Information

  • Flight Simulators
    DCS world, BeamNG, Run8
  • Location
    US, WV
  • Interests
    Railroading, Flight, Electronics, Radio Comms
  • Occupation
    truck driver,coal miner

Recent Profile Visitors

3834 profile views
  1. Trust me, you'll get it, even without the spring mod. I fought and fought against myself trying AAR. Then I finally went by RedKites tutorials for AAR, and after a very short time I was connecting with the boom and drogue for a couple seconds. I got used to being so close to the tanker and relaxed and now it's pretty natural, especially fueling the Viper. The Tomcat took me a little longer, then I turned off Jesters mic..... Good to hear that the springs worked out for ya, I still want to get a premium quality HOTAS, but it's just not a big priority. But since I did the mod to my x56, an
  2. I've ran through 10 scenarios, Jester has refused to lock the contact in 9 of them, optimal acquisition conditions. This is what I am experiencing, I'm getting same performance from turn rates as before the patch. I'm not trashing the module, I was only sharing my feedback. When I try reviewing a track that involves the Tomcat, it doesn't repeat the flight that I did. But I know this is with the strange behavior of the track replay tool, it does weird stuff with a lot of the modules. I'm working on numbers and clips to share from in game and TV. I'll remove the previous post until I get them r
  3. Autostarting the Hornet from any parking spot, in Nevada map @ Tonopah Test Range Airfield. Returns error: "Right Engine RPM Failure: Auto Start Stopped" The right engine actually starts, but autostart is terminated from this point on. Tried at other airfields in NTTR Map, and auto start works normally. Included zip file with 2 track files, DCS log file and screenshot of strange shadow copy of unit, after moving it to a different location. Cannot interact with the shad
  4. Can't stop flying it, beautiful addition to DCS. Thank you ANUBIS!
  5. Still no patch for flight model and missiles being junked. Seems like that would be pretty important, right?
  6. Was curious where, if any, in my DCS root folder. Could I find the data to set up cockpit parameter, argument ranges and indication triggers? i.e. I'm wanting to set some triggers based on the pilot turning on or off the radar. And are these parameters universal, or different for each AC?
  7. I have experienced this same thing. And from what I gathered, it was only when I tried to go back and do some of the older and original training missions. I have loaded into some old TMis and not been able to use throttle, control surfaces, etc.. But it varies through some of the older missions. Never could figure it out, only way I got it working. I loaded the file to ME and removed the aircraft completely then re-added.
  8. So, is MOOSE zone class broken? still can't create polygon zones, tried with late activated unit. sample polygon zone missions included in MOOSE Missions, not working either.
  9. So the F-14 is thoroughly junk for the time being. It's like trying ACM at 50kts in a c-47 skytrain. Like loading down a '94 Ford Fiesta with the only girls that were down to have an orgy (350 on the front hoof), then road racing a zx9r. And, the lack of jesters radar acquisition skills are even worse. He couldn't lock up a windows 95 computer! And even without jester, the radar has a timed sequence it goes by, that makes it completely blind. It just drops every contact at once, for about a minute. wth happened
  10. thanks for the help, folks. I don't fly my viper mod very often, and couldn't find anything about the mprs boom issue because I have really never used it in one of my missions. Was just trying some different combos out, thanks again.
  11. I can't get a response from the kc135mprs, when I'm flying the F-16. I've tried uhf and vhf freqs. Am I doing something wrong, maybe?
  12. Thought my mods had jacked something up, would say they'll get it fixed pretty quick.
  13. update: Seemed to be causing an error when calling a particular livery, replaced the Air Vietnam, and oddly started working Thanks for the reply @Highwayman-Ed, Tried it, still just defaults to solid white skin for all of them note: also found this in log file 2020-11-15 20:32:56.414 ERROR Lua::Config: load error livery = { {"Airbus_A320", 0, "airbus_a320_AAS.dds",false}, {"Airbus_A320", 1, "airbus_a320_b.jpg",true}, {"Airbus_A320", ROUGHNESS_METALLIC, "Airbus_A320_RoughMet.dds",true},​ {"Boeing_Metall", ROUGHNESS_METALLIC, "Boeing_Metall_RoughMet.dds",true}, } name = "Air Asia HS-B
  14. This is the included "Zone Polygon" sample mission from MOOSE, the log file and a screen cap that shows that the zone smoke isn't there. ​ 2020-11-15 04:49:40.649 ERROR SCRIPTING: Mission script error: [string "C:\Users\Bishop\AppData\Local\Temp\DCS.openbeta\/~mis0000077C.lua"]:2: attempt to index global 'Include' (a nil value) stack traceback:
  15. spawning air traffic normally, but no matter which way I script it, never uses random liveries, any idea what I'm doing wrong? local a320=RAT:New("RAT_a320") local a320skins={"Turkish Airlines TC-JUJ", "Vietnam Airlines VN-A308", "cebu pacific RP-C4107" } a320:SetTakeoffAir() a320:Spawn(5) a320:Livery(a320skins)
×
×
  • Create New...