RifTUP! FullHD Oculus DK1 upgrade kit

[wileythecoyote]

Any news laseredge about the 5.9 inch fhd screen?
Can we expect your controllerboard to be available 1st quater of 2014?

[cgp44]

deleted

[cgp44]

deleted

[Inscothen]

Any word on where the parameters are stored? Anyone not using a panel the same dimensions as the DevKit will need to be able to change the dimensions info to have rift content work.

[OzOnE2k10]

Hi, all,

Happy New Year!

I've been taking a long break from the PC and Rift stuff over Xmas / New Year, so it might take me a while to catch up / sober up / remember. lol

OK, finally got hold of the datasheet for the Nexus 7 (2013) JDI panel.
I know this might be a bit naughty, but I don't really care atm...
https://mega.co.nz/#!KlQAQQpK!HQEdDXI5Q ... ujLzFRzjxY

Just for reference...
http://www.panelook.com/TFTMD070021_JDI ... 20734.html

Only problem is, it looks like the datasheet is for the actual Glass panel + driver IC, so I'm not entirely sure the pinout on the last page matches the actual pinout for the FPC connector that the manufacturer uses?

It does give quite a few of the MIPI commands for starting the panel etc.

Maybe the pinout on the last page does match the actual connector? It does look like it has 31 pins on this image...
http://www.panelook.com/images/201311/1 ... pg.big.jpg

The 5-pin LED backlight flex seems to match the photo as well.

The good thing is, it should be possible to get hold of the MIPI cable for the Nexus 7 (2013) / JDI panel.
Once we have a physical panel, it wouldn't take long to find the true pinout of the FPC connector (if it doesn't quite match the datasheet).

I hope that makes sense?

This datasheet is essentially an "OEM" type for the glass panel itself, so may not reflect the pinout for the choice of connector on the back.
The manufacturer likely adds the LED backlight driver at a stage just after the "Glass+IC" stage too.

Could somebody possibly translate the text next to the connectors on PDF page 26 - I think it's Japanese?

@Inscothen - are you talking about the parameters for the different panel types in the Rift SDK?

AFAIK, the SDK has "templates" for various different panel sizes / resolutions.
The last time I checked (many months ago), the source already had a template for the HD Rift prototype panel.
I think all that it does is check the EDID ID string to select the appropriate panel? ie. "OVR0001" for the DK1.

The templates change the warping factors / IPD / scaling stuff I think?
I'll have to have a look at the latest source soon. I'm not sure if one of the Rift guys would want to chime in on this? hehe

@esilviu - Thanks for the link, I'll check out that seller.

@wileythecoyote - I second that - LaserEdge, any news on your board being released in the next few weeks?

@cgp44 - That's some great info there. Using an OLED display would be amazing.
How did you examine the pinouts, were those preliminary pinouts found by tracing the data pairs etc?

Also, how did you find the info on the Hirose connectors? That's usually quite difficult to do unless it's listed on the Web or printed on the connector.

I just found your discussion with Inscothen over on the Oc forum...
https://developer.oculusvr.com/forums/v ... 7&start=40

Definitely a MIPI panel then?

OzOnE.

[OzOnE2k10]

Wow - OLED is suitably pricey then...

http://www.aliexpress.com/wholesale?Sea ... 0101074557

Would be very nice, but quite an expensive option compared to a FHD LCD.
Maybe it would be a fair bit cheaper if you can find them without the digitizer attached?

Also, would a 4.99" panel be a teensy bit small for the DK1?

OzOnE.

[cgp44]

I must have limitied peripheral vision as I've removed the lenses in my rift to compare the screen coverage
with what I see. My conclusion is a 4.99incher is ok, it will cover what I can see.

[cgp44]

Thus a huge breakthrough to go forward ( for me at least).
Hell of a lot of voltages.

