Comprehensive list of known bugs in EV Nova

the comprehensive bug report made by you!

The goal of this thread is to provide a single location in which to document all known engine bugs in the current version of Escape Velocity: Nova. This is both for plug-in developers to reference and know what they need to work around, and in case a future update is made so it is known what needs to be fixed. Please contribute to it any bugs of which you are aware.

There are several guidelines to follow when posting here:

  • This thread is the place to list bugs in the current version of EV Nova, which at the time of this writing is v1.1 on Mac and v1.0.10 on Windows. List only bugs found in the current version of Nova.

  • When listing a bug, include your operating system and version, and the version of EV Nova where you see the bug.

  • This thread aims to enumerate engine bugs. You are welcome to list scenario bugs for the stock game, but please label them as such.

  • An engine bug can be identified by a number of criteria:

    • The application program EV Nova crashes, freezes, quits, or behaves unacceptably as an application.
    • The behavior of the game EV Nova does not match the relevant description in the Nova Bible.
    • The Nova Bible does not specify how the game is supposed to behave, AND the behavior is not consistent across operating systems OR the behavior is unexpectedly restrictive
  • Describe the bug in detail. Additionally, if you have them, please provide links to any previous threads about it.

More information is always appreciated, so if you see a bug reported previously to which you can add specifics about what causes it and what its effects are, or if it is no longer present, please do so. I will do my best to keep this first post updated with bugs as they are listed.

Now to begin:

Application failure

Crash on startup using alternate data files
Versions affected: Mac v1.1
I am experiencing frequent crashes of EV Nova 1.1 on Mac OS X 10.6.4 during game start-up, most often after selecting an alternate source folder for data files. This is not consistent, and does not seem to be affected by which data files are selected, but occurs often enough to be a major annoyance. Once the game starts up though, it usually runs fine.

Plugin Converter crash
Versions affected: Windows v1.0.10
The Plugin Converter application that comes with EV Nova 1.0.10 for Windows has the following bug in Windows 7, as described here: the plugin conversion will fail if the eighth character of the name of the file to be converted is any of the following: #+23;bcjkrsz(BCJKRSZ{

Game disobeys documentation

Small asteroids absent on large screens
Versions affected: Mac v1.1 and Windows v1.0.10
Asteroids do not appear on large screens unless their sprite sizes are at least 100×100 pixels.

Asteroid FragCount = 1 does not work
Versions affected: Mac v1.1, don’t know about Windows v1.0.10
Asteroids set to have FragCount 1 do not produce any asteroid fragments when destroyed. The Nova Bible says they should produce FragCount±50%, which means exactly 1 every time when FragCount is 1. See here.

Strict play and ship speed inexplicably linked
Versions affected: Mac v1.1 and Windows v1.0.10
When a pilot is not on strict play, it has a +50% bonus to top speed and there is no option to disable this unfair advantage without also using strict play. The Strict Play checkbox gives no mention of this, so it should not be tied to that. The speed bonus should be optional independent of strict play.

Pilot location after using escape pod
Versions affected: Mac v1.1, don’t know about Windows v1.0.10
There is no documentation of what happens when a pilot ejects into an escape pod. This should be documented so plug-in developers can know where to expect a pilot will appear after ejecting. Recommendation: the pilot should be sent to the initial system in which its chär began.

One-way jump links made two-way
Versions affected: Mac v1.1 and Windows v1.0.10
There is no documentation of the “implicit reciprocal link” behavior seen in the game engine. This behavior is detrimental to plug-ins designed to have one-way jump links, and therefore should be removed. Currently if system A has a link to system B, then the game engine will allow the player to jump from system B to system A, which is to be considered a bug.

Mxxx not working
Versions affected: Mac v1.1, don’t know about Windows v1.0.10
The Mxxx expression does not properly move the player’s ship within the target system as specified in the documentation, if I remember my test results. It is supposed to be moved on top of the first stellar in the target system, or to the center of the system if there is no stellar present. This does not occur, and Mxxx appears indistinguishable from Nxxx.

