Nagilem

I am finding the CCIP piper to be very inaccurate. 1. After lining up the fall line on the target, and right as the cross comes over the target, the piper will sometimes jump significantly. Even with AGR mode selected. 2. Any minor tilt - less than 1 degrees of AOB, and the bomb falls way off regardless if the piper is actually over the target. I thought the point of a continuously computed impact point was to correct and show where the bomb will land, even with some minor AOB dialed in. 3. I also find bombs seem to always fall short - the heavier the bomb the more I have to compensate with the piper past the target to get the bomb on target. I know its supposed to be hard, but this seems erratic. I used to be able to hit vehicles easily with Mark 82s, Not so much anymore.

@Hollywood - Thank you!

Hi Greyman, Thanks for the idea. I don't have anything set on the config tab of Viacom pro for custom DCS path. The path is the standard path - C:\Program Files\Eagle Dynamics\DCS World OpenBeta. None of the options for that are checked.

Sorry Max - you're right. Probably should have put it over there. Apologies. I can resubmit over there if that would be easier. Nothing seems to be broken, but this just keeps coming up in the log a couple of times every 10 seconds. As I said, I've removed everything from the export.lua file except viacom and am still getting the issue, so I know this isn't a conflict with my other export hooks. I also went the other way and removed the viacom hook line with everything else left as is and the error disappears. I have also renamed the viacompro.export.lua file to get a fresh version in the scripts folder, and that had no effect.So I dont think the hook file is corrupt, unless my whole installation is corrupt. I canl try a reinstall as my last resort. Would rather not do that if this is a known issue.

