Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Gamma Campaign Research Bug #4556

Closed
wzdev-ci opened this issue Feb 27, 2017 · 8 comments
Closed

Gamma Campaign Research Bug #4556

wzdev-ci opened this issue Feb 27, 2017 · 8 comments

Comments

@wzdev-ci
Copy link
Contributor

resolution_closed type_bug | by notos98


Short and to the point:

This bug occurs when you load a savegame from gamma campaign or starting a fresh one from the main menu. Beta and Alpha are unaffected by this bug.

What it does: Nullifies almost all previous research, all units already built and built after the bug will have base stat values for the body, propulsion, and turret. Structures are bugged as well, turrets on defenses do base damage/ROF but some structures retain some upgrades (health on factories is 1100 and walls down to 550) but not what you have access to in gamma.

It will NOT happen if you enter Gamma campaign normally (Final Beta mission -> starting Gamma). However it will return as soon as you load after saving, so you can still beat gamma but only if you do it in one sitting.

Will upload 2 saves, Beta - 11(final mission) and Gamma - 1 bugged saved. You can recreate it by loading a campaign from the menu and look at your units, if the tanks you have are 1600~ 2000~ commander then you are bugged.

One odd thing worth mentioning if you load a fresh gamma campaign the machine gun turret does not exist in the blueprints when you select "show obsolete tech". Hope that helps


Issue migrated from trac:4556 at 2022-04-16 12:40:23 -0700

@wzdev-ci
Copy link
Contributor Author

notos98 uploaded file ResearchBugSaves.zip (139.4 KiB)

Save game files

@wzdev-ci
Copy link
Contributor Author

vexed changed blocking which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

vexed changed blockedby which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

vexed commented


Yes, please use 3.1.5, or, please help test the fixes that Berserk Cyborg has been doing.

We are in need of testers for 3.2 campaign issues!

Please see here: http://forums.wz2100.net/viewtopic.php?f=1&t=12714 for info on how to help!

Thanks!

@wzdev-ci
Copy link
Contributor Author

Hironaru commented


Hello,

This issue seems to persist in 3.2.3.

Operating System
Windows 10 Pro 64-bit
CPU
Intel Xeon E5 v2 @ 2.10GHz
Ivy Bridge-EP/EX 22nm Technology
RAM
32.0GB DDR3 @ 651MHz (9-9-9-24)
Motherboard
ASUSTeK COMPUTER INC. RAMPAGE IV BLACK EDITION (LGA2011)
Graphics
NV Surround (5760x1080@59Hz)
3071MB NVIDIA GeForce GTX 780 Ti (ASUStek Computer Inc)
3071MB NVIDIA GeForce GTX 780 Ti (ASUStek Computer Inc)
ForceWare version: 376.53
SLI Enabled
Storage
298GB Western Digital WDC WD3200JS-63PDB1 SCSI Disk Device (SATA)
931GB Western Digital WDC WD10EZEX-00BN5A0 (SATA)

@wzdev-ci
Copy link
Contributor Author

Berserk Cyborg changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

Berserk Cyborg changed resolution from `` to closed

@wzdev-ci
Copy link
Contributor Author

Berserk Cyborg commented


This don't seem to happen anymore according to campaign testers. See post in http://forums.wz2100.net/viewtopic.php?f=1&p=139372#p139354.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant