Elite: Game talk

26 Jul 2022, 11:11pm
QuillmonkeyI’m not an expert on this but ED uses shaders to give colour to everything from hud to interior lighting etc. reshaders just allow you to change these colours. Some, including EDHM allow you to do this on the fly. EDHM does it via its shipyard where you can apply a theme to any ship in yr fleet. When you fly that ship all colours are set to the new theme. Can’t be more technical than that but try EDHM on its own and see what is missing.


I am not trying to reshade just ship interior, I am trying to reshade the environment, general lighting, celestial bodies etc. I am trying to figure out a way where I can have both edhm effects as well as environmental changes.
26 Jul 2022, 11:26pm
Yuna SakashiroFor sensors, the only advantage of A-rated is their improved ability to resolve cool running targets. I never found this particularly useful, so I always pick D-rated. If your ship can afford the weight increase, the long range mod will make more ships appear on your navigation panel, making it easier to acquire high value targets in a RES.

If long range combat is not a factor then I would use D-rated without question. But I'm curious how valuable the extra sensor range is when weapons are modded for long range, either in your own ship or the enemy ship.
26 Jul 2022, 11:41pm
I found long-range sensor useful for AX, for manoeuvring, pulling the swarm away, keeping the safe distance comfortably. Also, fighting multiple interceptors, you less likely will have an unwelcome surprise less than 3km away.
26 Jul 2022, 11:49pm
Aetoate Bace
QuillmonkeyI’m not an expert on this but ED uses shaders to give colour to everything from hud to interior lighting etc. reshaders just allow you to change these colours. Some, including EDHM allow you to do this on the fly. EDHM does it via its shipyard where you can apply a theme to any ship in yr fleet. When you fly that ship all colours are set to the new theme. Can’t be more technical than that but try EDHM on its own and see what is missing.



I am not trying to reshade just ship interior, I am trying to reshade the environment, general lighting, celestial bodies etc. I am trying to figure out a way where I can have both edhm effects as well as environmental changes.


here are some old graphic tweaks (including reshade) Graphics Mods and color change editor HUD Color Theme Editor -maybe helpfull


Last edit: 27 Jul 2022, 10:00am
27 Jul 2022, 12:05am
KurakilIf long range combat is not a factor then I would use D-rated without question. But I'm curious how valuable the extra sensor range is when weapons are modded for long range, either in your own ship or the enemy ship.

A-rated won't give you extra range over D-rated. All sensor classes have 8km range by default, and 14km with grade 5 long range mod, which doubles the module's weight. The only difference between the classes is sensitivity to ships with low heat signature. But remember, you can also increase a ship's signature with emissive munitions. Unlike A-rated sensors, emissive munitions will also widen gimbal arcs.
27 Jul 2022, 12:55am
Yuna Sakashiro
KurakilIf long range combat is not a factor then I would use D-rated without question. But I'm curious how valuable the extra sensor range is when weapons are modded for long range, either in your own ship or the enemy ship.

A-rated won't give you extra range over D-rated. All sensor classes have 8km range by default, and 14km with grade 5 long range mod, which doubles the module's weight. The only difference between the classes is sensitivity to ships with low heat signature. But remember, you can also increase a ship's signature with emissive munitions. Unlike A-rated sensors, emissive munitions will also widen gimbal arcs.

What is the "typical emission range" for the sensors then? I guess that is where I am not clear.
27 Jul 2022, 9:40am
Hi people, I'm new to the game and I have some kind of a bug with a station. I need to end the mission, but all docking pods are occupied. I've tried to wait when bots will go away, but they didn't. Moreover, station gave me an access to land on the pod... That still was occupied. So, I couldn't land, and only thing that I recieved with autodocking - I've landed on other ship, but not on the station... Now bots are trying to fly from the landing pad, but they can't, they are kinda jumping on it instead of flying away, and when they finally fly away... A new one ship appears on that landing pad immediately literally from nowhere. What I should do in that situation? I have 5 more hours for the mission, should I just leave the game and wait?
27 Jul 2022, 9:50am
KurakilWhat is the "typical emission range" for the sensors then? I guess that is where I am not clear.

It's basically the scan range, which is separate from the targeting range. It does not affect the radius at which your contacts panel will populate. And once a ship appears in the contacts panel, you can target it, even if it's behind you. Scanning requires facing the target.

A long time ago, I joined Epi in a hazRES. His Vulture had D-rated long range sensors, my Courier had lightweight ones. He saw all the high value targets long before I could see them. Lightweight was the right choice for a high speed Courier, but bigger ships are less sensitive to weight, so I've used the long range mod on my Mamba and now on my Cutter, on D-rated sensors. I found A-rated totally unnecessary and not worth the weight increase.

Engineering doesn't change the typical emission range, so you can compare D- and A-rated before wasting materials.
27 Jul 2022, 10:13am
ParkanHi people, I'm new to the game and I have some kind of a bug with a station. I need to end the mission, but all docking pods are occupied. I've tried to wait when bots will go away, but they didn't. Moreover, station gave me an access to land on the pod... That still was occupied. So, I couldn't land, and only thing that I recieved with autodocking - I've landed on other ship, but not on the station... Now bots are trying to fly from the landing pad, but they can't, they are kinda jumping on it instead of flying away, and when they finally fly away... A new one ship appears on that landing pad immediately literally from nowhere. What I should do in that situation? I have 5 more hours for the mission, should I just leave the game and wait?