having issues pop up in DCS log file - 2020-07-02 23:27:53.713 ERROR Lua::Config: Call error LuaExportAfterNextFrame:[string "C:\Users\user1\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:164: bad argument #1 to 'find' (string expected, got nil) stack traceback: [C]: ? [C]: in function 'find' [string "C:\Users\user1\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:164: in function 'Flush' [string "C:\Users\user1\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:87: in function 'AfterNextFrame' [string "C:\Users\user1\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:237: in function 'LuaExportAfterNextFrame' [string "C:\Users\user1\Saved Games\DCS.openbeta\Scripts\SimShaker-export-core\ExportCore.lua"]:62: in function 'SimLuaExportAfterNextFrame' [string "C:\Users\user1\Saved Games\DCS.openbeta\Scripts/SimShaker.lua"]:517: in function 'PrevLuaExportAfterNextFrame' [string "C:\Users\user1\Saved Games\DCS.openbeta\Scripts/TacviewGameExport.lua"]:65: in function 'LuaExportAfterNextFrame' [string "C:\Program Files\DCS-BIOS\dcs-lua\BIOS.lua"]:90: in function <[string "C:\Program Files\DCS-BIOS\dcs-lua\BIOS.lua"]:83>.I went ahead and removed everything but viacom pro from my export lua file and I still get this: 2020-07-02 23:38:48.160 ERROR Lua::Config: Call error LuaExportAfterNextFrame:[string "C:\Users\user1\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:164: bad argument #1 to 'find' (string expected, got nil) stack traceback: [C]: ? [C]: in function 'find' [string "C:\Users\user1\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:164: in function 'Flush' [string "C:\Users\user1b\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:87: in function 'AfterNextFrame' [string "C:\Users\user1\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:237: in function <[string "C:\Users\Rob\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:236>.I've renamed my viacompro.export.lua file to old to get a new one generated and ended up with the same error. Anyone know how this can be resolved?

Bump

Not sure here, but I thought at one time, you could turn off the TAWS for nape of the earth flying and not getting the 'pull up' or 'roll right' betty calls. I went into HSI-->Data-->AC--> and unboxed TAWS, but still get warnings in the hud and betty giving me instructions. Did this ever work? Am I misunderstanding its full function? TAWS track.trk

What I have noticed is that you have to have the TGP as SOI before you hit WPNDSG for the pod to move to the WP. Boxing the WP on the HSI doesnt seem to be required.

Ok thanks. Let me try again.

Really enjoying the SC features but I find that I cannot get the 'proper comms' down to get a grade when coming through marshal, and if I want to practice trapping by staying in the pattern, I mostly don't get LSO calls or a grade. For marshal - 1. Call inbound at 50nm 2. Call See you at 10 3. Call overhead (Auto) - get signal charlie 4. Have tried calling commencing and not - neither one seems to impact my grade 5. Call ball at .75 miles after IFLOLS comes up - receive 'roger ball' I get no correction calls and usually get the improper comms procedure message. Not sure what I am missing. For staying in pattern - I usually take off, stay dirty after takeoff, climb to 600 and start the pattern. I make ball calls at .75 and get 'roger ball', but no lso calls and no grading message. Do I need to exit the pattern to get graded? I've read the manual, and have not seen any specifics that say what is required for proper comms. Any thoughts will be much appreciated.

Ok. Did something interesting. I went into the commondata.lua file and cleaned all text out except the two top lines that set the module, and the very end line closing out the module and the errors went away. I assume that file is about getting exporting instrument information if I had need of that data for gauges or dials that are physical / mechanical in nature. Is that true?

Ok. I replaced the commondata.lua file in the appdata area with your code. That caused a different error with the util.lua. Pulled your version down of that file and now getting the error below - 2020-06-05 15:28:09.257 ERROR Lua::Config: Call error LuaExportAfterNextFrame:[string "C:\Program Files\DCS-BIOS\dcs-lua\lib\Util.lua"]:122: attempt to index local 'value' (a nil value) stack traceback: [C]: ? [string "C:\Program Files\DCS-BIOS\dcs-lua\lib\Util.lua"]:122: in function 'setValue' [string "C:\Program Files\DCS-BIOS\dcs-lua\lib\Util.lua"]:753: in function 'v' [string "C:\Program Files\DCS-BIOS\dcs-lua\lib\Protocol.lua"]:169: in function 'step' [string "C:\Program Files\DCS-BIOS\dcs-lua\BIOS.lua"]:85: in function <[string "C:\Program Files\DCS-BIOS\dcs-lua\BIOS.lua"]:83>. I am using DCS bios for some arduino boards for a F-18 UFC and Right panel. Would reverting to an earlier version of DCS-BIOS be worth it? I use VR so getting more data out of DCS for airspeed and attitude for gauges isnt really necessary. The commondata.lua looks to do just that. Any way to disable those features I dont need? I play alot of MP so these errors are concerning since there are plenty of other issues in MP without having controller issues.

Hi BlackLibrary - where would I download that from? Git?

Anybody have ideas on why I keep seeing this error in my dcs.log? I am running DCS-Bios v0.10. This happens in empty missions as well as populated ones. 2020-06-05 05:05:45.748 ERROR Lua::Config: Call error LuaExportAfterNextFrame:[string "C:\Users\Rob\AppData\Roaming\DCS-BIOS\Plugins\module-commondata\CommonData.lua"]:26: attempt to index local 'selfData' (a nil value) stack traceback: [C]: ? [string "C:\Users\Rob\AppData\Roaming\DCS-BIOS\Plugins\module-commondata\CommonData.lua"]:26: in function 'v' [string "C:\Program Files\DCS-BIOS\dcs-lua\lib\Protocol.lua"]:169: in function 'step' [string "C:\Program Files\DCS-BIOS\dcs-lua\BIOS.lua"]:85: in function <[string "C:\Program Files\DCS-BIOS\dcs-lua\BIOS.lua"]:83>.

Wags video shows one must deselect SLAM on the stores page to get the DPOD to show up on the MFD. If you have another SLAM on the jet, it forces a GPS realignment when reselected. Is there any way to see the video without deselecting the next SLAM? Also, after firing the first SLAM, the next SLAM is not automatically selected - I have to manually STEP to the next missile to fire. Is that correct behavior?

Having the same issue

@Rescue - YES! I cant believe I missed that icon for so long! Thank you.

Opening either a new mission, or an existing mission, I see the options to put a new SC in the mission, can place the object along with an Arleigh Burke, but do not see the SC when I zoom into the group. All I get in full zoom on the ME is the icons for the carrier and destroyer the way they were in the old ME. Updated fully to latest OB patch, and when I enter the mission, I see the new carrier with all the techs running around on the deck. I also can interact properly with the SC in both SP and MP. Is there some setting I am missing?

Anybody know where I can find info on dedicated server settings that can be added to the autoexec.cfg? looking to improve networking and performance but unsure what options exist that can be leveraged. Thanks in advance for any help!

I mapped idle on/off to the fingerlift pullback button on the throttle. Works like a champ.

I have intermittently had the same experience.

Two things - make sure the windows Firewall has the ports open that you need on the hosting machine, and use chrome or firefox to connect to it, even locally. You should be able to connect to the dedicated server using the local browser. Until that happens, the rest is immaterial.

Definitely would order. Id be curious on price and a way to mount to throttle that doesn't require the table top arms.

First, thanks ED for providing this module. I have had months of enjoyment flying! My preference would be to get some of the main components fixed or finished first. 1. Fix the VR issues such as one eye blinking, one eye projection of clouds / iights, etc. 2. Fix many of the quality of life bugs - ground guns sometimes shooting high; entering laser codes changes other UFC items like DL code or bomb quantity; Lots of others 3. I'd like to also see all of the hotas functions added to make controlling the jet less about touching OSB buttons during flight 4. Then adding new features I don't really care if you call it EA or not, I just want to see some of the base stuff actually getting fixed first so we can continue to enjoy what is in game already. Id also be willing to forgo any further plane updates if we could see the graphics engine revamped to be more efficient and perform better in VR. Just my $.02 - that and 6 bucks *might* get you a good cup of coffee. Thanks again for all you are doing!

@stickman - I would recommend it but you will need a fast CPU like an 8700k or 3700 and at least a 1080ti or higher card to drive the game with decent resolution and without stuttering. You can get away with lower, but then the quality and experience will also lower. Headsets are all personal choice. Rift S is probably the best for the money, but then spend the money on a better GPU that you save in buying that headset. I've heard the reverb is also good. I also agree with Panton41 - its not crystal clear, but the immersion is amazing. I would def never go back to flat screen.