unmounted , just raising the wheeled Vehicle by the gizmo . see the spring area open a little

you can see the spring0 animation .

while mounted see the wheel has extended but the animation of the suspension isn't visible .

(vehicle eye)

again the wheels are extended , the animation isn't visible (player eye)

aaaaand THANX :)

All in all it runs very smoothly and looks nice, even on lowest settings, which is much more than i can say for most engines on this toaster.

The asset and package system is enormously useful despite the hastles, which i am using to the max.

All of my porting and assetizing was done by hand, so i haven used the editor asset tools much.

As i noticed the base packages were removed, this makes it much harder for new people to make games or evaluate the engine properly.

In addition the new level editor doesnt have a tab to place map environment entities.

I overcame those since i already had working asset bases to use and copy.

There are also a few bugs, such as players landing cause a crash and so does spawning a particleemitternode.

I also seem not to be able to crouch, idk if thats not related to something else however.

The shape editor also doesnt update the tab data for models neither, making it somewhat useless.

All in all however im pretty satisfied with it and those little issues can be worked around, it has many nice improvements but those little regressions are gnarly.

Looking forward to 4.0.4 and getting more out of this one.

Branch: https://github.com/lukaspj/Torque3D/tree/cinterface-update

The PR seeks to update the CInterface, which was left in order to integrate JavaScript with T3D.

My main issues with the existing solution was that it still used the TorqueScript console for method calls, which is inefficient compared to calling functions directly. Also it didn't really work any more.

Furthermore, this CInterface seeks to transfer the control of method-lookups and the like from the console to the script that interfaces with the engine.

Main issues that needs to be addressed:

Script->Cinterface calls

In the codeInterpreter.cpp, TorqueScript calls the CInterface, this code should be reviewed / verified:

https://github.com/GarageGames/Torque3D/pull/2136/files#diff-5ec52f3c77bc47c45a6b93b21c6f783b

In console.cpp, the CInterface is called before the console is inquired about evaluation of the function call. This should be reviewed / verified:

https://github.com/GarageGames/Torque3D/pull/2136/files#diff-03ce4e39e998227a38fd95067262f6ad

Cinterface->Engine calls

In engineTypes.h, the ValueType of EngineStructTypeTraits has been changed, despite the fact there was a clear reason that it had the original type to begin with. This should be reviewed / verified:

https://github.com/GarageGames/Torque3D/pull/2136/files#diff-da7328c8cb002a64b343c49c865a5cc6

With as big of chunks of development all coming together now, there's bound to be a few rough edges that need a bit of shine before we can put out a right-proper Release Candidate build.

So, I've put together a build just for that, a Pre-RC 4.0 Preview build.

Repo: https://github.com/Areloch/Torque3D/tree/Preview4_0

Windows precompiled: http://ghc-games.com/SC/Preview4_0_bld5_win.zip

Linux precompiled: http://ghc-games.com/SC/Preview4_0_bld5_lin.zip

MacOS precompiled: http://ghc-games.com/SC/Preview4_0_bld5_mac.zip

I'll have linux and mac precompileds up tomorrow.

Known issues/problems:

-Some gui profiles haven't been updated/finalized with the editor dark theme so expect some bits to not match aesthetically, Those'll be shored up this week

-Some ongoing tidbits with forward lighting with PBR materials, as per me and Az's discussion in #dev Majority of the PBR logic works, just be aware that forward/translucent materials are likely to exhibit oddness

-Updated BaseGame UI theme isn't complete, most noteably scaling of the various main menu UIs being shifted to the left. Also need to update the aesthetic of the options menu