#
# ams499qp01 the samsung S4 OLED display
#
# pinouts
#
# receptacle Hirose BM10NB(0.8)-40DS-0.4V(51) (on display flexiboard)
# plug is Hirose BM10B(0.8)-40DP-0.4V(51)
#
# 40 pins @ 0.4mm spacing, 44 pins for the i9500 but 41-44 connected to ground.
#
# mine was a i337 snapdragon 600 (i9505)
# I have scratched the masking black off the flexiboard
# and the wires do seem to be possible fit to the connector pinout below.
#
# ........ top of display, connector to right, facing up
# on i9500 (octa) repair manual header is hea700 pg 97
#
# 3 pins.....#.+39...40+#.. 3 pins
# -4.4V......#.+37...38+#.. 4.6V
# elvss......#.+35...36+#.. elvdd
# .touch Enbl..+33...34+... elvdd_fbs
# .............G.+31...32+ NC
# ..ln2P.......+29...30+ mlcd_rst
# ..ln2N.......+27...28+ err_fg
# ..............G.+25...26+ OLED_ID
# ..ln1P.......+23...24+ vcc 3.0V lcd
# ..ln1N.......+21...22+ elavdd 7.0V
# ..............G.+19...20+ vcc 1.8V lcd
# ..clkP........+17...18+ el_on_1
# ..clkN.......+15...16+ el_on_2
# .............G.+13...14+ G
# ..ln0P.......+11...12+ tsp_sda 1.8V
# ..ln0N.......+9.....10+ tsp_scl 1.8V
# ..............G.+7.......8+ tsp_avdd 3.3V
# ..ln3P.......+5........6+ tsp_vdo 3.0V
# ..ln3N.......+3.......4+ tsp_nINT (via r741 tsp_vdd 1.8V)
# ..............G.+1.......2+ tsp_vdd 1.8V
#

The mystery pins are: el_on_1, el_on_2, OLED_ID, elvdd_fbs.
The error flag and lcd reset can be left hanging.

[cgp44]

tsp is touch screen processor, with a i2c interface and voltages.

[cgp44]

the digitizer is attached somehow to the glass that is glued to the ams499qp01 S4 oled substrate.
On heating it with a heat gun the glue to the fragile sustrate melts first and destroys
the view. You cannot separate these. Break the top layer touch screen, you get the whole unit.

[cgp44]

extracted from perl module Parse::EDID from a summary output via Edid Manager on windows 7.

%myDisplayEDID1 = ( # derived from Oculus Rift DK v1 7inch mobile lcd 1200x800
'serial_number' => 0,
'feature_support' => {
'GTF_compliance' => 0,
'sRGB_compliance' => 1,
'rgb' => 1,
'DPMS_suspend' => 1,
'has_preferred_timing' => 1,
'DPMS_active_off' => 1,
'DPMS_standby' => 1
},
'checksum' => 96,
'serial_number2' => ['SerialRD'],
'video_input_definition' => {
'voltage_level' => 0,
'digital' => 1,
'composite_sync' => 0,
'separate_sync' => 0,
'sync_on_green' => 0
},
'VertRefresh' => '56-76',
'monitor_name' => 'Rift DK',
'established_timings' => [
{'vfreq' => '60','X' => 640,'Y' => '480'},
{'vfreq' => '60','X' => 800,'Y' => '600'},
{'vfreq' => '60','X' => 1024,'Y' => '768'}
],
'max_size_precision' => 'cm',
'monitor_range' => {
'horizontal_min' => 30,
'vertical_max' => 76,
'pixel_clock_max' => 230,
'horizontal_max' => 83,
'vertical_min' => 56
},
'product_code' => 1,
'HorizSync' => '30-83',
'monitor_details' => '',
'standard_timings' => [
{'ratio' => '16/10','vfreq' => 60,'X' => 1280,'Y' => '800'},
{'ratio' => '16/9','vfreq' => 60,'X' => 1280,'Y' => '720'},
{'ratio' => '16/10','vfreq' => 60,'X' => 1920,'Y' => '1200'},
{'ratio' => '16/9','vfreq' => 60,'X' => 1920,'Y' => '1080'}
],
'week' => 24,
'detailed_timings' => [
{
'vertical_sync_offset' => 3,
'bad_ratio' => 1,
'pixel_clock' => '71.11',
'horizontal_border' => 0,
'stereo' => 0,
'interlaced' => 0,
'horizontal_blanking' => 160,
'digital_composite' => 3,
'vertical_sync_pulse_width' => 6,
'horizontal_active' => 1280,
'vertical_sync_positive' => 1,
'horizontal_sync_pulse_width' => 32,
'horizontal_sync_positive' => 0,
'vertical_border' => 0,
'preferred' => 1,
'horizontal_sync_offset' => 48,
'ModeLine' => '"1280x800" 71.11 1280 1328 1360 1440 800 803 809 823 -hsync +vsync',
'vertical_image_size' => 94,
'horizontal_image_size' => 150,
'ModeLine_comment' => '# Monitor preferred modeline (60.0 Hz vsync, 49.4 kHz hsync, ratio 16/10)',
'vertical_blanking' => 23,
'vertical_active' => 800
}
],
'extension_flag' => 1,
'gamma' => 120,
'diagonal_size' => '0',
'edid_revision' => 3,
'EISA_ID' => 'OVR0001',
'max_size_horizontal' => 0,
'max_size_vertical' => 0,
'edid_version' => 1,
'year' => 2013,
'manufacturer_name' => 'OVR'
);

