Latest update 0.9.8.e

[Alienhead]

In editor everything looks as it should.  In run mode I get this.

I fear all updates.

 

[Josh]

It says there is an error on line 347 of uagcontroller.lua, and the "mesh" field of an object is nil.

[Alienhead]

Yes I read that. Problem is the code and model was fine before update. There's only 2 models that even show up ( as the screenshot shows ).  I thought the screenshots clarified the problem.  

The order of things - 

• Everything worked fine
• Updated to lastest
• Nothing loads and error pops up.

 

[Josh]

Can you please upload a project I can test? I do not know of any changes that would have caused this, so I do not know where to look unless I can produce the error on my computer.

[Alienhead]

Here is the working code prior to last update.

 344        self.world = self.entity:GetWorld()

 345       self.mesh = LoadModel(self.world, self.playerModelFilenname)

 346       --self.mesh = Model(self.mesh) 

 347        self.mesh:SetCollisionType(0)

[Josh]

 

1 minute ago, Alienhead said:

Here is the working code prior to last update.

 344        self.world = self.entity:GetWorld()

 345       self.mesh = LoadModel(self.world, self.playerModelFilenname)

 346       --self.mesh = Model(self.mesh) 

 347        self.mesh:SetCollisionType(0)

This helps a little bit. The model file format version was incremented because some new information was added. Maybe your project does not have the current Lua binaries?

[Alienhead]

I use update project like everyone else.   Don't know why I wouldnt have updated binaries?  My project worked just fine 45 mins ago, before updating to latest.

[Josh]

Can you upload the model file that is causing the problem?

[Josh]

You can send it in a private message if that is needed.

[Josh]

It looks like I failed to upload the required Lua binaries in the standalone update. The editor is saving a slightly different scene file format, the previous build cannot load. Sorry for the trouble, it is updated now.

[Josh]

New thread here. It's not a good idea to post a new bug report in another topic that has been solved: