Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cargo needs are not always correct #2645

Open
Tkael opened this issue Aug 25, 2024 · 2 comments
Open

Cargo needs are not always correct #2645

Tkael opened this issue Aug 25, 2024 · 2 comments
Assignees
Labels
6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour.

Comments

@Tkael
Copy link
Member

Tkael commented Aug 25, 2024

What's Wrong (please be as specific as possible)

Cargo needs are not always correct and in some cases are zero when they ought not be.

Expected

Cargo needs are always correct when requested

Observed

Cargo needs are not always correct and in some cases are zero when they ought not be.

Steps to reproduce

  1. [Give the fullest and most reproducible steps you can]
  2. [The more reproducible, the better our chances of fixing it]

Configuration

  • Version
    • EDDI Version: 4.1.0-b3
    • VoiceAttack Version: N/A
  • Localization
    • EDDI's language: N/A
    • Voice: N/A

My Investigation

Investigation Notes

CalculateCargoNeeds() does not run or update after collecting, refining, or otherwise acquiring cargo.

EDDI Logs

[Any log files providing additional details about what happened. These are located at %APPDATA%/EDDI and have the extension ".log"]

Player journals

[These are not required if EDDI Logs are verbose but may be helpful otherwise. They are located at [your Saved Games folder]/Frontier Developments/Elite Dangerous/. Please only provide excerpts or attach files from the play session where the issue occurred.]

@Tkael
Copy link
Member Author

Tkael commented Aug 25, 2024

Per Darkcyde:
Just running another Rescue (surface salvage) mission. When I picked it up at the station, I check the .need and it correctly stated 4. I've now picked up a couple at the mission location, and checked again, but now it's saying zero. So it's been wiped somewhere in between taking it and being at the location. I'll see if I can do some more and check at various stages to see if i can work out where it's being wiped.

@Darkcyde13
Copy link

Darkcyde13 commented Aug 26, 2024

Just thought I'd mention this. While running tests for the Surface Signals/Locations execution order on game start, I noticed that after a restart of EDDI, that the cargo.need is now zero. I guess it needs to be set/updated when you load into a game too.

EDIT: Sorry, Ignore that. I forgot to test for .need after I collected the commodity and before the SS/L testing, so it could have been wiped before the testing. I'll try to run some more to clarify.

@Tkael Tkael self-assigned this Sep 16, 2024
@Tkael Tkael added the 6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour. label Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6. not up to spec The expected behaviour per the spec doesn’t match the observed behaviour.
Projects
None yet
Development

No branches or pull requests

2 participants