[cgp44]

@OzOnE2k10 I found out it was Hirose connector because I viewed the us$200 plus artifact under
a x14 mag glass along with the online pictures from digkey or some other supplier.
Plus I eventually found a hrs trademark on the connector. Ridges and other geometry stand out for
identification.
However this is academic for me as I am attempting to wire to the testing cables which fit exactly.
I will remove the receptacle connector and solder a wire cradle with 20 wires 0.4mm wire separations. Crazy tiny but
doable under a mag glas with spot gluing (with high temp resin) to stop movement and
flux gel and solder paste.

we now have android jelly bean drivers specfically for the ams499qp01 that confirm
it is mipi. I just needed proof beyond quesswork. serious tragedy it aint eDP, looks like
mipi for mobiles forever. eDP possibly for phablets, but us VRers need small lightweight displays
right against our eyes.

[Quppa]

Could somebody possibly translate the text next to the connectors on PDF page 26 - I think it's Japanese?

Here's my attempt at a translation: http://www.quppa.net/misc/JDI.png

I'm keeping an eye on this thread as I'd like to use one of these high density 7" panels for a carputer. It'd be nice to harness the Nexus 7's display and touch digitiser (the only disadvantage being its portrait orientation), but failing that the KOE LVDS panel looks promising, provided we can actually get our hands on them.

[yunti]

Thus a huge breakthrough to go forward ( for me at least).
Hell of a lot of voltages.

#
# ams499qp01 the samsung S4 OLED display
#
# pinouts
#
# receptacle Hirose BM10NB(0.8)-40DS-0.4V(51) (on display flexiboard)
# plug is Hirose BM10B(0.8)-40DB-0.4V(51)
#
# 40 pins @ 0.4mm spacing, 44 pins for the i9500 but 41-44 connected to ground.
#
# mine was a i337 snapdragon 600 (i9505)
# I have scratched the masking black off the flexiboard
# and the wires do seem to be possible fit to the connector pinout below.
#
# ........ top of display, connector to right, facing up
# on i9500 (octa) repair manual header is hea700 pg 97
#
# 3 pins.....#.+39...40+#.. 3 pins
# -4.4V......#.+37...38+#.. 4.6V
# elvss......#.+35...36+#.. elvdd
# .touch Enbl..+33...34+... elvdd_fbs
# ...........G.+31...32+.NC
# ..ln2P.......+29...30+.mlcd_rst
# ..ln2N.......+27...28+.err_fg
# ...........G.+25...26+.OLED_ID
# ..ln1P.......+23...24+.vcc 3.0V lcd
# ..ln1N.......+21...22+.elavdd 7.0V
# ...........G.+19...20+.vcc 1.8V lcd
# ..clkP.......+17...18+.el_on_1
# ..clkN.......+15...16+.el_on_2
# ...........G.+13...14+.G
# ..ln0P.......+11...12+.tsp_sda 1.8V
# ..ln0N.......+9....10+.tsp_scl 1.8V
# ...........G.+7.....8+.tsp_avdd 3.3V
# ..ln3P.......+5.....6+.tsp_vdo 3.0V
# ..ln3N.......+3.....4+.tsp_nINT (via r741 tsp_vdd 1.8V)
# ...........G.+1.....2+.tsp_vdd 1.8V
#

The mystery pins are: el_on_1, el_on_2, OLED_ID, elvdd_fbs.
The error flag and lcd reset cane be left hanging.

cgp44 - Great progress on the samsung screen. Would the note 3 N9006 screen not be the better size to use at 5.7" rather than 4.9" of the S4?
There are quite a few options of where to locate this from (single orders too):
http://www.alibaba.com/product-gs/15141 ... ality.html

Not sure if the pinout work you have done on the S4 will carry over to the Note 3, or if every screen will be different - (even in the same family of screens)?

Although a 1080p OLED screen would be ideal with the improved lag, I would still be happy with any of the LCD 1080p screens we have discussed earlier in the thread, whatever is easiest to get off the ground and working.

