408
edits
Talk:Switching default texture format to DDS: Difference between revisions
Jump to navigation
Jump to search
Talk:Switching default texture format to DDS (view source)
Revision as of 19:29, 6 September 2014
, 6 September 2014→Proposal for a change input format "on the fly" in the texture format
| Line 60: | Line 60: | ||
:: Tom has already optimized several things, and I am sure we'll see more optimizations. But just making generic statements and stating assumptions obviously doesn't help improve the Canvas system. As could recently be seen on the devel list, we've had a fairly massive issues in the effects subsystem for years, tremendously slowing down effects (and FG as a whole) and even pointing at other subsystems - well informed bug reports are usually also dealt with, but just making generic claims isn't really helping anybody to check the merits of such statements. | :: Tom has already optimized several things, and I am sure we'll see more optimizations. But just making generic statements and stating assumptions obviously doesn't help improve the Canvas system. As could recently be seen on the devel list, we've had a fairly massive issues in the effects subsystem for years, tremendously slowing down effects (and FG as a whole) and even pointing at other subsystems - well informed bug reports are usually also dealt with, but just making generic claims isn't really helping anybody to check the merits of such statements. | ||
:: Thus, it would make sense to use a heavily down-stripped test case, such as texturing the ufo this way to exclude other Nasal code from showing up in the profile. Let us know if you need help doing that. Thanks --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 14:36, 6 September 2014 (UTC) | :: Thus, it would make sense to use a heavily down-stripped test case, such as texturing the ufo this way to exclude other Nasal code from showing up in the profile. Let us know if you need help doing that. Thanks --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 14:36, 6 September 2014 (UTC) | ||
:::Excuse me, I'd insert the SVG format only as a simple example to understand the flexibility of my proposal. Canvas However I find it fantastic and definitely want to be taken to implement some instruments in the G91 we are doing. The basic concept is to clarify whether this proposal makes sense, and it may be the key to solving the problems of compatibility between formats. My proposal is an attempt to have the maximum flexibility in size of all the graphic objects in FGFs and make compatible the simulation environment of FGFs in any context. At this point I ask the question to those who can develop in C ++ for FGFs, what I'm proposing is practicable? And What I am proposing can solve the problem of non-free formats? --[[User:Abassign|Abassign]] ([[User talk:Abassign|talk]]) 19:29, 6 September 2014 (UTC) | |||