Skip to content

Issues: BoneCrasher/ShirabeEngine

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.

Sign up for GitHub

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

18 Open 2 Closed
18 Open 2 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

GFXAPI::ResourceManagerIntegration: Think abouty ways to enforce the "from-data/from-file" constraints with async/sync and data pointers & memory management
#20 opened Nov 2, 2017 by BoneCrasher
1
GFXAPI::ResourceManagerIntegration: Implement Requests. Each creation request requires a ResourceDescriptor<TResource>-member
#19 opened Nov 2, 2017 by BoneCrasher
@BoneCrasher
GFXAPI::ResourceManagerIntegration: Use requests in the resource manager, but have the engine resource only use the descriptor.
#18 opened Nov 2, 2017 by BoneCrasher
@BoneCrasher
GFXAPI::Subsystem: Implement task builder access for UPDATE
#16 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
GFXAPI::Subsystem: Implement task builder access for CREATE
#15 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
GFXAPI::Subsystem: Implement task builder access for DELETE
#14 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
GFXAPI::Subsystem: Implement task builder access for QUERY
#13 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
GFXAPI::Subsystem:: Error handling/Recovery/Fallback for async load and error cases?
#12 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
ResourceManager <-> Renderer: Integrate to allow access to resources
#11 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
1
Resource-Manager: Implement Hierarchy-Creation and Management (inkl. proper destruction)
#10 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
ResourceManager: IMplement CRUD and Get
#9 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
DX11: Think about builder signature
#8 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
DX11: Handle lost device states or resource issues and fwd to GFXAPI-Subsystem
#7 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
DX11: Implement Proxy Creators
#6 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
DX11: Implement Builders
#5 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
GFXAPI::Subsystem: Implement platform resource handling and make sure to delete everything on close/destroy
#4 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
GFXAPI::Subsystem: Implement subsystem creation for DX11 w/ linkage to DX11 instance
#3 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
GFXAPI::Subsystem: Implement API switch and void* storage of task builder
#2 opened Oct 25, 2017 by BoneCrasher
@BoneCrasher
ProTip! Exclude everything labeled bug with -label:bug.