OzOnE2k10- I'm UK based too so happy to come in on any screen order if that helps - will PM you when I get a mo.

[FR3D]

http://www.oled-info.com/samsung-report ... panels-gs5

this one would be fine ...

best regards FR3D

[cgp44]

yunti, no the pinouts for mobile displays are all over the place. You need confirmed
documentation to play with them.

That alibaba site seems to be too cheap to be believable. A third the price of etradesupply?
They are aggregators with silly price ranges (bulk bying does not make that much difference).
Has anyone brought from them?

[cgp44]

Inscothen warping paras in util_render_stereo.h/.cpp No?

[remosito]

http://www.oled-info.com/samsung-report ... panels-gs5

this one would be fine ...

best regards FR3D

latest rumor: production troubles. they cant make enough for S5 massive sales. switching to sharp lcd.

leaving existing production up for grabs!


Please, please, please!

[OzOnE2k10]

Erm, OK, things might be taking a different route again guys (for me at least)...

Daniel Rozsnyo has been in contact again, and is hoping to complete his HDMI / MIPI boards soon.

It should work out a bit cheaper than the Signet FPD offer, and won't have the same minimum order restrictions either.
Also, if we go with the LG or other mobile panel, they will be much easier to get hold of in future (and we'll have the proper datasheets / pinouts / connectors).

So, I'm holding fire on the Signet offer for the time being.
Sorry to anyone who have already shown interest in the Signet offer, but I think Daniel's board will be a much nicer all-round solution in the end.

There's nothing stopping anyone buying the Signet kits still of course.
You'll need to get enough buyers together though, and I think it would have taken quite a while to reach 50 people at this rate.

I know for sure that Daniel already has a few different panels to test (5.5", 5.99" etc.).
I said a slightly larger panel like the 5.99" or a 6.5" panel would be ideal.

We're going for 1080p for now, but if higher-res panels become available in the coming months at a reasonable price, then we can always make an extension board for the different types.

OzOnE.

[Fredz]

As for HDMI to MIPI, we had that done last May. Not to be a hipster or anything, but we have done all this stuff before it was cool.

From : http://forums.modretro.com/viewtopic.ph ... 50#p155950

Not that surprising, but that's the first time I read a confirmation about this. Nice quote about fresnel lenses also.

[MSat]

As for HDMI to MIPI, we had that done last May. Not to be a hipster or anything, but we have done all this stuff before it was cool.

From : http://forums.modretro.com/viewtopic.ph ... 50#p155950

Not that surprising, but that's the first time I read a confirmation about this. Nice quote about fresnel lenses also.

Cool find!

The lenses for the final developer kit are done, but the consumer lenses are still being worked on.

So there IS going to be one more dev kit before the consumer version.

Also curious about these "tiled" lenses. If they're on the same plane, wouldn't that still make them fresnels?

[OzOnE2k10]

As for HDMI to MIPI, we had that done last May. Not to be a hipster or anything, but we have done all this stuff before it was cool.

From : http://forums.modretro.com/viewtopic.ph ... 50#p155950

Oh, I don't doubt that at all. It kind of goes without saying tbh.

I'm sure Palmer and the guys have had some amazing tech to play with, and well before they even started work on the DK1.

I will still continue on my quest for a reasonably cheap 1080p upgrade before the DK2 release.
Would be great to know when they have the DK2 ready, and exactly what the release date will be.

I have to be honest though - I'm personally not looking forward to another 7-month wait for a new Dev Kit to be shipped.
I'm assuming / hoping they've got a ton of shipping centres and other channels sorted now?

OzOnE.

[remosito]

As for HDMI to MIPI, we had that done last May. Not to be a hipster or anything, but we have done all this stuff before it was cool.

From : http://forums.modretro.com/viewtopic.ph ... 50#p155950

Oh, I don't doubt that at all. It kind of goes without saying tbh.

I'm sure Palmer and the guys have had some amazing tech to play with, and well before they even started work on the DK1.

I will still continue on my quest for a reasonably cheap 1080p upgrade before the DK2 release.
Would be great to know when they have the DK2 ready, and exactly what the release date will be.

I have to be honest though - I'm personally not looking forward to another 7-month wait for a new Dev Kit to be shipped.
I'm assuming / hoping they've got a ton of shipping centres and other channels sorted now?

OzOnE.

Very interesting statement about DK2 lenses being done but CV optics still being worked on.

Either the DK2 will be coming soon before they can finish CV optics. Or DK2 will have different screen than CV making Optics not interchangable...


Personally hoping for both
DK2 soon and CV different screen

Budgeted for two Rifts this year already anyway. Just in case

[Inscothen]

Inscothen warping paras in util_render_stereo.h/.cpp No?

Cybereality said the parameters are stored in the headset. You can find some for the various Rifts made, but any changes for dsiplay and/or lenses, the stored parameters need to be replaceable to keep compatability.


OVR_Device.h

Code: Select all

 // Operator = copies local fields only (base class must be correct already)
    void operator = (const HMDInfo& src)
    {        
        HResolution             = src.HResolution;
        VResolution             = src.VResolution;
        HScreenSize             = src.HScreenSize;
        VScreenSize             = src.VScreenSize;
        VScreenCenter           = src.VScreenCenter;
        EyeToScreenDistance     = src.EyeToScreenDistance;
        LensSeparationDistance  = src.LensSeparationDistance;
        InterpupillaryDistance  = src.InterpupillaryDistance;
        DistortionK[0]          = src.DistortionK[0];
        DistortionK[1]          = src.DistortionK[1];
        DistortionK[2]          = src.DistortionK[2];
        DistortionK[3]          = src.DistortionK[3];
        ChromaAbCorrection[0]   = src.ChromaAbCorrection[0];
        ChromaAbCorrection[1]   = src.ChromaAbCorrection[1];
        ChromaAbCorrection[2]   = src.ChromaAbCorrection[2];
        ChromaAbCorrection[3]   = src.ChromaAbCorrection[3];
        DesktopX                = src.DesktopX;
        DesktopY                = src.DesktopY;
        memcpy(DisplayDeviceName, src.DisplayDeviceName, sizeof(DisplayDeviceName));
        DisplayId               = src.DisplayId;
    }

    bool IsSameDisplay(const HMDInfo& o) const
    {
        return DisplayId == o.DisplayId &&
               String::CompareNoCase(DisplayDeviceName, 
                                     o.DisplayDeviceName) == 0;
    }

};

