BUG DA Gold - Research Treaties provide no extra research

The research treaties provide diplomatic bonuses but not extra research at least to yourself. The extra 10% looks as if it is being given i.e. the time to completion of a tech is reduced but the extra beakers are not given i.e. when u hit turn.

This problem also existed in beta 2b can't remember if I posted about it or not.

This has happened every time I have mutually engaged in a research treaties with another race.
9,092 views 14 replies
Reply #1 Top
Surely I'm not the only person to have noticed this bug. Is stardock aware of this? Anyone else noticed this in there games? Are the AI's receiving the bonus research due to a treaty?.
Reply #2 Top
bump - Does nobody care that research treaties don't work? This is true of the latest DA 1.5059 patch.
Reply #3 Top
I certainly care, but haven't particularly noticed. So the total research in the research screen doesn't go up after you get the treaty??
Reply #4 Top
Example: You sign a research treaty with the torians. This gives you 10% of there total research every turn. On the research screen there is an amount showing how much the research treaties should be giving you that turn.

If you create zero research yourself that turn (select 0 percent spending)then you should just recieve the amount from the research treaty. Select a low level cost tech (easier to see progress on amount meter) and press turn. You will see that no extra research has been added. This is the case regardless of whether you spend any amount on research yourself or not.
Reply #5 Top
Yeah, it's broken indeed.

While the research screen shows how much you *should* get from treaties and the "time to complete" uses that figure, the actual time is always longer (or if you set your own spending to 0%, it will never be finished). Just try it and check the numbers.

Fix, please.
Reply #6 Top
Yeah, it's broken indeed


this is the first post i have seen on this issue? Perhaps it is like a starbase or anomaly bonus? it only increases by 10% whatever your own research is?

Question; is there anyone who has definate proof of the tech treaty working properly?
Reply #7 Top
No, it doesn't have anything to do with your own spending, I did thorough checks with lots of different spending settings. Why don't you try it yourself?
Reply #8 Top
Why don't you try it yourself?


You sound combatative?? i was just asking! anyway, i'm at work and cannot run the game.
Reply #9 Top
Thanks for posting Todd Hawks. Nice to know I'm not imagining things.

Stardock person required for bug aknowledgement...
Reply #10 Top
I tried this last night and found it to be true. You don't seem to get the extra research from the research treaty. On DL, when researching a tech at the end of the tree, I will usually move the tech slider down as far as it can go and still get the tech in 1 turn.

I had a tech treaty in my DA game, and tried this same tactic. Next turn, no tech. Still said 1 turn to research. It appears that it happens the way Todd Hawke described it. It uses the tech amount you are supposed to get to calculate the time to complete, but doesn't actually give it to you.

Stardock please look into this.
Reply #11 Top
The treaty gives you 10% of the civ's research spending.

The value showed on the Research screen for Research Treaties is the amount of the research spending you are receiving.  Is this 0 bc?  Or are you saying that it has a value listed there, but it doesn't appear to get added in?

Can you provide a saved game that shows the problem?  If these treaties are not working correctly we DO care, and want to fix it.  If you do have a saved game (that would be the quickest way for us to see what is happening), please zip it and send it to [email protected] with your debug.err file.  Also, providing a link back to this thread would be helpful.

Thank you.
Reply #12 Top
I found the source of the problem.  Thank you for reporting it.
It will be fixed in the next update.

Reply #13 Top
Give us a minute to send a save game.  

Thanks! You guys rock!
Reply #14 Top
I found the source of the problem. Thank you for reporting it.
It will be fixed in the next update.