Low DeathDelay leaves ghost
Versions affected: Mac v1.1, don’t know about Windows v1.0.10
When a ship whose DeathDelay is 0 or 1 explodes, a copy of its sprite remains in space and cannot be removed even though the ship itself is gone.

Shields affecting armor after eject
Versions affected: Mac v1.1, don’t know about Windows v1.0.10
Here and here the bug is described. Apparently shield levels affect armor levels after ejecting, which can cause the player to explode again immediately after ejecting, or be rendered immobile. I don’t know if it’s still an issue in v1.1 either, but I recall hearing that shield values of 0 or 1 cause the escaped-into ship to explode immediately.

Rank discounts don’t affect outfits
Versions affected: Mac v1.1, don’t know about Windows v1.0.10
One field of the ränk resource is documented as providing a percentage discount on all ships and outfits of the appropriate government. This only works for ships, it does not work for outfits.

Autoaborting missions don’t give legal status
Versions affected: Mac v1.1, don’t know about Windows v1.0.10
When a mission is set to pay the player on autoabort, it does not grant the legal status that would be given if the mission were completed successfully, namely that specified as part of the payment to the player.

Attack Enemy Spobs broken
Versions affected: I think Windows v1.0.10, not Mac v1.1
Setting AI ships to Attack Enemy Spobs is, if memory serves, broken, but I can’t remember how.

Inconsistent behavior and unexpected restrictions

Can’t rename startup music on Windows
Versions affected: Windows v1.0.10
In v1.0.10 for Windows, the game’s startup music must be named “Nova Music.mp3”, regardless of the second entry in STR# 130. In v1.1 for Mac, the game’s startup music can be renamed, so long as the second entry of STR# 130 is renamed accordingly. The latter behavior is desirable, the Windows behavior is to be considered a bug.

Can’t relabel volume levels
Versions affected: Mac v1.1 and Windows v1.0.10
In both v1.1 for Mac and v1.0.10 for Windows, the labels for the volume levels seen in EV Nova preferences cannot be changed. In previous Mac versions, the first 9 entries of STR# 136 would alter those volume labels. The latter behavior is desirable, the current behavior is to be considered a bug.

This post has been edited by Qaanol : 01 February 2011 - 07:24 AM

@qaanol, on Oct 18 2010, 10:09 PM, said in Comprehensive list of known bugs in EV Nova:

Destroying spobs broken
I think there is a bug regarding actually destroying spobs on Windows, but I don’t know the details.

What's your source for this? It wasn't broken the last time I checked in Polycon. Coretaps and Maelstrom blasts work just fine.

One bug I have encountered recently is with ports of EVC TCs like Heart of Darkness and Realm of Prey, one that is supremely frustrating. After playing for a while, I manage to save enough money to buy a decent warship (a Marauder in RoP), and then, a few minutes later, the game goes kaphooie moments after taking off from a planet. That save never works again. Oddly, it only happens with EV Classic total conversions. In case you don't already know, I'm playing Windows EVN.

I believe those are bugs associated with the Nova ports for the Classic TC, not the Nova engine itself.

From what I have seen in progressions of WinNova, the destroyed stellar bug seems to have come and go, and is functioning correctly with 1.0.10.

Having just tested trying to change STR#136 in EVNEW, it does not seem to change the volume labels in the preferences, but I would have to try another Windows machine, preferably running XP to confirm this change. I've noticed that both Vista and Win7 have a tendency to protect the system folders in strange ways, often leading to changes in Nova files not being saved unless a new file name is created (and oddly, the file reverting to the last saved copy under a previously saved file name if the file name is changed to that previously saved file name.)

I can also confirm that setting ship AIs to attack enemy stellars does not work, but I have had difficulty with both inherent AIs and getting ships to follow government orders, so it could be my fault and not the engine's.

