ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread

Amadeus

A
gapper4 said:
Thanks ! Will try this as soon as I get home. Still wondering why FD hasn't already done this. Seems like a no-brainer...
Click to expand...

I can confirm that this works on 1.06
Had to learn how to use a hex editor but not biggie.

Go to the offset, find the string of two digit characters, highlight them and retype the new values.
Hopefully this isn't going to set off any cheat alarms but it's so much more playable with the CA fix.

Can't understand why it's not made official.
 

CylonSurfer

CylonSurfer
So do any other Rifters fancy meeting up in E: D? I'm UK based, usually on at around 9PM, although I should be on most of this evening after around 6. I'm Commander CylonSurfer in the game.

I was running trade runs in a Lakon Type 6 but recently sold it and moved to a Cobra MKIII for some bounty hunting or smuggling / pirating to get a feel for different play types.
 

gapper4

gapper4
CylonSurfer said:
So do any other Rifters fancy meeting up in E: D? I'm UK based, usually on at around 9PM, although I should be on most of this evening after around 6. I'm Commander CylonSurfer in the game.

I was running trade runs in a Lakon Type 6 but recently sold it and moved to a Cobra MKIII for some bounty hunting or smuggling / pirating to get a feel for different play types.
Click to expand...

I'm Cmdr Geo Merkator. Give me a shout if you want (Does ED support voice yet ? I currently use TeamSpeak with the Mobius PvE private GROUP).

Hell, is there a DK2 private group yet ? Why not create one ?
 

Half Giant

H
Amadeus said:
I can confirm that this works on 1.06
Had to learn how to use a hex editor but not biggie.

Go to the offset, find the string of two digit characters, highlight them and retype the new values.
Hopefully this isn't going to set off any cheat alarms but it's so much more playable with the CA fix.

Can't understand why it's not made official.
Click to expand...

The dev team will implement the full SDK and that will fix or improve the chromatic aberration. A complex dev project has a massive list of things to do. So from a long term project point of view it doesn't make sense to create extra work by making a short term change that you know will be fixed soon enough anyway and then would need to be undone.
 

CylonSurfer

CylonSurfer
gapper4 said:
I'm Cmdr Geo Merkator. Give me a shout if you want (Does ED support voice yet ? I currently use TeamSpeak with the Mobius PvE private GROUP).

Hell, is there a DK2 private group yet ? Why not create one ?
Click to expand...

Not that I am aware, we should create one if there isn't - Do you play in the all group?
 
Last edited:

gapper4

gapper4
Half Giant said:
The dev team will implement the full SDK and that will fix or improve the chromatic aberration. A complex dev project has a massive list of things to do. So from a long term project point of view it doesn't make sense to create extra work by making a short term change that you know will be fixed soon enough anyway and then would need to be undone.
Click to expand...

Agreed in principle but this small change to the code takes a couple of minutes to incorporate. It's not like they have to redesign anything. Instead, players have to input this at every release. Not a biggie; just wondering why something so useful, painless, and easy hasn't been done already.
 

Half Giant

H
From the outside things always appear this way. Having worked in dev teams I can imagine there is the right guy to make this change, he's the OR guy. So he can hard code a specific fix, as you say quickly. Does it have to include some logic so that it detects DK1s and doesn't break it for them? Even if if it did that isn't too much more complicated. But then that needs to be tested on DK1 and 2s and then releasing. For all we know the update that implements the latest SDK is a few days away. So you are pulling the guy who is doing that the full SDK off his track, to make a change that will only be needed for days.

Or the new SDK is implemented and being tested internally as we speak. So why muddy things up, in that OR code path, again for a short term thing.

Even a small released change involves dev, pm, test and release. Things do look simpler from outside but it is a bit like fixing a dripping tap when you know the plumbing is being replaced in a week or two.
 

gapper4

gapper4
Half Giant said:
From the outside things always appear this way. Having worked in dev teams I can imagine there is the right guy to make this change, he's the OR guy. So he can hard code a specific fix, as you say quickly. Does it have to include some logic so that it detects DK1s and doesn't break it for them? Even if if it did that isn't too much more complicated. But then that needs to be tested on DK1 and 2s and then releasing. For all we know the update that implements the latest SDK is a few days away. So you are pulling the guy who is doing that the full SDK off his track, to make a change that will only be needed for days.

Or the new SDK is implemented and being tested internally as we speak. So why muddy things up, in that OR code path, again for a short term thing.

Even a small released change involves dev, pm, test and release. Things do look simpler from outside but it is a bit like fixing a dripping tap when you know the plumbing is being replaced in a week or two.
Click to expand...

Ok, fair enough. I don't know enough about devving to comment further. FD have been great Devs so far so I assume they're all over this. In the meantime, I'll spend the extra few minutes modding this myself.
 

Amadeus

A
Half Giant said:
From the outside things always appear this way. Having worked in dev teams I can imagine there is the right guy to make this change, he's the OR guy. So he can hard code a specific fix, as you say quickly. Does it have to include some logic so that it detects DK1s and doesn't break it for them? Even if if it did that isn't too much more complicated. But then that needs to be tested on DK1 and 2s and then releasing. For all we know the update that implements the latest SDK is a few days away. So you are pulling the guy who is doing that the full SDK off his track, to make a change that will only be needed for days.

Or the new SDK is implemented and being tested internally as we speak. So why muddy things up, in that OR code path, again for a short term thing.

Even a small released change involves dev, pm, test and release. Things do look simpler from outside but it is a bit like fixing a dripping tap when you know the plumbing is being replaced in a week or two.
Click to expand...

It's just changing few values though isn't it?
Make it a menu option and label it "experimental" if you wish but the C:A is spoiling a lot of peoples DK2 experience on Elite and it needn't had.

