Jump to content

fullwoody

Members
  • Posts

    48
  • Joined

  • Last visited

  1. I haven't received an actual crash log yet looking through the regular log I see a lot of DX11BACKEND entries, however DCS just stops responding. Currently I am running a server with a mission built in Caucasus, my buddy can get on a fly just fine, however if I try to switch to his plane, or really do anything I get the "Not responding, close or wait option". I earlier loaded a Syria Scarlet Dawn mission, I was able to get on and fly with no issues. My buddy who is flying on my Caucasus mission could connect, but it froze and crashed while rendering.
  2. AV8B Virus? Attached is a screenshot from windows defender.... any ideas where this would be coming from? or whats going on. all the updates are from ED right
  3. yup. I've also ran into the same issue. AV8B. i haven't tried repairing yet.
  4. Pass a thank you on to the coders working on this already. it was disappointing. But. it was quickly found, verified and obviously fixed. look forward to the fix releasing soon. Like someone else said, the price we pay for living on the cutting edge.
  5. i agree, the hud is very difficult to see now, the quality of the video on the TGP is terrible. same observations about bhot and whot. i noticed the same thing on the hornet as well yesterday. the flir quality was not nearly as good as it was.
  6. the Harrier can jam some of the missiles and was used for Wild weasel missions. I have flown up against several different SAM systems in game with the ECM pod and it made a tremendous difference just as a single ship. with a few others it would make SAM site hunting very effective.
  7. Squadron Name: VUSN Discord: Fullwoody#7087 Contact person Discord ID: Fullwoody#7087 Aircraft Selection: FA18C Pilots: Fullwoody
  8. i've been trying to get this to work..... i must have something set wrong. I have the jet in AG mode. TGP on, laser armed (seemed to have to be on, in the various tutorial videos). i have a predator lasing on 1688. So both my codes are set to that. tgp set to A-G and is SOI. plane set to CCRP, pointing the nose on the target. i hit the cage/uncage button. and it will slave to the steerpoint... and then back. but not lock the laser at all. what am i missing?
  9. Did they include a discount for Hornet owners as promised? if so how do you get that added.
  10. I hooked up my complicated circuit card i built... and tested it and it works as well as DCS-BIOS will allow. however. i will spend some time digging around because i did have it all working with this new version. maybe i can strike gold and get the right combination of libraries and such that i had before. !!curse you hard drive that acted up forcing a reinstall!!
  11. Yea i was able to get things to work great. for quite a while.... apparently though, not so much. i tested it in DCS and it does work. but not in the Arduino serial monitor. It used to work just fine and it was awesome. I don't remember what version of things i had. but yes i would see "MASTER_MODE_AA" or whatever other buttons i had pushed. I sent a message to [FSF]IAN asking him to look into this.
  12. So i just backed mine all the way back to version 0.93 to test it, and its still not working, and that was the last known version i had working...... i'm at a loss at this point.
  13. interesting. i hadn't had a problem until the last 2 or 3 weeks after a fresh install on my desktop. When did this version come out? id used the new version with the webhub thing that installs on the machine and it worked great. however... i'm not sure what the old version was compared to this "new" version. i thought it was like 0.93
  14. I actually did. i hooked up a regular switch and just pulled it through a digital input. It worked fine. I tried several non DCS-BIOS scripts and they all worked just fine. I'm wondering if i have inadvertently got the wrong library or something. I downloaded the version from the instructions on the site. I went through all the instructions multiple times. So i know the USB ports are working, because the regular arduino code works fine. Ive tried multiple Arduino's with no difference. all known good. my conclusion is that it has to be related directly with the DCS Bios Arduino library somehow..... but what that is, i dont know.
  15. IF you dont have DCS installed in the default location. i dont think DCS-BIOS will find it. At the bottom of the DCS Connection page, it should say "If your DCS installation is not shown above, you can manually add the following line to your Export.lua to enable the Virtual Cockpit Connection:" Then below it, it should have the various pieces of code to add to the Export.Lua which is located in: Saved Games\DCS.openbeta\Scripts for Example, mine looks like: BIOS = {}; BIOS.LuaScriptDir = [[C:\Program Files\DCS-BIOS\dcs-lua\]]; BIOS.PluginDir = [[C:\Users"YourUserNameHERE"l\AppData\Roaming/DCS-BIOS/Plugins\]]; if lfs.attributes(BIOS.LuaScriptDir..[[bIOS.lua]]) ~= nil then dofile(BIOS.LuaScriptDir..[[bIOS.lua]]) end --[[DCS-BIOS Automatic Setup]] That just gets pasted into the ExportLua. If not... i would suggest install DCS in the default location to try it then. UPDATED: I have dug into all the files i can find that are code related for DCS Bios. and i cant find anywhere where the file path for DCS is explicitly declared, so it must either be pulling it from the windows registry or some other voodoo like searching the environment variable for program files. However, the export.lua script should(emphasized) be all that you need to get it to work. If that doesn't i would try to contact some of the DCS Bios people on here directly and ask them about it. I'm running in to some weird issues myself that are currently un-explainable.
×
×
  • Create New...