The roid size is also an issue on Windows, when used with Guy's Resolution Patch, as is the 50% speed bonus, just in case that matters.

@qaanol, on Oct 18 2010, 09:09 PM, said in Comprehensive list of known bugs in EV Nova:

Shields affecting armor after eject
Versions affected: Mac v1.1, don’t know about Windows v1.0.10
Here and here the bug is described. Apparently shield levels affect armor levels after ejecting, which can cause the player to explode again immediately after ejecting, or be rendered immobile. I don’t know if it’s still an issue in v1.1 either, but I recall hearing that shield values of 0 or 1 cause the escaped-into ship to explode immediately.

It's shield value 0 only, and yes it still affects the game. I'll also add shield outfits do not affect this, only the ship's inherent shield value. So, even if your ship comes with a shield outfit that adds 32766 shields but has zero shields on it's own, it'll explode after ejection.

Never heard of immobilization as a result before, however.

QUOTE (Qaanol @ Oct 19 2010, 03:09 AM) <{POST_SNAPBACK}>

Low DeathDelay leaves ghost
Versions affected: Mac v1.1, don’t know about Windows v1.0.10
When a ship whose DeathDelay is 0 or 1 explodes, a copy of its sprite remains in space and cannot be removed even though the ship itself is gone.

This may be a bug, but it's also useful for plug-in developers. For instance, it could be used to create a "ship graveyard" of unboardable vessels.

QUOTE (Lindley @ Oct 21 2010, 05:01 PM) <{POST_SNAPBACK}>

This may be a bug, but it's also useful for plug-in developers. For instance, it could be used to create a "ship graveyard" of unboardable vessels.

That can be done much more easily in other ways.

Guy sent me a long list of bugs, and I will add them into my first post as I have time to format them properly. Meanwhile, here they are in plain text:

1.1 Issues:

• Pure white portions of cicns are transparent (even if the mask says otherwise).

• New/Open/Prefs dialogs unresponsive on 10.3.9.

• Nova Ships 8 is redundant, race movies shouldn't have resource forks, music shouldn't have (incorrect) type/creator codes, Nova-DF.rsrc should be check-summed (to avoid exploitation by unregistered users).

• Filenames are missing from debug log sections for "opening files in Nova Files/Plug-Ins folder"

• Plug-Ins section in the Help doesn't clearly indicate where the debuglog should be created.

Engine Limitations:

• Non-simultaneous weapons can fire no more than once per frame.

• Negative DatePostInc doesn't work. We need to travel back in time!

• Perses not present when a pilot is created will all be assumed to be dead.

Engine Bugs:

• Beam hit detection is terrible. Beams can pass right through large parts of a ship without hitting.

• Non-infinite aux ships are lost on quit. Ie, if you have a mission which has a fixed number of aux ships but you quit the game before completing the mission, when you next load that pilot the aux ships will be gone.

• RLE colour runs aren't affected by colouring/transparency/murk.

• Starfield is also not affected by murk.

• Exit points don't work for carried fighters - they just always come from ship center. The additional downside to this is that you can't use negative inaccuracy to make fighters come out sideways.

• Player's ship can only turn at rates in multiples of 10 (30°/s), despite what's shown in the player info. AI ships have no problems.

• Ranks only discount ships, not outfits.

• If you have an IFF jammer planets still won't let you land. When you hail them though they appear all happy and friendly and you can't offer them a bribe to let you land. You have to demand tribute to turn them hostile and then you can offer them a bribe.

• Missions where you have to retrieve cargo from multiple ships don't seem to work very well. When you board the first ship you'll retrieve the complete quantity of cargo but you can't complete the mission without boarding the others too. To board the remaining ships you need to have the same amount of free cargo space again but when you actually board them you retrieve 0 tons. Ideally, the cargo quantity would be distributed across all the ships.