Once you apply the fix all the menus are a lot easier to read and the game looks a ton better.

Minor change now and keep your DK2 fanbase or wait until OR get the dev kit problems fixed and find a lot of people have given up on elite on the rift.

Also you don't want to have people messing about with hex editors on a multiplayer game if you can avoid it...
 

gapper4

gapper4
Splendour said:
You can edit it yourself for the 1.06 exe , the instructions are at:
http://www.reddit.com/r/oculus/comments/2dysny/elitedangerous_chromatic_aberration_improvement/
I used hexplorer to do this http://sourceforge.net/projects/hexplorer/
As someone who had never tied this sort of thing before I found it straightforward and it took all of two minutes. Just make sure to save a copy of the exe before you edit it in case of mistakes
Click to expand...

Well, I've managed to open the .exe with Hexplorer but the text is so tiny that I can't make anything out. There doesn't seem to be any way to make it bigger. Or is there ?
 

robdood

robdood
Having spent some time on this last night after the update, can't say I've noticed the chromatic aberration being that bad any more (applied the hex edit back on 1.04 and hadn't thought I'd need to do it again!)

You chaps who have issues with it, you've definitely run the measuring app in the configuration tool, right? And you also made sure your rift is on squarely to your face? If you go into something like the desk demo, you can easily see the chromatic problems if you slightly tilt /adjust the Rift's position while on your face.

In other news, I'm close to nailing a buttery 75fps. But star ports still cause judder (~65fps according to my counter). Fingers crossed FD have a ton of optimisation planned, as I'm having to run on absolute lowest detail with nVidia control panel forcing all 3D options to prefer maximum performance. My pc isn't a beast, but it isn't a slouch either. (i7 4770k, gtx670 4gb, 16gb ram..)

We need low detail pilot body and lower detail star ports in the meantime.. Please, FD!
 

slartybartfast

slartybartfast
robdood said:
Having spent some time on this last night after the update, can't say I've noticed the chromatic aberration being that bad any more (applied the hex edit back on 1.04 and hadn't thought I'd need to do it again!)

You chaps who have issues with it, you've definitely run the measuring app in the configuration tool, right? And you also made sure your rift is on squarely to your face? If you go into something like the desk demo, you can easily see the chromatic problems if you slightly tilt /adjust the Rift's position while on your face.

In other news, I'm close to nailing a buttery 75fps. But star ports still cause judder (~65fps according to my counter). Fingers crossed FD have a ton of optimisation planned, as I'm having to run on absolute lowest detail with nVidia control panel forcing all 3D options to prefer maximum performance. My pc isn't a beast, but it isn't a slouch either. (i7 4770k, gtx670 4gb, 16gb ram..)

We need low detail pilot body and lower detail star ports in the meantime.. Please, FD!
Click to expand...

ouch on the lowest settings, dont bode well for me im on a i7 3930k gtx 670 4gb ( same as you best bang fer the money at the time ) with 32 gb ram. a waiting for my dk2.
 

Half Giant

H
Amadeus said:
It's just changing few values though isn't it?
Make it a menu option and label it "experimental" if you wish but the C:A is spoiling a lot of peoples DK2 experience on Elite and it needn't had.

Once you apply the fix all the menus are a lot easier to read and the game looks a ton better.

Minor change now and keep your DK2 fanbase or wait until OR get the dev kit problems fixed and find a lot of people have given up on elite on the rift.

Also you don't want to have people messing about with hex editors on a multiplayer game if you can avoid it...
Click to expand...

For all I know there could be an update tomorrow that does exactly this and I'd look a bit silly. But I don't find the CA to be a problem personally. I don't think a lot of people are going to give up on Elite because of it. Menus involve localisation, UI changes are a higher bar than non UI changes. Why risk regressing things for DK1 users. Where did the values come from? Do they fix it for an average or specific person - i.e. is it for a specific IPD for instance? Any work means something else isn't being done, it just seems a distraction to me. I'd rather look at it positively, if they did have a quick patch to do this then it would be a clue to me that they think full DK2 sdk support is far enough off to make it worth while. They haven't, so far, so hopefully that means they aren't worried about it and it's not far off. All speculation, of course, just chatting about why a dev team might not jump at at something like this.
 

Sanderson

Sanderson
Anyone have the edited 1.06 available to DL or know where I can get it? I just don't trust myself editing my exe.
 
Last edited:

Sanderson

Sanderson
Amadeus said:
I can confirm that this works on 1.06
Had to learn how to use a hex editor but not biggie.

Go to the offset, find the string of two digit characters, highlight them and retype the new values.
Hopefully this isn't going to set off any cheat alarms but it's so much more playable with the CA fix.

Can't understand why it's not made official.
Click to expand...

How much better is it? Possible to do a screen shot comparison?
 

Amadeus

A
Sanderson said:
How much better is it? Possible to do a screen shot comparison?
Click to expand...

I suppose it depends on your individual optics but for md it turned an orange hazy mess into clear text. I checked my ipd both in software and in the mirror with calipers. Both 63mm

A screen shot wouldn't go any good because that records the image pre-optics.

It's scary at first but if you take a copy and follow the guides you'll be fine.

Strange thing is it only deals with sideways aberration.
North south means you need to adjust how it sits on your face.
 

robdood

robdood
slartybartfast said:
ouch on the lowest settings, dont bode well for me im on a i7 3930k gtx 670 4gb ( same as you best bang fer the money at the time ) with 32 gb ram. a waiting for my dk2.
Click to expand...

To be fair on the Rift the detail you traditionally care about isn't that important! It still looks great, and tbh given the resolution of the rift you don't actually perceive that much difference in textures and stuff. The only thing I miss really is the shadows dancing round the cockpit.
 
You must log in or register to reply here.
Back
Top Bottom