Ideally we would want not only a new display, but also new lenses in 3D printed eyecups. If we use a ~6" display with say the 50mm lenses we can improve our devkits quite a bit. With larger diameter lenses(and lower magnification power) we would have much better visual quality.

EDIT: Just saw "Added sensor firmware update to the Config Utility." in the last SDK update. Anyone think this might be a way to change parameters?

[Inscothen]

more on parameters

Code: Select all

//-------------------------------------------------------------------------------------
// ***** OVR::SensorDisplayInfoImpl

// DisplayInfo obtained from sensor; these values are used to report distortion
// settings and other coefficients.
// Older SensorDisplayInfo will have all zeros, causing the library to apply hard-coded defaults.
// Currently, only resolutions and sizes are used.
struct SensorDisplayInfoImpl
{
    enum  { PacketSize = 56 };
    UByte   Buffer[PacketSize];

    enum
    {
        Mask_BaseFmt    = 0x0f,
        Mask_OptionFmts = 0xf0,
        Base_None       = 0x00,
        Base_Screen     = 0x01,
        Base_Distortion = 0x02,
    };

    UInt16  CommandId;
    UByte   DistortionType;    
    UInt16  HResolution, VResolution;
    float   HScreenSize, VScreenSize;
    float   VCenter;
    float   LensSeparation;
    float   EyeToScreenDistance[2];
    float   DistortionK[6];

    SensorDisplayInfoImpl();

    void Unpack();
};

[geekmaster]

HID feature report 9 is used to read or write those configuration parameters. However, that internal storage is limited, and cybereality also stated elsewhere that the config utility stores its data in the Registry, as I recall.

[Inscothen]

Thanks geekmaster.

With the HID stuff you could just overwrite specific parameters? How would we go about doing it. I don't know anything about it.

Also, does the config utility have any parameters for the display or lenses? All I've seen is for the IPD, height, gender, mag calibration, eyecup choice.

[silentbrain]

Hi,

Here is solution of MIPI bridge for Kindle Fire HDX panel. I got this prototype from Korea company by thankful help.
Bridge board is perfectly work well except only refresh rate 40Hz and This issue will be tunned.

Temporarily, I replaced my DK1 with this panel+ Bridge board and successfully decease screen door effect!!
I will update soon next step for refresh rate.