If it's an outpost and those are truly just NPC ships, just make a docking request and you should get the free landing pad fairly quick. I never noticed such problem with large stations (there are enough pads). But the behavior you described sounds odd. In the worst case, you can jump back to the game menu and back to the game.
27 Jul 2022, 10:46am
Artie

If it's an outpost and those are truly just NPC ships, just make a docking request and you should get the free landing pad fairly quick. I never noticed such problem with large stations (there are enough pads). But the behavior you described sounds odd. In the worst case, you can jump back to the game menu and back to the game.


It happens a lot in busy instances in popular stations with high traffic. Few players ditching their ships on landing pads being AFK can deteriorate an instance very badly. The solution is to reset the instance or switch mode.
27 Jul 2022, 10:51am
Artie
ParkanHi people, I'm new to the game and I have some kind of a bug with a station. I need to end the mission, but all docking pods are occupied. I've tried to wait when bots will go away, but they didn't. Moreover, station gave me an access to land on the pod... That still was occupied. So, I couldn't land, and only thing that I recieved with autodocking - I've landed on other ship, but not on the station... Now bots are trying to fly from the landing pad, but they can't, they are kinda jumping on it instead of flying away, and when they finally fly away... A new one ship appears on that landing pad immediately literally from nowhere. What I should do in that situation? I have 5 more hours for the mission, should I just leave the game and wait?


If it's an outpost and those are truly just NPC ships, just make a docking request and you should get the free landing pad fairly quick. I never noticed such problem with large stations (there are enough pads). But the behavior you described sounds odd. In the worst case, you can jump back to the game menu and back to the game.

Yes, it's an outpost. I did all of that, spent 1 hour waiting for them to leave, even left game couple of times and traveled to other systems. They are still there, no new bots can land, and even another playerd couldn't land. Now it's not new appearing ships, it's just Cobras that don't want to leave, and I still can get a permission to land, even that I can't because of Cobras. There is one free medium size landing pad, but game doesn't want to give it to my small ship or to bots, it was just empty all that time.
27 Jul 2022, 10:55am
Parkan
Yes, it's an outpost. ~~

try the same station in "Solo" game mode once.
It might be better there...
27 Jul 2022, 10:55am
Episparh
Artie

If it's an outpost and those are truly just NPC ships, just make a docking request and you should get the free landing pad fairly quick. I never noticed such problem with large stations (there are enough pads). But the behavior you described sounds odd. In the worst case, you can jump back to the game menu and back to the game.



It happens a lot in busy instances in popular stations with high traffic. Few players ditching their ships on landing pads being AFK can deteriorate an instance very badly. The solution is to reset the instance or switch mode.

But if it's just AFK players then I would not receive a permission to land literally on their heads and bots would not try to land on their heads too, right? Moreover, after scanning, looking at contacts menu and just trying to see players nearby through the messages menu I didn't see them as players, so it's just bunch of stucked bots.
27 Jul 2022, 11:03am
Sir-Duke
Parkan
Yes, it's an outpost. ~~


try the same station in "Solo" game mode once.
It might be better there...

Oh, thank you very much, now pads are empty! I thought that Solo mod will somehow limit what I can do in the game, so I didn't try it. Still I'm very confused, because if there are no any of them in Solo mode - then it's definitely AFK players, but why I could receive a permission to land and why bots were trying to land on them?
27 Jul 2022, 11:11am
Parkan

But if it's just AFK players then I would not receive a permission to land literally on their heads and bots would not try to land on their heads too, right? Moreover, after scanning, looking at contacts menu and just trying to see players nearby through the messages menu I didn't see them as players, so it's just bunch of stucked bots.


As I said it is issue of the p2p network model that ED uses for synchronizing instances. If you play in large player group or online and you have more than one player in the instance the synchronization deteriorate over time and you can observe a lot of borked NPC behavior. Clogged pads or mail slot, NPC ships on supposedly free designated landing pad or merged together ships.

Post a reply

You must be signed in to post here.
Elite:Dangerous related questions, answers, tips and help. Simply anything that is directly related to the game and its gameplay goes here.
For the discussions about the community, other stuff related to the game like astrophysics and so on please use the General talk thread.

What does belong here:
  • Questions, answers, tips and guides about ship loadouts, game activities like exploration, mining, combat and similar things that directly relate to the gameplay.
  • Game technical issues and problems, if you are looking for a help. For the bug reports please head to the official FD forum.
  • Discussion about "official" events from GalNet and community goals.
What does not belong here:
  • Discussing player actions and activities, general topics about Elite community and player events, topics related to the game but also real world (like astrophysics and similar). Please post these to the "General talk" thread instead.
  • Any off topic discussion, please post this kind of stuff to the "Offtopic" thread.