-Secondary windows(notably Verve's editor) don't close when you click the window 'x'. To close it atm you need to click the editor menu to close it out

I plan to rapid-fire throw fixes in as they're made/suggested into the preview build so that we can easily just peel them out and PR them to the main repository later.

Feel free to throw down issues noted here, or in the discord

The #4_0-pre-rc-testing channel is the one dedicated to testing and feedback on the preview build.

For anything you feel needs a tutorial or demonstration(with all the new stuff, i 100% know there'll be cases of that, feel free to throw out a suggestion about it in the #tutorials channel as well. Got a pretty solid idea of the must-haves for these, but more ideas is always good.

And remember, it's not even a release candidate, so expect some rough spots. I want to have things largely in a shape for RC by the end of the month so we can give a few weeks to shore up any remaining problem spots and give this bad boy a mirror shine before launch :)

Components

• Mesh Render(Done)
  
• Animation(Done)
  
• Sound Emitter(Mostly Done)
  
• Collision(Done)
  
• Item Rotation(Done)
  
• Camera Component(Done)
  
• Player Physics Controller(Done)
  
• Simple Physics
  
• Rigid Body Physics
  
• Vehicle Springs
  
• State Machine(Done)
  
• Damage/Destruction
  
• Particle Emitter
  

Game Classes

ShapeBase

• Mesh Render
  
• Collision
  
• Animation
  
• Sound Emitter
  
• Fade/Cloak
  
• Damage/Destruction
  

Player

• Same as Shapebase
  
• Player Physics Controller
  

Item

• Mesh
  
• Collision
  
• Animation
  
• Item Rotation
  
• Simple Physics
  

Vehicle

• Mesh
  
• Collision
  
• Animation
  
• RigidBody physics
  
• Vehicle springs
  
• Engine/Control component?
  

Weapon

• Mesh
  
• Animation
  
• Collision(Maybe a separate, simpler version that just raycasts to detect wall penetration?)
  
• State Machine
  

This is a rough starting list. I'll do up some of the other game classes(like turrets) next, but this should be a good block-out point. The logic for the components not yet done can be peeled out of the respective reference Game Class(like the vehicle springs being pulled from the vehicle class)

@Azaezel rigged up a solution to shift stuff over to ditch 'splashes' and use the regular explosion system which is more standard and used elsewhere, so it's handled right. So basically, this is pretty much just a general 'Request for Information' thread for feedback/notions on handling for this sort of thing in the future. Does shifting over all that uncommon stuff to the common explosion class make the most sense? Should the whole thing be encapsulated in a generic Effects/Particles system?

Feel free to throw down ideas on what the best general handling for stuff like splashes, explosions, and other such things triggered by other objects would be.

Final Testing Branch: https://github.com/Areloch/Torque3D/tree/NewBaseGameTemplateFinal

PR itself: https://github.com/GarageGames/Torque3D/pull/1953

Blocking

Note: As this will be the new template base, no other PRs that are script-changing will be merged until this is wrapped and merged in so we're not trying to juggle two paths with this. As such, the faster we can test and finalize this, the faster we can get back to script changes being rolled in.

The new template is solid enough for people to start poking at it and looking for anything that I may have missed. Go ahead, give it a pull, make a new project with it and give it a whirl.

Should have full multiplayer capability, and the new options menu should be working fine.

Known issues that will be corrected shortly:

Screen Brightness menu doesn't change brightness when you adjust the slider, but the brightness does actually change.

Todo:

While Epoxy's proven it can work better than glew, it looks like it's older and not supported compared to Glad, so we're looking at swapping over to Glad for the OpenGL extension tracking and the like. Grab it, fire it up on OpenGL and note any issues or errors as well as your hardware config so we can see if there are any hardware/driver issues that'd cause a problem.

Branch: https://github.com/Areloch/Torque3D/tree/DBPacingWIP

So, the above branch is a WIP testing some cleanup to cut down on the ugly pointer usage, which is to use some functions already in the engine to get the datablock ID and pack it to stream in a cleaner way.

All you need to do is merge it in, and ensure that you don't spot any odd behavior, errors, or stuff failing to reference/spawn. If you do note any issues, please post logs, what objects/datablocks tripped it up.

Pull Request: https://github.com/GarageGames/Torque3D/pull/1785

Compiles, runs, plays. We've noted performance is lower than other platforms, so if you guys can provide additional metrics on differing hardware, we can try and narrow down where the major bottlenecks are. Most of the mac devices just don't have that good of hardware or drivers for OpenGL, but there are no doubt some bottlenecks that can be found and fixed all the same.

The branch is here: https://github.com/rextimmy/Torque3D/tree/d3d11

Follow the standard 'how to test a PR' instructions to pull it down to your local repository an make sure you do a new project to ensure the new engine and template files get copied. Once you get the game fired up, ensure you can switch to the D3D11 driver in the options menu and test everything and make note of any problems.

If you can integrate it into an existing project for a more in-depth test, that's even better.

This implements the full deferred shading pipeline. As there's a few things that need fixing with the DX11 branch that Timmy's still looking into, for the moment we'll push forward on giving the Deferred work a test-over so it can be rolled in first. As far as I or Az are aware of, it's all functional, so it should just be a matter of pulling the changes into a build(preferrable a game build!) and testing everything to make sure it all behaves as one expects.

Known issue: the distance parameter does not currently work as intended, but everything else seems to. Please pull and test by spawning the volume fog in a level, test the different shapes and any fog textures/lighting conditions and note any issues.

This sub-forum is intended to only have threads pertaining to current issues or feature requests that need a fix and Pull Request made, or an existing PR that needs testing before being merged into the engine. For issues, feature requests or pull requests that are deigned to have priority, they will have a thread created in here pertaining to it. This gives a more local place to inform if something is being worked on, or any discussion/inquiries about it.

So, how can you contribute?

There are two main ways.

• If the thread is about an issue, or feature request, you can submit a fix or implementation of it and create a new pull request.
   
  
• If the thread is about an pull request awaiting testing you can pull down and test the PR, and report what, if any, issues you encountered.

This will expedite important issues being resolved, as well as fixes and features being rolled in!

If you're unfamiliar with how to utilize git with Torque for creating or testing pull requests, there's a wiki page that consolidates most of the necessary information here:

How to use git with Torque.

Once an issue has been handled, or the PR has been merged/closed, the thread pertaining to it will be closed. This is intended to keep what needs to be worked on clearer.

If there is an issue, or a pull request you feel needs handling that isn't in here currently, or you feel there's a problem with a previously handled one and it should be revisited, feel free to contact me and let me know so it can get set up in here!

I started work here: https://github.com/Areloch/Torque3D/tree/NFD_WIP , but have so far been unable to figure out how to debug on linux to catch a crash issue with it.

Either debug instructions, or better, someone that's familiar with debugging in linux to pull it down and test it out. Once the issue has been ironed out, it should be ready to PR.