Context3D has no field __clear... ... except it definitely does

[THEkatinamicrowave]

I've been trying to compile Codename Engine August (referring to v1.0.1) for a while now and I've gotten every library installed on their most-likely version at August's launch. it's so close to being workable, but I currently have a bug (in my opinion) with this. I'll put the output of building here.

PS D:\cne> lime test windows
[ BUILD INFO ]
Haxe Version: 4.3.7
Target Platform: Windows
Build Date: 2026-07-08 14:53:18

D:/cne/.haxelib/openfl/git/src/openfl/display/BitmapData.hx:3222: characters 12-19 : openfl.display3D.Context3D has no field __clear
D:/cne/.haxelib/openfl/git/src/openfl/display/_internal/Context3DDisplayObject.hx:44: characters 12-19 : openfl.display3D.Context3D has no field __clear
D:/cne/.haxelib/openfl/git/src/openfl/display/BitmapData.hx:3222: characters 12-19 : openfl.display3D.Context3D has no field __clear
D:/cne/.haxelib/openfl/git/src/openfl/display/_internal/Context3DDisplayObject.hx:44: characters 12-19 : openfl.display3D.Context3D has no field __clear
D:/cne/.haxelib/lime/8,1,2/src/lime/system/Sensor.hx:15: characters 24-62 : Unknown<0> cannot be constructed

For some reason, this is displaying twice, but the main issue I'm focusing on is Context3D having no field __clear. Except it does. I checked openfl/display3D/Context3D.hx and it very much does have the field __clear()

@:noCompletion private function __clear(useScissor:Bool, red:Float = 0, green:Float = 0, blue:Float = 0, alpha:Float = 1, depth:Float = 1,
			stencil:UInt = 0, mask:UInt = Context3DClearMask.ALL)
	{
		__flushGLFramebuffer();
		__flushGLViewport();

		var clearMask = 0;
		// etc...

Unfortunately for openfl, source/openfl/display3D/Context3D.hx removes the __clear() function for some reason even though it just kills openfl. Unsure what to do about that. Should I just add it back or what?

[r6915ee]

There is issue #904 from a couple of months ago that details the same issue with that method. That being said, I think it might be safe to add back the method? I'm not quite familiar with how OpenFL works internally, so I can't really say much here.