Incubator branch Thread - Vector Thrust

For the moment it is active a new branch that will allow the players to see the new development as they progress.
You can opt in the Incubator branch by following these steps:

• Right click on Vector Thrust in the steam client.
• That will open a context window, then go to Properties and in Beta's tab you will find a combo box.
• There select “Incubator”
• The steam client will update VT and then you can play

Important: the Incubator is a development branch and may be unstable

This thread will be used to discuss and provide information as new updates become available; some may be too small to be created an announcement.

Copypasta from my previous comment:

The update makes Ziz Hunt mission insanely laggy (other mission/skirmish with Ziz still works fine)

The log got constantly spammed with the following error during the lag, thus giving the log file large size (~16 megs for less than 1 minute from starting the mission until I have to AltF4 out of the game) as the consequence:
"Error loading texture Ogre/ShadowTexture0. Texture layer will be blank. Loading the texture failed with the following exception: OGRE EXCEPTION(6:FileNotFoundException): Cannot locate resource Ogre/ShadowTexture0 in resource group Internal or any other group. in ResourceGroupManager::openResource at ..\src\OgreResourceGroupManager.cpp (line 763)"

Edited by: Nergal01

Maybe it has to do with the unit or weapon that you used. I used the Su-37 and the log was clean

I used F-14 and MiG-29 and both ends with same result

From what I tried several hours ago my game also crashed when playing campaign Restless Bonds chapter 3 (crashed during gameplay), I saw the log and there are a lot of lines saying error loading texture.

I played in skirmish for a bit with the new update. Now this may be related to either my computer being on the low end or an actual glitch, but when planes are using chaff/flares from afar, they appear as white rectangles corresponding to where the particles are at in the air. When I'm closer, it all looks normal. Also lag is an issue as flares and chaff are used gratuitously by all AI planes.

Also with this update, it seems like standard missiles turn into the player aircraft at times causing damage to the aircraft and even destroying it. Mainly the situation arises when a missile comes off a rail on the opposite side of the player aircraft when launched against a target aircraft off center and opposite to the side of the launching missile.

Edited by: Raptor_101

Missiles spoofed by countermeasures considered as hit.

Also dealing with Ziz sometimes end up with myserious crash, nothing unusual in the log aside the usual "OGREEXCEPTION:chaff reactor/.skin/white.png not found" in the last lines. Since it occur when I'm fighting Ziz in a crowded mission (my Black Label mission), it may be a memory leak perhaps?

Edited by: Nergal01

Both campaings experince crashes after the update. In both cases the triggering event seems to be the destruction of a J-35J.

Here are Ogre.log files for both cases: Mediafire.com

In addition, tried to move Restless Bonds missions 4 and 7 to Battle Scenario to test anti-ship and anti-SAM tactics.

Mission 4 works fine, while 7 crashed with these being last lines from the log:

19:47:38: Texture: spark1.png: Loading 1 faces(PF_A8R8G8B8,64x64x1) with  hardware generated mipmaps from Image. Internal format is PF_A8R8G8B8,64x64x1.
19:47:51: Texture: WaterSMedBull_h.png: Loading 1 faces(PF_A8R8G8B8,128x128x1) with  hardware generated mipmaps from Image. Internal format is PF_A8R8G8B8,128x128x1.
19:47:51: Texture: Blast_DarkRing1.png: Loading 1 faces(PF_A8R8G8B8,256x256x1) with  hardware generated mipmaps from Image. Internal format is PF_A8R8G8B8,256x256x1.
19:47:51: Texture: Blast_AfterSmoke.png: Loading 1 faces(PF_A8R8G8B8,256x256x1) with  hardware generated mipmaps from Image. Internal format is PF_A8R8G8B8,256x256x1.
19:47:51: Texture: Blast1_RingFlare.png: Loading 1 faces(PF_R8G8B8,512x512x1) with  hardware generated mipmaps from Image. Internal format is PF_X8R8G8B8,512x512x1.
19:47:51: Texture: Blast_MDebries.png: Loading 1 faces(PF_A8R8G8B8,256x256x1) with  hardware generated mipmaps from Image. Internal format is PF_A8R8G8B8,256x256x1.
19:47:57: OGRE EXCEPTION(6:FileNotFoundException): 'BattleScene\RB_Miss7/Objects/Reactor/KH-31A_Live.ini' file not found! in ConfigFile::load at ..\src\OgreConfigFile.cpp (line 84)
19:47:57: Texture: RocketEff_RingFlare24.png: Loading 1 faces(PF_R8G8B8,256x256x1) with  hardware generated mipmaps from Image. Internal format is PF_X8R8G8B8,256x256x1.