• The choice of nebu picts is messed up - it prefers to scale small picts up rather than large picts down. Even if the large one is only 1 pixel too large for the current scale it'll choose one half the size and blow it up. Looks really bad.

• Outfits set to modify max guns/turrets don't stack. If it's set to give you 2 more turrets and you buy 4 of them then you still only get 2 more turrets.

• The Hxxx ship changer (and probably Exxx too) doesn't give you any carried fighters that might come with the new ship - all you get is an empty bay. Same thing also happens with the ship the player is given when starting the game.

• Weapons that draw ammo from other weapons can cause incorrect free mass readings in the ship info dialog. The mass of the ammo is added to the free mass reading. If you buy the ship it has the correct amount though.

• Fail texts are dependent on CanAbort, in that the mission will only be "persistent" on failure if CanAbort is false. This may not be a bug but it makes things really difficult and I can't see any good reason for it. Missions should instead check for the presence of a fail text to determine whether or not it is persistent after you fail it. They would also need to be non-abortable after failure (regardless of CanAbort) to prevent OnFail and OnAbort from both being run.

• Systems that change due to visbits will often be coloured on the map according to your status in the previous system (the one with the lower ID) rather than the new one. The same applies to message buoys - the previous string will always be shown instead of the new one.

• Sometimes ships will become paralysed if you hit them momentarily with a tractor beam. Hitting them again will bring them back to life.

• Sometimes map outfits will not reveal all systems within the specified number of jumps. This is to do with the ordering of the hyper links - Nova doesn't always take the shortest route to a system so it thinks it's further away than it is.

• Missions where cargo is to be picked up from special ship and dropped off at travelstel will allow you to complete the travelstel objective before picking up the cargo.

• Ship trade-in value sometimes appears higher in the player info extras pane than in the shipyard. I'm guessing that it's including persistent outfits in the extras pane while the shipyard is correctly ignoring them.

• PD beams will sometimes fire at targets way out of their range. I'm guessing this happens when it fires at one target that is within range and kills it but the count of the beam requires it to stay on screen for longer so it acquires the next target whether it is within range or not.

• A target is determined to be in or out of a weapon's firing arc (front, sides, rear) based on the angle from the centre of the firing ship, rather than the exit point the shot is coming from. For example, a front-quadrant turret can fire backwards from its weapon exit point if the target is behind the weapon exit point but in front of the firing ship.

• Smaller asteroids don't appear in higher res. This is somehow related the actual size of the sprites and can be avoided by padding them out to make them larger.

• When Gxxx is used in the OnBuy field of a weapon or ammunition outfit the actual outfit you're trying to buy does not get given to you (symmetrically, Dxxx in OnSell). This can be worked around by making the outfit Gxxx itself as well. DO NOT FIX - Plug-ins that use the work-around will be broken.

• Crons don't work! There would appear to be multiple bugs at work here so fixing even just one of them would be a welcome improvement.

• Missions with random travel/return stellars when accepted from a stellar whose system will be changing the next day will fail to find an appropriate travel/return stellar. More info.

• Dude specific advice STR#s often fail to load all entries.

• 'Owned' spobs (using the "always dominated" flag) have a minor glitch when hailed. The middle button reads "Leave" and appears disabled but you can still click it to evoke a 'no response' from the spob.

• A number of people have complained bitterly about the shan 0x0002 flag "unfolds to hyperjump and land". It would be far more useful if it did NOT unfold to land, but only for hyperjumping.

• Govt borders on the map are only drawn in a 512x512 area, which is a problem when using plugs that change the map size. Ideally it would be drawn to the same size as the DITL element for the map area. The performance of the govt borders is already pretty poor though, so I'm not sure how well it would work with a really big map.

