Jump to content
Game-Labs Forum

shvaks

Members2
  • Posts

    8
  • Joined

  • Last visited

  • Days Won

    1

shvaks last won the day on October 31 2023

shvaks had the most liked content!

shvaks's Achievements

Landsmen

Landsmen (1/13)

10

Reputation

  1. Category: Shipbuilding Repro attempts: 1/1 (always) Repro steps: 1. Enter shared design builder 2. Select US and select the following hulls: Large Scout Cruiser Large Armored Cruiser Semi-Armored Cruiser IV "Flush Deck" Destroyer Current behavior: Listed hulls have graphical artifacts on them Desired bahavior: The graphical artifacts should not exist, or they should be scaled and placed appropriately. Screenshots:
  2. Category: Shipbuilding Repro attempts: 1/1 Repro steps: 1. Enter ship builder 2. Select dreadnought I hull 3. Add the following parts: reinforced main tower II advanced funnel rear tower IV standard superimposed barbette mark 3 13 inch gun turret (on top of barbette) Observe the warnings and the turret's sector of fire Current behavior: "Some guns have poor sector of fire" warning appears even though the turret is not obstructed. Desired bahavior: The warning should not appear in this case.
  3. Sorry I don't think comparing this to fallout is a good analogy. Fallout's VATS: Built into the game as a core feature and provides balanced gameplay if you are not min maxing too much Possible to exploit but the control is in player's hands, you can choose to use it or not This bug: Very likely a side effect of wonky code on ship accuracy, is not shown as a feature anywhere(no modifiers such as"+100% accuracy against adjacent target" shown) Possible to exploit, but the control is mostly not in player's hands. Both player and AI can trigger it by accidently bunching up ships, even more so when the equally wonky formation AI is in charge. Shooting into a cluster of ships and getting big hits is ok, but it needs to be balanced and explicitly shown as a feature. If this is really a bug, it needs to be removed as it affects the core gameplay. If this is a "feature" now, it needs more work to make the player contextulize what is happening and give the player more tools to interact with it.
  4. Category: Battle Repro attempts: 3/3 Repro steps: 1. Enter any battle 2. Watch enemy torpedo launches and their marked range Current behavior: Torpedos travel much further than their range says and can still hit and damage ships when they outrun their marked range. Desired bahavior: Torpedo should be incapacited beyond their maximum range. Video evidence:
  5. It is way too abusable and way too easy to trigger in larger battles. Imagine a FPS game has a bug that allows you to aimbot. It needs to be fixed.
  6. Category: Shipbuilding Repro attempts: 1/1(always) Repro steps: 1. Enter ship builder from any entrypoint 2. Find the costal defense ship (BB) hull from US 3. Attempt to place a secondary gun on the hardpoint shown in the picture below Current behavior: You cannot place a secondary gun there even though there is visual of a hardpoint on the ship model Desired bahavior: Either the player should be able to place a secondary gun there, or there should not be any visuals of a hardpoint.
  7. Category: Battle Repro attempts: 3/3 Repro steps: 1. Enter custom battle menu 2. Design some fast ships for player and ships with heavy guns and minimal fire control for AI for best effect (example: any fast TBs versus BBs with only heavy guns) 3. Enter custom battle and find the enemy 4. Sail all your ships extremely close together and let the enemy shoot at them 5. Observe the enemy shells and thir aim status Current behavior: Enemy shells will have a very high chance of hitting other ships that are very close to the target. Oftentimes even when ladder aiming isn't complete and accuracy is 0%. In extreme cases, you can achieve 100% hit rate when hit chance is 0% when the bug kicks in. Desired bahavior: Only a very small portion of the missed shells should scatter onto other ships that are near the target, and not a vast majority of them. Video evidence:
  8. Just bought the game and noticed fires causes the performance to drop a lot, to the extent of game breaking. The attached screenshot shows three scenarios: 1. ship engulfed in flames, zoomed in, fps drops to a unplayable 9-10 fps. 2. same ship in flames, viewed at minimum zoom, fps returns to 60. 3. same ship, fire nearly extinguished, zoomed in, 60fps. all the screenshots are taken when playing with "good" graphic settings. Given my system specs: CPU: Intel Core i7-9750H @2.60GHz, running at ~4.05GHz when playing the game RAM: 16GB Graphics card: Nvidia RTX 2060 6GB This doesn't feel right that some fires can cause such massive fps drop. I understand that performance is not on the priority list right now and the devs intend to improve performance after the campaign update. However I don't think performance can be completely overlooked right now, especially when the game is going for a steam launch in august while the campaign is scheduled to take 5-6 months to implement.
×
×
  • Create New...