JATAC Sound Error in the new patch

[ronht]

I just noticed this error in the "In the Weeds" mission after replying to the "Advise when ready for remarks and further talk on" call.

 

 

If you reply to that, the JATAC continues on normally, there just isn't any audio at that point.

 

Sorry for the quality of the pic, I had to put it in windows mode to get the screen shot.

[dantron]

I'm having a similar issue with the "In the Weeds" mission but I'm getting a slightly different error.

 

wMessage::buildSpeech() -> luan handle() call error: [string "./Sounds/Speech/NATO.lua"]:738: table index is nil !

 

I've had a look at line 738 of the NATA.lua script file and I'm must admit, I'm over my head...

 

Is there a fix for this?

 

Is anyone else experiencing the same error with "In the Weeds" or any other mission?

[Jona33]

Speed made a fix. Look in the mods and apps section.

[Speed]

Speed made a fix. Look in the mods and apps section.

 

Sorry, I should update that thread, that fix I made was for 1.1.1.0. ED made the same fix as I did in patch 1.1.1.1, so if you're updated to 1.1.1.1, you shouldn't have that problem any more.

 

As for the problem reported by dantron on January 9, I will look into it. That problem, like most Lua errors, will probably be fixable.

[Speed]

I'm having a similar issue with the "In the Weeds" mission but I'm getting a slightly different error.

 

wMessage::buildSpeech() -> luan handle() call error: [string "./Sounds/Speech/NATO.lua"]:738: table index is nil !

 

I've had a look at line 738 of the NATA.lua script file and I'm must admit, I'm over my head...

 

Is there a fix for this?

 

Is anyone else experiencing the same error with "In the Weeds" or any other mission?

 

Ok, Dantron, I did find a problem with their Lua logic in this file, but I need to make sure some things first:

1) Is that a clean, unmodified, patch 1.1.1.1 version of NATO.lua?

2) If you can reproduce this problem, please upload your dcs.log immediately after you get done flying the mission where this problem occurred.

 

Technical discussion and how to fix this problem yourself:

 

 

The error in their logic is that they are not catching the case of displayTypeId being equal to nil. What is odd about the problem with their logic is that I would expect the error to occur at line 736:

if typesCounter[displayTypeId] == nil then

If the error is going to occur at line 738, then here at line 736, the code is asking for the value of a table at the index of nil. I had thought that that would generate a Lua error, but it looks like it doesn't. Instead, the error occurs at line 738, where they try to set the table value at an index of nil:

typesCounter[displayTypeId] = 1

I guess that perhaps Lua only generates an error when you actually try to set data in a table at a nil index, and just returns nil if you request data in a table at a nil index.

 

So to fix this yourself, make this change:

 

Original lines 733 to 741:

							if displayTypeId == nil then
								base.print('Warning: Index for airdefence unit \"'..typeName..'\" missed !')
							end
							if typesCounter[displayTypeId] == nil then
								typesQty = typesQty + 1
								typesCounter[displayTypeId] = 1
							else
								typesCounter[displayTypeId] = typesCounter[displayTypeId] + 1
							end

 

NEW, fixed lines 733 to 742 (one line added):

							if displayTypeId == nil then
								base.print('Warning: Index for airdefence unit \"'..typeName..'\" missed !')
							else
								if typesCounter[displayTypeId] == nil then
									typesQty = typesQty + 1
									typesCounter[displayTypeId] = 1
								else
									typesCounter[displayTypeId] = typesCounter[displayTypeId] + 1
								end
							end

So the lines 736 to 741 will no longer execute if displayTypeId is nil. That should fix that particular logic error, but I haven't looked to see if there will still be another issue further down in the logic.

 

 

 

Edited January 19, 2012 by Speed

[brydling]

I just got this last error too. Clean unmodified version of NATO.lua ver 1.1.1.1.

[Tailgate]

I had a similar index error in the second mission of the Georgia Hammer campaign when communicating with JTAC. Fresh install 1.1.1.1