• The 'Auto-Machine-Gun' bug: An issue with beam decay. I'll talk about the Winter Tempest which it affects in a big way, though it also affects some other beams in the game.
Prior to EVN 1.0.A, when you held down the fire key for the WT, the beam would fire on every frame but not decay until you stop firing. This was more-or-less fine except that it didn't always work. If you had other primary beams (like the BRL) on your ship which fired at the same time then each time the WT fired (every frame) it would also decay and the overlapping beams would build up and cause extreme damage to anything crossing its path. Alternatively, you could rapidly press the fire key rather than holding it down and the same thing would happen.
The 1.0.A update changed things so that the beams will always decay every time they fire, so no matter what you're doing the WT will always build up and cause extreme damage.
My proposal is a 3-stage solution:
1. Whenever a particular beam is fired from a particular exit point, kill off any previous decay of that same beam that exists at that same exit point. Ie, the same as pre-1.0.A behaviour, except working in all situations. This isn't perfect though as the player could still exploit the behaviour to save fuel on the WT by firing once, waiting for it to decay, then firing again.
2. Decay the beam's damage down to 0 as the beam itself decays. This would make decay more logical and also provide a disincentive to exploit the beam as mentioned above.
3. Draw out fuel consumption over the life of the beam. Ie, rather than x units of fuel per shot, use x/count units of fuel per frame. Consume additional, decaying quantities of fuel as the beam decays. Kill the beam immediately if there's not enough fuel. This way the player is 'paying' for the additional damage done by beam decay, if and only if the beam does decay.

• FPS vs 30ths of a second: Certain statistics in Nova are based on the current framerate, while others are based on a timer ticking at a rate of 1/30 of a second. The problem occurs primarily with weapons, where the reload depends on the 1/30 timer while the duration depends on the framerate. For example, a beam set to 14 reload and 15 count should appear to be a constant beam if fired continually but in practice, with an average framerate of 47 FPS, there is a very noticeable gap in between beam durations. This could also happen the other way: with a much lower framerate (e.g. in a big battle), the beam would last longer than the reload timing. This isn't just a cosmetic bug; since no weapon can fire faster than once every frame, slower computers will be able to deal less damage per second than faster computers with some weaponry, such as Ion Cannons, Bio-Relay Lasers, and Hail Chainguns. This upsets the gameplay balance depending on a computer's speed.

• Issues with AI cloaking.
AI ships will cloak when hyperspacing: Should also be cloaked when jumping into a system.
AI ships will cloak when just flying around: Should also be cloaked when going to leave a system.
AI ships will not uncloak until close to their target: Only works for carried fighters.
AI ships will cloak when docking: Doesn't seem to do anything. Assumed behaviour is for carried fighters to cloak when returning to mothership.

• 'Pirates' take care to disable but not destroy their targets - their weapons will always leave at least 1 armour point on the target. However if a ship only has 3 or less points of armour it cannot be disabled, leaving it invulnerable to further damage from the pirate. In these situations, it would be better if the pirate simply destroyed the ship.

• Font behaviour has been kludged on the Windows version of Nova. Requests for Mac fonts like Geneva or Charcoal are unnecessarily translated to Arial, meaning if the user were to install these fonts they would still not work.

• The hyperspace flash on the Windows version of Nova does not 'build up' like it does in the Mac version. This is why Windows users have been complaining about the flash.

• There have been many reports of compatibility issues with QuickTime on Windows.

• On Windows Vista, users may not have permission to write to the program files folder or may need to explicitly give permission.

Scenario Bugs:

• The 200mm railgun is inferior to the 150mm. The only advantage is the increased mass damage but the vastly increased reload time more than cancels that out. Not to mention the greater decay and increased weight and cost. Also, I think the larger railguns should have greater range than the smaller ones rather than the other way around.

• The Fission Reactor is heavier and more expensive per unit of fuel generatation than Solar Panels and provides no additional advantages. Eg, you can buy 3 Solar Panels (9 tons) for a fraction of the price of a Fission Reactor (10 tons) and enjoy faster fuel generation than the Fission Reactor.

• Set and launch trap mission is way too hard. The escorts jump in and destroy the poor little guy before you can say Old Grey Fox.

• Multiple Ion Cannons (either variant), BRLs or TBRLs do not stack damage as they cannot fire more than once per frame. Qaanol's plug-ins includes a number of methods of fixing this, each with various downsides.

• Vell-os abilities are lost on eject. Qaanol's plug-ins includes a method of fixing this.

• There remains an exploit allowing you to do multiple strings on the same pilot. Qaanol has the details.

• STR#s 4001 and 4002 are missing entry 80 "*Samantha".

Scenario Bugs fixed in Mac Nova 1.1 but still present on Windows:

• junk 138 (Ancient Vell-os Sculpture) lowercase name missing an o: "ancient Vell-s sculpture"

• Mistake in desc 314 (Kymonth Station): "This is where most critical patients and battle-injured warriors are bought."

• Mistake in desc 4135: "Upon seeing you a there is a sudden hush"

• Mistake in desc 4544 (need to escape speech marks): "This Eiric may be a different man altogether{b809 ", although by your reaction," he smiles, "I think this may be a man we count on." "."} Techerakh would be going himself..."

• Mistake in desc 9307 (missing speech marks): "{G"His" Her"} honor is impeccable..."

• Mistake in desc 9368: "she asks slightly impatiently as you make her way over."

• To work around an engine bug involving asteroid sprites on high res screens, the sprites should be padded out to about 50x50.

• The Vell-os area map only works every three days. To make it work every day, set the PreHoldoff to 0 and move OnStart string to OnEnd (to work around a cron bug).

• To work around an engine issue involving beams with decay, the Flower of Spring, Summer Bloom, and Winter Tempest should have their decay removed.

• The Auroran Cruiser and Thunderforge ship resources have garbage values in their moviefile fields, which causes Win Nova to crash when selecting these ships in the shipyard.

Bible Errors:

• oops Stellar: Spob range should be 128-2175.

• oops Stellar: -2 (mission-related news) is not a valid value. This functionality from the EV/O days has been replaced by crons in Nova.