Panel number : LG LD070WU2-SM01 7" 1920*1200 (Kindle Fire HDX)
Interface : HDMI
Power Input required : 12V

[Inscothen]

Is this the first display mod?

If you can change the lenses out(provided you can change lens parameters and readjust lens-screen distance with custom eyecups) you should be very happy with the mod.

[virror]

Very cool!
Any idea what the added latency is?
What board is that and were did you get it from?

[OzOnE2k10]

Looks like a nice board, with the scaler integrated.

Well done, @silentbrain!
I bet it looks fantastic?

What's it like being able to see details in the distance when using those lenses now?
Would you say it improves the overall experience as much as you'd hoped?


In other news - Daniel's MIPI bridge design has just gone off to the PCB house.

So, we'll finally have a few options for this now, and for most other MIPI panels for the foreseeable future.
Daniel even mentioned some other panels with 2K or higher resolution.

OzOnE.

[Inscothen]

Awesome day. Did Daniel say what framerates are supported for any 2k or higher panels? Maybe we can see a 60Hz 2k LCD or 90-120Hz 1080p OLED if the circuit is capable.

I am curious on any 5.5-6.x" 2560 x 1xxx panels that might be available. I'm thinking of buying a used or broken devkit(as long as the tracker is good) for a second mod depending on the dk2's arrival/specs.

Still need to try to get custom eyecups and lenses close to MIPI availability since the dk1's are pretty bad.

[OzOnE2k10]

Oh, I should have mentioned - the board that's currently being made is using the Solomon SSD2828 MIPI bridge I believe.
That's good for up to 1080p atm, but he'll definitely be working on higher-res panels for his Digital Cinema products in the near future.

I have to be careful what I say here, 'cos he has some other very interesting products on the horizon which he doesn't want public just yet. :p

For a higher res MIPI panel, it may require a pair of bridge chips. I'm not too sure how that works in the newer phones.
They are no doubt building the MIPI outputs directly into the newer SoC chips for these mobiles nowadays.

I will be interested in getting better lenses for the DK1 as well once we have 1080p panels installed.
The plastic lenses are pretty good compared to others I've seen, but thin glass ones with chromatic correction would be great.

I'm not too bothered about adding a little bit more weight.
The 1080p panels will likely be thinner and lighter than the DK1 panel anyway, so that saves us a bit.

As soon as I have a MIPI bridge prototype in my hands, I'll be testing to see if the bridge board can be kept at the controller end of the cable.
I think it's a fairly small board though, so should sit next to the tracker behind the panel without too much trouble.

I can't post any pics of the PCB layout yet until I talk to Daniel again, but it looks like he's made provision for a few different panel connectors.

OzOnE.

[shavster]

This all sounds most exciting... count me in!

[Lookforyourhands]

Amazing work.

I'll give this a little more time and then hopefully be modding my DK1 with a new screen

Imagine the screen upgrade with a diffuser, and then Stem for positional tracking.

[3dvison]

In other news - Daniel's MIPI bridge design has just gone off to the PCB house.
OzOnE.

So is the "PCB house" where they go to get produced in larger numbers ?
If so, is there any time frame for when they might go on sale ?

[cegli]

Hi,

Here is solution of MIPI bridge for Kindle Fire HDX panel. I got this prototype from Korea company by thankful help.
Bridge board is perfectly work well except only refresh rate 40Hz and This issue will be tunned.

Temporarily, I replaced my DK1 with this panel+ Bridge board and successfully decease screen door effect!!
I will update soon next step for refresh rate.

Panel number : LG LD070WU2-SM01 7" 1920*1200 (Kindle Fire HDX)
Interface : HDMI
Power Input required : 12V

Excellent work! How much did the HTBM5 board cost? Is there any chance of getting the board with pre-flashed firmware? I assume you're tweaking the firmware to go from 40hz to 60hz. Did the screen fit cleanly in there, maintaining the same focus/distance?

[yuriythebest]

silentbrain Oculus should hire you!

[ripcurl123]

im putting my money on Daniel Rozsnyo, coming through as he does have a proven track record
just saying

[wileythecoyote]

Nice work silentbrain!
How do you feel about the added resolution? Does it make enough difference or should we opt for smaller fhd panel?
If I recall correctly this 1920x1200 is about 2.2 times more visible pixels and with 5.9 fhd panel it's around 3.5 times more visible resolution than dk1...