-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in mission.lua due to DCS API getCategory behaviour change #246
Comments
Also needs to be corrected in unit.lua as well. |
Note, I have implemented the changes in this PR locally on top of the 0.7.1 release. #247 Even with those fixes in place, the StreamUnit hangs after a unitGone event. Here is the output from a little python grpc script streaming units. Whenever a "unit gone" event happens, the stream stops. The unit gone is me jumping out of a slot and taking another slot. It only records the unit gone, no other events..
Here is the dcs.log from that time period
the gRPC.log shows more detail about that timeframe...
|
Just came to say that this PR did indeed fix the issue I reported above. I implemented the change in the PR incorrectly. I had changed it to: |
In latest OB patch, the DCS API function getCategory was corrected. It now correctly returns the unit, weapon airbase category depending on the object type the method is used on. Before it always returned the object category.
In the file mission.lua, the lines
local category = object:getCategory()
must be changed to
local category = Object.getCategory(object)
to correctly retrieve the object category.
Currently, we get the error
The text was updated successfully, but these errors were encountered: