Jump to content

Recommended Posts

  • 2 weeks later...
  • Replies 135
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Fixed - just download the latest lua from GitHub https://raw.githubusercontent.com/ciribob/DCS-SimpleRangeScript/master/rangescript.lua   Test mission isnt updated yet - but just use the new

I've knocked together a simple Range Script inspired by SNAFU's original here: http://forums.eagle.ru/showthread.php?t=109174   It has the ability to track all bombs / rockets fired at a Trigger Zone

I confirm, the script no longer works Inviato dal mio Redmi Note 8 utilizzando Tapatalk

Fixed - just download the latest lua from GitHub https://raw.githubusercontent.com/ciribob/DCS-SimpleRangeScript/master/rangescript.lua

 

Test mission isnt updated yet - but just use the new script 👍

  • Like 1
  • Thanks 1

Scripts: Complete Transport And Logistics Deployment - CTLD / CTLD Examples - Lots of example of how to use CTLD

CSAR Script - Downed Pilot Rescue / Dedicated Server Script - Automatically launch DCS Multiplayer server at startup

Range Scoring Script - Get scores and counts hits on targets for gunnery or bombs / SimpleSlotBlock - Multiplayer dynamic Slot Blocking Script

 

Projects: DCS-SimpleRadio Standalone - DCS Radio Integration for All Aircraft - NO TeamSpeak Required! :)

DCS-SimpleRadio Troubleshooting Post / DCS-SimpleRadio Free Support Channel on Discord

Link to post
Share on other sites
  • 2 weeks later...

Hi, I've been using the Iron Bombing Range mission that utilizes the rangescript.lua, just realized this morning the bombing accuracy in meters is no longer being reported.  I went back and did a fresh start with the original file from sidekick65 from the DCS User Files download, still no accuracy information being reported.  Is anyone else seeing this?

Link to post
Share on other sites
16 minutes ago, DP Spaz said:

Hi, I've been using the Iron Bombing Range mission that utilizes the rangescript.lua, just realized this morning the bombing accuracy in meters is no longer being reported.  I went back and did a fresh start with the original file from sidekick65 from the DCS User Files download, still no accuracy information being reported.  Is anyone else seeing this?

 

Please, read two posts above yours 🙂

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites

I have updated with the latest rangescript.lua, still seeing the same issue.  Is anyone else experiencing the same?  I'm no expert at with lua, I'll do my best to continue investigating.

 

I lowered the min altitude and that appears to have gotten it functioning.  Further testing has resulted in intermittent reporting of the accuracy.  Will continue to test and investigate.

 

2/20: Lots of testing and have not been able to reproduce and problems, likely just my lack of understanding how things work.  It is part of my standard tools when flying DCS, greatly appreciate the effort to create and maintain this capability for the DCS crews!


Edited by DP Spaz
Update testing results
Link to post
Share on other sites

Further testing of the rangescript.lua I sometimes get this error.. see the attached file.  It appears to be related when at above min bombing altitude to launch bombs/rockets and I enter into zone.  The message appears twice, which seems to coincide with enter zone and exit zone.  I have set range.bombingMinAlt = 1800

 

I'm also finding the following issue:

 

1. strafing zone maxAlt = 1500, the in-zone messages are being displayed well above that altitude.. 3-4k

 

 

Error1.JPG

Spaz NM P51 Cardonville Practice.miz


Edited by DP Spaz
Attached the .miz file
Link to post
Share on other sites
51 minutes ago, DP Spaz said:

Further testing of the rangescript.lua I sometimes get this error.. see the attached file.  It appears to be related when at above min bombing altitude to launch bombs/rockets and I enter into zone.  The message appears twice, which seems to coincide with enter zone and exit zone.  I have set range.bombingMinAlt = 1800

 

Hello,

 

Please attach the mission so that @Ciribob has more information to check the issue.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites

I've attached the .miz file to my previous post.  Appreciate looking into this.  Let me know if you have any questions or need additional information.

 

Some times the reporting works, other times nothing.  I'm just learning lua and scripting so my knowledge and experience at this point is limited. 


Thanks!

Dave

Link to post
Share on other sites

I made some changes to my mission, specifically the size of the zones for the bombing targets.  I thought possibly because they are over-lapping it may be causing the issue.  I reviewed the Iron Bombing Range mission and see how they implemented the zones, so followed with the same implementation.  Unfortunately it did not resolve the issue.  I'm attaching my updated mission and the track file so you can see exactly what is happening. 

Spaz NM P51 Cardonville Practice.miz 210223_Spitz_Cordville_Bomb00.trk

rangescript.lua


Edited by DP Spaz
Attaching my rangetrack.lua file as well.
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...