Drive Date 2008/07/14 has compatible drives, however libogc does not allow those.

[Aeplet]

What's the issue you encountered?

D3 and D3-2 disc drives both use the same drive date (2008/07/14). The problem in question is that there are DVD compatible drives with the date libogc uses as its cutoff.

How can the issue be reproduced?

Get a Wii with a D3 (not D3-2) drive, and use something like WiiMC to try to play back a DVD. Due to this function checking for the drive date 2008/07/14 or newer, and D3 (not D3-2) drives using the same drive date, this basically eliminates those drives from being used by apps that use this function.

I don't know a better way to detect DVD support, but it could be potentially discussed.

[DacoTaco]

@Aeplexi : do you have access to a drive with that date that can and can't read dvd's?

[Aeplet]

@Aeplexi : do you have access to a drive with that date that can and can't read dvd's?

In one of my Wiis, or my drive bin probably.

[Aeplet]

Update: Might have to handle D3 differently

[DacoTaco]

Update: Might have to handle D3 differently

and you have an idea how?

[Aeplet]

Update: Might have to handle D3 differently

and you have an idea how?

An "idea" yes, albeit it's not a "great one".

DDDC marks D3/D3-2 as "Maybe" for the compatibility test.
Due to this issue, it does not use the DVD support function in libogc.

Best thing I can think of is to stub (and call another function that also returns "Maybe" in a way, although I don't know how apps would handle that) the DVD support function, and replace it with a new one that handles D3.