Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some binary files missing sources. #7

Closed
shadowmint opened this issue Sep 21, 2012 · 7 comments
Closed

Some binary files missing sources. #7

shadowmint opened this issue Sep 21, 2012 · 7 comments

Comments

@shadowmint
Copy link

Some binary chunks (Torque 3D.exe) are missing source files. '

eg.
[Torque3D] grep "Would you like to generate a project" * -R
Binary file Torque 3D.exe matches

@ScottBurns-GG
Copy link
Member

I'm not quite following, could you be more specific? Are you referring to the projects not being in there? That's intended if that's the case. The generateAllProjects.bat must be run on a fresh clone or download of the zip. Our installer did this previously as part of the install process but since this is a raw repo it is now a manual step.

@DavidWyand-GG
Copy link
Member

I believe you are referring to Torque 3D.exe at the root of the repo -- the Torque Toolbox? The sources for the Toolbox had to be left out of this initial release. It is built on a commercial version of Qt, and an old one at that. We do intend on releasing the source code for the Toolbox after I convert it to use the latest open source version of Qt.

Does that answer your question?

@shadowmint
Copy link
Author

Yes, that's what I was referring to.

It just seemed a little strange to 'open source' something and then leave binary chunks in the repo with no source code for them (especially when they're critical components; eg. you can't easily generate a project without using the Torque Toolbox).

...but if you're planning on releasing the source for the toolbox later, that's awesome. Could you possibly push an update into the README making it more obvious what other (if any) components the source code is not currently available for?

@DavidWyand-GG
Copy link
Member

Even without the source to the Toolbox, people can still make their games, simulations, etc. just as they could with the retail version of T3D 1.2. The source to the Toolbox will come. We just didn't feel it was necessary to delay the MIT license release of the engine over it.

@dottools
Copy link

To avoid confusion I think the Toolbox executable should be renamed to Toolbox.exe instead of Torque 3D.exe.

@setlec
Copy link

setlec commented Sep 21, 2012

agreed.

@DavidWyand-GG
Copy link
Member

The Project Manager now replaces the old Toolbox. It is open source and is available here: https://github.com/GarageGames/Torque3D-ProjectManager with compiled versions that include all necessary libraries in that repo's Downloads section.

Azaezel referenced this issue in Azaezel/Torque3D Jun 16, 2014
Areloch added a commit that referenced this issue Nov 13, 2015
transcription error was messing with addProtectedField for arrays
MAVachon pushed a commit to MAVachon/Torque3D that referenced this issue Mar 7, 2018
…-ride

TODO:
track down where the heck
D3D11 WARNING: ID3D11DeviceContext::OMSetRenderTargets: Resource being set to OM RenderTarget slot 0 is still bound on input! [ STATE_SETTING WARNING GarageGames#9: DEVICE_OMSETRENDERTARGETS_HAZARD]
D3D11 WARNING: ID3D11DeviceContext::OMSetRenderTargets[AndUnorderedAccessViews]: Forcing PS shader resource slot 0 to NULL. [ STATE_SETTING WARNING GarageGames#7: DEVICE_PSSETSHADERRESOURCES_HAZARD]
spam (in release causes lights to flicker()
is comming from
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants