Godot: Make tscn the default format for better text processors / SVCs compatibility?
Shouldn't the new tscn format be default over the binary scn?
unfa
All 19 comments
I'd be in favour of it yes.
akien-mga
on 9 Mar 2016
+1
Sometimes I forget to use tscn and have to rename it later.
AlexHolly
on 9 Mar 2016
.tscn will work in most cases, but if you are dealing with 3D Geometry it' s usually a bad idea.
I think this should be made optional in the editor settings, or project settings (preferred scene format)
reduz
on 9 Mar 2016
Another (little more trouble some) way would be to show alert message when editor detects that we are trying to save 3d mesh geometry data with tscn.
kubecz3k
on 10 Mar 2016
What is wrong with 3D data in .tscn?
On Thu, Mar 10, 2016 at 6:15 PM, kubecz3k [email protected] wrote:
Another (little more trouble some) way would be to show alert message when
editor detects that we are trying to save 3d mesh geometry data with tscn.—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3996#issuecomment-194899014.
slapin
on 10 Mar 2016
@slapin it's slow to save and it's slow to load (maybe reduz know more reasons why it's not the best idea)
kubecz3k
on 10 Mar 2016
hmm, where are the editor settings stored? I need to be able to set this once, have it affect all new projects, check it into svn, then when the artists pull the repo it is set for them too. If it's saved into AppData that isn't going to work.
captainwasabi
on 8 May 2016
@captainwasabi ~ I guess you should open another issue for this, as it is useless to bloat this one. (i.e. "per-project editor setting" would be a nice title)
bojidar-bg
on 8 May 2016
I think .tscn is just not ready for production yet
On Sun, May 8, 2016 at 10:04 PM, Bojidar Marinov [email protected]
wrote:
@captainwasabi https://github.com/captainwasabi ~ I guess you should
open another issue for this, as it is useless to bloat this one. (i.e.
"per-project editor setting" would be a nice title)—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3996#issuecomment-217739830
slapin
on 8 May 2016
Ah. Fair enough.
On May 8, 2016 4:08:58 PM Sergey Lapin [email protected] wrote:
I think .tscn is just not ready for production yet
On Sun, May 8, 2016 at 10:04 PM, Bojidar Marinov [email protected]
wrote:@captainwasabi https://github.com/captainwasabi ~ I guess you should
open another issue for this, as it is useless to bloat this one. (i.e.
"per-project editor setting" would be a nice title)—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3996#issuecomment-217739830
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/godotengine/godot/issues/3996#issuecomment-217743121
captainwasabi
on 9 May 2016
I think .tscn is just not ready for production yet
Care to argument? Many users are using it for production just fine. It has a couple of bugs of course, but by this logic let's say that "I think Godot is just not ready for production yet" and stop wasting our time.
akien-mga
on 9 May 2016
People use all kinds of stuff for "production". Unless you limit scope you
limit scope of what you say it is true. Godot is not ready to produce 3D
games with complex animations.
.tscn frmat is not ready to be used for 3D scenes. Godot vehicle physics
have very limited use and not ready for real usage. Godot 3D physics is not
ready for complex scenery,
this includes collision system. All that doesn't mean Godot is not ready
for 2D production use, and Godot 3D is good for static scenes and FF7-style
graphics, and if you do
all your 3D animations in "traditional" way (i.e. no animation blending),
and you don't have 10 characters on screen at the same time, it is ready
for production too.
But scene file format is different. You don't want to save your assets to
it and find it breaks or doesn't work right for you, or loses data, as long
as you save any scenery to it.
Whatever the effectiveness there is you should not lose data saving to it
as long as it is produced by Godot editor and tools. This leads to
uncertainty, also you have ..scn which
is bad but works and never lose data. This just prints "don't use .tscn
unless you're ready to lose data", there are known bugs in it and there are
no any reasonable plans about fixing them.
If you feel adventurous, please help with testing, but if you want to store
production stuff, stick with .scn for now.
On Mon, May 9, 2016 at 4:37 PM, Rémi Verschelde [email protected]
wrote:
I think .tscn is just not ready for production yet
Care to argument? Many users are using it for production just fine. It has
a couple of bugs of course, but by this logic let's say that "I think Godot
is just not ready for production yet" and stop wasting our time.—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3996#issuecomment-217865933
slapin
on 11 May 2016
Also, you look depressed. Cheer-up, even though 3.0 is a lie, we all still
have a shred of hope in our hearts.
On Wed, May 11, 2016 at 5:29 PM, Sergey Lapin [email protected] wrote:
People use all kinds of stuff for "production". Unless you limit scope you
limit scope of what you say it is true. Godot is not ready to produce 3D
games with complex animations.
.tscn frmat is not ready to be used for 3D scenes. Godot vehicle physics
have very limited use and not ready for real usage. Godot 3D physics is not
ready for complex scenery,
this includes collision system. All that doesn't mean Godot is not ready
for 2D production use, and Godot 3D is good for static scenes and FF7-style
graphics, and if you do
all your 3D animations in "traditional" way (i.e. no animation blending),
and you don't have 10 characters on screen at the same time, it is ready
for production too.
But scene file format is different. You don't want to save your assets to
it and find it breaks or doesn't work right for you, or loses data, as long
as you save any scenery to it.
Whatever the effectiveness there is you should not lose data saving to it
as long as it is produced by Godot editor and tools. This leads to
uncertainty, also you have ..scn which
is bad but works and never lose data. This just prints "don't use .tscn
unless you're ready to lose data", there are known bugs in it and there are
no any reasonable plans about fixing them.
If you feel adventurous, please help with testing, but if you want to
store production stuff, stick with .scn for now.On Mon, May 9, 2016 at 4:37 PM, Rémi Verschelde [email protected]
wrote:I think .tscn is just not ready for production yet
Care to argument? Many users are using it for production just fine. It
has a couple of bugs of course, but by this logic let's say that "I think
Godot is just not ready for production yet" and stop wasting our time.—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3996#issuecomment-217865933
slapin
on 11 May 2016
something that doesn't exist can't be a lie.. it's just a promise
reduz
on 11 May 2016
Well, I know cake actually probably did exist. But I still can't believe in
3.0
The reasons:
- there is no clear path curent state --- A... B.. C ... ... 3.0, so it is
just plain abstract number when everybody will be happy and grass will be
green again. - while there are people who can do shit, the uncertainty about 3.0, no
pull requests about 3D allowed, no plans shared until Juan
(very busy person indeed) makes everyone happy. While people could
experiment and do things now the current state just forces them away.
I don't think Juan should do that. I just think a few comments from Juan
about what stuff in 3D is going to be accepted now, what is not,
some ad-hoc feature lists, etc. would do a great thing. - Time passes, single-person projects tend do evolve very slowly and people
lose patience. Probably some people could speed things up.
Probably. - There are some great things waiting in uncertainty (
https://www.youtube.com/watch?v=j99vFXPXHHA
https://www.youtube.com/watch?v=c8Cu_VzcL2Y
https://www.youtube.com/watch?v=lMw9gWKq7mQ
https://github.com/slapin/godot-fork/wiki/City-Geometry-creation )
people ask but don't get answers. If there were some big picture... but
only big loss of motivation persists.
On Wed, May 11, 2016 at 5:42 PM, Juan Linietsky [email protected]
wrote:
something that doesn't exist can't be a lie.. it's just a promise
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3996#issuecomment-218480752
slapin
on 11 May 2016
solved by 29177e1e9b2644cfa2d5efe6fcfe2605b84ed68c?
djrm
on 25 Jun 2016
@djrm you are right :+1:
kubecz3k
on 25 Jun 2016
this is already the default, closing
reduz
on 26 Jun 2016
oh you won
reduz
on 26 Jun 2016
Related issues
RayKoopa
·
3Comments
blurymind
·
3Comments
rgrams
·
3Comments
testman42
·
3Comments
Spooner
·
3Comments
Most helpful comment
Care to argument? Many users are using it for production just fine. It has a couple of bugs of course, but by this logic let's say that "I think Godot is just not ready for production yet" and stop wasting our time.