• weap Flags: 0x0008 (don't fire at fast ships) is not a valid flag. This functionality from the EV/O days has been replaced by smarter AI in Nova. The AI will automatically determine whether or not to fire guided weapons at a target based on the capabilities of the weapon and the target.

• Game Constants: Max Crons (512) is not mentioned.

• Game Constants: Max Person Types is actually limited to 1023 as the 1024th ID is reserved (for Hector?). Note: 1023 is the Bounty Hunter.

• misn ShipStart: -5 through -16 are also valid values for other spobs in the system.

Features not mentioned in bible:

• Falloff for a projectile weapon will cause the shot to fade out if positive or fade in if negative.

• Zero-speed warships are treated as "defence platforms" and will be placed in formation around the system centre.

• AI ships set to scoop asteroid debris but lacking the means to do so will go into "economy-at-work" mode, continually travelling between two stellars in a system.

• Duplicate perses are treated as a single pers with an increased chance of appearing.

QUOTE (Qaanol @ Oct 29 2010, 12:08 AM) <{POST_SNAPBACK}>

• Ship trade-in value sometimes appears higher in the player info extras pane than in the shipyard. I'm guessing that it's including persistent outfits in the extras pane while the shipyard is correctly ignoring them.

I always assumed this was due to ranks discounting ships and including the player's ship for the discount. If the player has a rank giving them a 10% on ships, I believe their own ship's trade-in value will also be subtracted by 10%.

DispWeight does not control the order that missions are offered in the bar. The Nova Bible says, “DispWeight Controls the order that the mission is presented in the bar and mission BBS list. Missions with higher DispWeight values are presented first.” but missions are offered in order of increasing resource ID, on Mac Nova 1.1.

There is a bug with Economy At Work ships sometimes becoming hostile to you when you request assistance. Here is a topic which confirms it.

I have three more related to Mac Nova 1.1. First is that the frame rate on an Intel is about five times lower than a similar PowerPC machine (link). Second is that on PPC Mac Nova 1.1, smoke trails and asteroid particles do not disappear (link). Third is that the enter key on my PowerBook no longer mimics a return (link; I no longer consider my advice to keep 1.0.10 handy useful in that post. The new plug-in system makes up for it.).

Another crön bug.
(You can argue that this isn't a bug since the bible doesn't clearly define the behaviour but I'm calling it a bug)

Date ranges don't work as expected. The day/month range is treated separately to the year range. This results in a scenario bug which will make a good example:
The Terraforming Start crön specifies a date range of 1/1/1178 to 1/1/1179 with a 40% chance of occurring on any day in that range. Essentially the chance that it will never occur should be 0% - the random factor just means it won't necessarily happen on the first day.
But Nova instead decides it can only occur on a day that is both within the day/month range (1/1 to 1/1) and within the year range (1178-1179), with the result being that there are only 2 days it can occur on: the first day of 1178 and the first day of 1179, together giving only a 64% chance of ever opening the Terraforming string. Changing the last date to 31/12/1178 would work around the bug (setting both dates to -1/-1/1178 should also work but I haven't tested how well ignored fields work).

Any chance of setting up a wiki page or something?

This post has been edited by Guy : 13 January 2011 - 08:11 PM

The EVN Wiki does have a category for "Bugs and Exploits" here. Feel free to create a few articles describing some bugs and add them there.

Bay launched fighters only take 75% damage (they still regenerate at the correct rate). This is undocumented, and I call it a bug. It applies to both player and AI-launched fighters (although I did not check AI fighters damaged by AI weapons).

I’ll also call it a bug when a weapon deals damage to remove the last of the target’s shields, it also deals its full armor damage to the target. What should happen is if it takes X% of the shield damage to remove the shields, then (100-X)% of the armor damage should be applied.

This post has been edited by Qaanol : 01 February 2011 - 02:10 AM

If an AI ship fires a weapon, the impact from that weapon (and its submunitions) does not affect the ship that fired it.

Negative recoil does not work for the player.

This post has been edited by Qaanol : 03 February 2011 - 12:29 AM

I've also noticed that ships with less fuel capacity than yours can top off your tank. Happened when I was in a Heavy Shuttle. A Fed Viper came up to me and filled me up all the way, which is weird since it has 3 jumps and I had 4 total.

Wait, you mean you had no fuel and this Viper completely filled your tank? I've never seen that. Every AI that's ever refueled me only gave me enough for one jump.

@darthkev, on 10 February 2011 - 02:27 AM, said in Comprehensive list of known bugs in EV Nova:

Wait, you mean you had no fuel and this Viper completely filled your tank? I've never seen that. Every AI that's ever refueled me only gave me enough for one jump.

Filled to the top.

If you are disabled your fuel bar reads 0. Requesting assistance will get you repaired and then your fuel bar will read normal again. It may seem like the other ship is giving you a boatload fuel but it actually isn't. Not a bug.

@guy, on 11 February 2011 - 05:12 PM, said in Comprehensive list of known bugs in EV Nova:

If you are disabled your fuel bar reads 0. Requesting assistance will get you repaired and then your fuel bar will read normal again. It may seem like the other ship is giving you a boatload fuel but it actually isn't. Not a bug.

I wasn't disabled, I was out of fuel.

@spartan-jai, on 11 February 2011 - 06:03 PM, said in Comprehensive list of known bugs in EV Nova:

I wasn't disabled, I was out of fuel.

Test this with both almost full fuel and being disabled, then test this with not-disabled but out of fuel, and then get back with the answer. Oh, make sure your ship has some ridiculous amount of fuel, like 20 jumps, and give the rescuing ship, say, 4 jumps of fuel.

Log in to reply