Collada - Support for Camera's sensor Extension (FCOLLADA, Modo401, blender) #32834

Closed
opened 2012-10-09 23:46:18 +02:00 by Philippe Blanc · 12 comments

%%%Add camera's sensor import for to the following Collada extension:

FCOLLADA - http://collada.org/mediawiki/index.php/Camera_FCollada_extension
Modo401 - http://collada.org/mediawiki/index.php/Imager_modo_401_extension
blender - new proposed extension

I am working on an export patch as well.

The patch is straightforward and should integrate nicely with the current blender's Collada code. The only tricky part is how I added support for the tag, which is a little on the hackish side but:

  • work well
  • doesn't disturb the current code
  • can be reused by future Collada extension%%%
%%%Add camera's sensor import for to the following Collada extension: FCOLLADA - http://collada.org/mediawiki/index.php/Camera_FCollada_extension Modo401 - http://collada.org/mediawiki/index.php/Imager_modo_401_extension blender - new proposed extension I am working on an export patch as well. The patch is straightforward and should integrate nicely with the current blender's Collada code. The only tricky part is how I added support for the <param> tag, which is a little on the hackish side but: - work well - doesn't disturb the current code - can be reused by future Collada extension%%%
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

%%%Attached a proof of concept on what it will looks like to export the camera sensor using FCOLLADA, Modo401 and Blender Extension. Modo401 is giving me some hard time:
a) The documentation @http://collada.org/mediawiki/index.php/Imager_modo_401_extension is not really clear about the use of the tag instead of the tag. My previous patch will load the Modo401 extension regardless but I don't have a copy of Modo for testing it.
b) Collada API doesn't seem to provide a way to define and then write a tag with all the needed parameters (name, type). There are a work around by using addExtraTechniqueTextblock but that seem hackish at best (not sure what need to happen for the end of line). More information about that here: https://code.google.com/p/opencollada/source/search?q=addExtraTechniqueParameter&origq=addExtraTechniqueParameter&btnG=Search+Trunk%%%

%%%Attached a proof of concept on what it will looks like to export the camera sensor using FCOLLADA, Modo401 and Blender Extension. Modo401 is giving me some hard time: a) The documentation @http://collada.org/mediawiki/index.php/Imager_modo_401_extension is not really clear about the use of the <imager> tag instead of the <extra> tag. My previous patch will load the Modo401 extension regardless but I don't have a copy of Modo for testing it. b) Collada API doesn't seem to provide a way to define and then write a <param> tag with all the needed parameters (name, type). There are a work around by using addExtraTechniqueTextblock but that seem hackish at best (not sure what need to happen for the end of line). More information about that here: https://code.google.com/p/opencollada/source/search?q=addExtraTechniqueParameter&origq=addExtraTechniqueParameter&btnG=Search+Trunk%%%
Author

%%%ping! If you need me to resubmit the patch or if you have any questions...%%%

%%%ping! If you need me to resubmit the patch or if you have any questions...%%%
Author

%%%ping! any thought? not necessary on the patch itself but at least on the functionality? Should I rework it?%%%

%%%ping! any thought? not necessary on the patch itself but at least on the functionality? Should I rework it?%%%
Member

Added subscriber: @jesterking

Added subscriber: @jesterking
Member

@visualfox, I've started working through open COLLADA tasks. Could you update your patch to current master? I have a hard time getting a good grip of the code, since the source code lines don't seem to match anymore.

I'd appreciate it if you could do the update for your patch as a differential edit. Thanks!

@visualfox, I've started working through open COLLADA tasks. Could you update your patch to current master? I have a hard time getting a good grip of the code, since the source code lines don't seem to match anymore. I'd appreciate it if you could do the update for your patch as a differential edit. Thanks!
Author

@jesterking I will try to do that this weekend. I will have to reset a working environement for it. I may break down the patch in smaller bit.

Thank you for reviewing the patch, I appreciate it

@jesterking I will try to do that this weekend. I will have to reset a working environement for it. I may break down the patch in smaller bit. Thank you for reviewing the patch, I appreciate it
Member

Closed as duplicate of #43298

Closed as duplicate of #43298

Changed status from 'Duplicate' to: 'Open'

Changed status from 'Duplicate' to: 'Open'

Added subscriber: @dfelinto

Added subscriber: @dfelinto

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'

Hi, thanks for your patch.

We are undergoing a Tracker Curfew where we are automatically closing old patches.

If you think the patch is still relevant please update and re-submit it. For new features make sure there is a clear design from the user level perspective.

Hi, thanks for your patch. We are undergoing a [Tracker Curfew ](https://code.blender.org/?p=3861) where we are automatically closing old patches. If you think the patch is still relevant please update and re-submit it. For new features make sure there is a clear design from the user level perspective.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#32834
No description provided.