Edited by: John_Silver

Nah those lines are unrelated to the issue.
I’m already working in a fix for some of the issues I’ve seen, but I’m not sure if I should add a new executable that really prints every step, but it really drops the FPS.
But I can add it in case someone is really interested in catching those bugs.

Well, bug-catching logger as optional exe would be nice. The faster we get those bugs the faster we can enjoy the game and actually check out new features.

On a somewhat unreated note, TimeS is it possible to add temporary "Unlock all planes" option until VT's full release?
It's rather tiring to manually edit all the ini files after each update.

John_Silver wrote: TimeS is it possible to add temporary "Unlock all planes" option until VT's full release?

All my this, although you can now fly all plane from the editor's test mode.

Okay, I may not be able to add everything that I was planning for today, but I’ll still update the build.
It will be 0.9108.
In that version press F-11 in the challenge mode to unlock all. (Everything will go back to normal after you shut down the game)

timeSymmetry wrote:
In that version press F-11 in the challenge mode to unlock all. (Everything will go back to normal after you shut down the game)

Maybe it's better to make it a switch: press F11 once to unlock all (saves on exit), press second time to return to normal?

Resetting after the exit would defeat one of the main purposes I wanted this feature for - easier custom skin\loadout testing. Since editing the ini files once would still be less of a hassle than unlocking planes every time needed to check custom skin\loadout (each requires 3-6 checks in average).

Edited by: John_Silver

That is a good idea, but I uploaded the new build a few moments ago, I´ll enable it in minutes.
But I can make it act like that in the next build.
The build that prints log is in the VectorThrust_log.exe (but should be used only when trying to catch bugs, the log file can grow over 100mb in just a few minutes)

the version 0.9108 is now available

A-10A challenge mission crash. It seemed to me at first this was happening when I hit a target with the main gun, but after this try, it seemed like it was everything in the second area where the actual objective is attempting to target me at the same time was what got it to crash:

Mediafire.com

For that buggy MiG-21PF challenge, here's the extended log where it crashes when one of my missile is nearing one of the target plane.
Dropbox.com

Edited by: Nergal01

I’m already on that issue Nergal01, now is the best part, to begin the detective work to find the cause of that issue.
I’ve found the reason for that, NT-43A are now configured as jammers and at the moment it seems jamming options conflicts with destroyable projectiles.

timeSymmetry wrote: I’m already on that issue Nergal01, now is the best part, to begin the detective work to find the cause of that issue.
I’ve found the reason for that, NT-43A are now configured as jammers and at the moment it seems jamming options conflicts with destroyable projectiles.

But what made it crashes before you implement destroyable projectiles? The update that made it unplayable was v0.9105, I think?

Then we have two issues, but it is possible that I added the NT-43A as a jammer around that time.

Seems both crashes during the campaign mode play has logs ending with similar lines:

16:57:59: SEARCH_ENEMY_Update
16:57:59: _____getEnemyInRangeL_____
16:57:59: rangeGrnd _2210
16:57:59: rangeAir _2210

Full log for the Restless bonds mission 2:
Mediafire.com

Same with the Restlesss Bonds mission 7 crash.
Full log:
Mediafire.com

Edited by: John_Silver

@ John_Silver, okay I’ll see that in a minute.
I’ve fixed the issue with the projectiles that appeared in the first and second challenge of the MiG-21 family.
I’m now working on the second issue that was probably present in the v0.9105

MiG-21PF challenge has been fixed

TS, could you please implement proper time setting in the editor in the next update? It's still have to be done manually via text editor as for now.

Roger!
it will be added in the map tab on the info window

The Su-37 challenge mission is now considered complete after you destroy the first 2 F-35's.

Considering countermeasures: QAAMs are now nearly useless. Maybe they should be tweaked a bit, so that they ignore flares?

Edited by: John_Silver