20,741
edits
Talk:Switching default texture format to DDS: Difference between revisions
Jump to navigation
Jump to search
m
Talk:Switching default texture format to DDS (view source)
Revision as of 14:36, 6 September 2014
, 6 September 2014→Proposal for a change input format "on the fly" in the texture format
(svg for liveries - hmmmm....) |
|||
| Line 54: | Line 54: | ||
:Cheers | :Cheers | ||
:--[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 10:30, 6 September 2014 (UTC) | :--[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 10:30, 6 September 2014 (UTC) | ||
:: Gijs can probably help clarify things a little here, he mentioned several times on the forum that he's been using SVG for liveries IIRC. Obviously, a SVG file has "layers", that need to be rasterized each - with Canvas that means, that each layer becomes a "group". SVG parsing does happen in scripting space, but should normally only happen during intialization and not at run-time. Otherwise, all the groups/layers are pre-created and put into C++ data structures (CanvasElements) and directly handled by ShivaVG. | |||
:: If you have doubts about the performance of Nasal/Canvas please post your code so that we can take a look - if you're right and your code is sufficiently optimized, then we can still use the [[Built-in Profiler]] to see why your code is triggering slow Nasal/Canvas code paths. | |||
:: Also, it would help us if you could tell us '''exactly''' what aircraft/features you're referring to with regard to "I already see a decrease of fps" - there are varying examples of Nasal/Canvas code in FG, and generally only TheTom's code is sufficiently optimized - code like the [[NavDisplay]] is still relatively unoptimized, and even more so the [[Avidyne Entegra R9]] code is not particularly optimized but doing a ton of stuff in Nasal that '''must''' be slow. Even if you're right, Canvas being "slow" now doesn't have to mean that Canvas will remain "too slow" in 2-3 release cycle. | |||
:: 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) | |||