Yue

I understand your point of view, but I don't even rock start games so much their efforts to encrypt their game resources, in the end many end up extracting those models for the benefit of the same game ("Modify") and this is allowed for the same users to make modifications to the same game, but this implies if our game becomes famous.

But let's face it, who cares about our assets? this happens, it's because our game is really famous, and in the end it would be good for you to modify it, okay?, as this system is fine, in the end I'll settle for changing the zip extension to pak, data, dll etc.

Any suggestions?, I can't compile.

Only C++?, Not Lua?

It's that part of the problem is Windows 10 and part of Leadwerks, if you download to Leadwerks 4.3 the problem does not happen. Something happened from version 4.3 onwards. At least I feel confident that this will happen to another user, and there are at least two of us who can make noise in this area.

Try to go down from 100% to 75% or 50%, my current screen is 21 inches and my theory is that if it's too big the screen has to go down a little bit more.

In the Mian.lua script I have the following. window=Window:Create(title,0,0,0,1024,768,Window.Fullscreen + Window.Center)

I'll try to emulate the mistake again. And I'll show you the results.... All I did was increase from 100% on windows to 125%.

Look at the nvida options under "Adjust the size and position of the desktop".

Hi, one of the things that fixed the problem in Windows was updating windows. And move all the possible settings of the nvida panel, especially the screen scale, although I'm more inclined to think about Windows updates. Something that should be understood is that in the Main file, it is configured that when the game is launched from the Leadwerks editor, it always goes to window mode in windows, if on the contrary the problem persists when running the distribution of the program I would try as I mentioned before to update windows or look at the settings of the graphics card. Translated with www.DeepL.com/Translator

Once I've thought about the shovel, with what I've learned so far with the joints, it doesn't seem to be so complicated.

Finish Sytem Car on Leadwwerks 4.5

The following diagram shows how I have implemented the chassis, and the movement of the tire but I have no idea how to put in an additional pivot for the steering. sdf

When I take a screenshot with the print key in full screen mode, what happens is strange, i.e. the capture it makes does not coincide with the exact moment of what happens in the scene. When I made this capture the vehicle was in another position on the stage, however the capture is like when the level starts. The same happens when changing the screen resolution, for a moment the vehicle is suspended and then returns to the current position where the resolution change was made. Any suggestions?

I have no idea what they're talking about, but I suppose it would be great to have features that allow us to do that without really understanding how it's done behind the scenes.

"Error: Failed to load model "C:/Users/Yue/Documents/Leadwerks/Projects/Montacargas/Modelos/caja.mdl" Message Debug info. Model Box. caja.fbx

It is now possible to turn the rim, but it does not roll with the engine drive. Script.rueda = nil --entity "Rueda" -- Wheel Script.susp = nil --entity "Susp" -- Spring function Script:Start() self.volante = self.entity:GetPosition() self.dir = Joint:Hinge( self.volante.x, self.volante.y, self.volante.z, 0, 1, 0, self.susp, self.rueda ) self.dir:DisableLimits() --self.dir:SetLimits(-35, 35 ) end function Script:UpdateWorld() self.dir:SetAngle( self.dir:GetAngle() + 100 ) self.dir:EnableMotor() self.dir:SetMotorSpeed(10) end

This continues without working, in which case, the steering axle ("pivot") is the one that moves and not the rim. I welcome any suggestions. Script.rueda = nil --entity "Rueda" --<<< Wheel Dir -- This script atach pivot dir. function Script:Start() self.volante = self.rueda:GetPosition() self.dir = Joint:Hinge( self.volante.x, self.volante.y, self.volante.z, 0, 1, 0, self.entity, self.rueda ) self.dir:DisableLimits() end function Script:UpdateWorld() self.dir:SetAngle( self.dir:GetAngle() + 100 ) self.dir:EnableMotor() self.dir:SetMotorSpeed(1000) end

I've found the solution to this, and the culprit is the wretched Windows 10. After going through screen-scaled GPU scaling, I found the solution to this problem. Windows by default scales to a percentage of 125%, and what you have to do is move this to a percentage of 100%.

I've been given to try out a Leadwerks 4.6 game and I have the same problem. This is regrettable. Understanding that with leadwerks 4.1 and 4.2 I don't have that problem.

All full-screen tests from leadwerks 4.3 to version 4.6 involve an error when trying to run a simple full-screen command. Verification steps. Leadwerks 4.1 Ok full screen. Leadwerks 4.2 Ok full screen. Leadwerks 4.3 Full screen error. Leadwerks 4.4 Full screen error. Leadwerks 4.5 Full screen error. Leadwerks 4.6 Full screen error. I have taken the time to download the update and perform the previous tests, however it is not the first time I do this report so I am not very optimistic that anyone will pay attention and therefore offer a solution, I guess it is because I am not a paying user, or the only bad user that got screwed with this problem. Translated with www.DeepL.com/Translator Windows 10 GTX 1050 OpenGL 4.6