Patch Notes Update Update 1.1 Incoming - Clipper hot fix (1.1.01) 7.15 pm GMT

Status
Thread Closed: Not open for further replies.
11157

After the patch, some of my keyboard settings were gone.

After trying to re-set them in-game I found out that Elite is now for some reason calling them differently.

For example when I bind the tilde key it lists it in game as at.

The minus key is listed as slash and the equal key is listed as RING

The sound is also very weird in-game now. Nothing sounds the same anymore. Engine's are less violent and shooting is weird too, I can't explain why exactly.

Again also, the sound for moving down below the station after docking and moving back up is missing, it's way too quiet.

And opening a mission in your transaction menu is a very weird thick orange colour and the letters are completely off too.
 
peraa

I am now also hearing weird ambient sounds when I am out in space just standing still. It used to be really quiet but now I am hearing weird humming and music chime sounds even with the music turned off.

What did you guys do? :S
 
Sounds like an issue with the joystick - unless others are seeing the same? Try unplugging the joystick, put it back in and then start the game. Also make sure you have the right drivers for it.

Michael

I am not having his exact issue, but am having joystick detection issues since 1.1. Related?

From my post #346

I have 6 game controllers installed. Everything was working fine prior to 1.1 patch.

I have:

Thrustmaster T1600M (used for Battlefield 4).
Cougar MFD (two of them, used for DCS A10C flight sim).
CH Pro throttle (used for ED).
CH Fighterstick (used for ED).
Saitek Pro rudder pedals (used for ED).

The controllers I was using for ED were working fine.

Now, after 1.1 patch, only the Thrustmaster T1600M and CH Pro throttle are detected by the game.

I saw in the patch notes:

"Allowed supplemental devices to be used. They count as PCPads (for example independent throttles, custom control panels)".

Perhaps this limits us to two controllers now? It was working before...
 
Have been on a little exploring trip, about 2500 Ly from Sol. Managed to get back to civilisation before the 1.1 patch to sell the data. Downloaded the patch, installed nicely. Started the game and have sold the first page. Seen the nice bonus window for beeing the first commander to scan a system. Now.. I can`t sell anymore of the data becouse the client keeps crashing.... sigh...

You could sell one page? For me tha game crashes back to desktop right when universal cartographics has ended loading. I see the systems-list for a fraction of a second, then the game crashes... always.
Won't move my ship out of that outpost until I sold all the data. Too dangerous with the collision issues.
 
NPCs are still getting stuck inside stations, around pillars and landing pads just as before. This was one of the fixes listed, but it's not fixed.

Also stations are still empty on first player arrival (NPCs jumping away from landing pads bug still?).
 
Last edited:
Players are just going to stop playing if everything they've worked for is wiped out in an instant when they're nudged by another player/npc. I'm sorry, but who thought this was a good idea? With the station ports being used for both entry and exit crashes happen frequently, especially with NPC's that move erratically. It's not fun if you're constantly terrified when entering/leaving a station that a NPC is going to come out of nowhere and take you out. Like I said in an earlier post this has just happened to me and I've pretty much lost everything - not meaning to sound dramatic but that's the reality. Don't want to play anymore reeally... very sad :(
 
Does anyone want to try risking their anaconda scraping the top of the letterbox with the docking computer?

Did they fix the docking computer for the anaconda? The docking computer doesn't let you use 4 pips to shields so be careful!
 
So post 1.1, I'm having a severe framerate drop whenever something explodes, no matter whether it's happening on- or off-screen. Using an AMD FX-6350, an AMD R9-285, 8GB of RAM.
 
Did they fix the issue where bounties would not register in the transaction log when using a cargo scanner and KWS at the same time? I doubt this is working as intended.
 
Realiatic collision damage would mean that almost any contact would be devastating with the speeds and masses involved. Getting to a good gameplay result is just about adjusting, testing and adjusting, until the result is what is wanted.

They will get it right, but it takes time.

Exactly time spent in Beta, not release, pushed this out way to fast!
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom