Hello Guest November 25, 2024, 20:50:24 *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
Pages: 1 [2]   Go Down

Author Topic: Mission Editor  (Read 8589 times)

Subwolf

  • Forum member
  • Posts: 398
Re: Mission Editor
« Reply #25 on: October 27, 2010, 16:11:15 »

Will the mission editor be released as part of another update which includes more fixes as well? I remember Frank from Vstep mentioned that the mission editor will be released two weeks after the last patch, but now it's getting close to a month. I can see he has deleted that now btw.

But a release should happen soon, I'm sure that a lot of players have finished the few missions included in the game. And now I'm sitting on deck with my feet in the water, waiting for something to do ;)
Logged

mvsmith

  • Guest
Re: Mission Editor
« Reply #26 on: October 27, 2010, 16:27:32 »

That has already been covered in another post: V1.3, which is being tested now, has the mission editor as an integral part of SSE.
The ME is not a separate program as it was in SS2008.

V1.3 cannot, or should not, be released until it has been tested and any bugs fixed. It is not possible to predict when all the bugs will be found and fixed, so any date would be little more than a guess.
If I were to make a guess, it would be early December.
Logged

larsdehaan

  • Guest
Re: Mission Editor
« Reply #27 on: October 27, 2010, 18:55:29 »

so the me will be in 1.3 and its coming out in september?  :'( :'( CAN'T WAIT THAT LONG (sorry for caps) jeez man 2 weeks after the release of 1.2 it was going to be released and pjort told me so cry
Logged

ScubaChris

  • Forum member
  • Posts: 21
Re: Mission Editor
« Reply #28 on: October 30, 2010, 15:32:54 »

After losing all my save games to corruption due to bugs in the 1.2 update I'd honestly much rather be patient and allow Vstep the time they need to iron out any 'kinks' in 1.3. No point in rushing it out.  ;)

C.
Logged

mvsmith

  • Guest
Re: Mission Editor
« Reply #29 on: October 30, 2010, 15:55:26 »

...Frank from Vstep mentioned that the mission editor will be released two weeks after the last patch,,,,

Indeed, but we have not yet seen the last patch, or patches.
Logged

The Ferry Man

  • Forum member
  • Posts: 10787
Re: Mission Editor
« Reply #30 on: October 30, 2010, 15:56:41 »

Indeed, but we have not yet seen the last patch, or patches.

No he meant the v1.2.2 patch
Logged

TFMs Guide to Crossing the Dover Channel (http://forum.shipsim.com/index.php/topic,21107.0.html)

mvsmith

  • Guest
Re: Mission Editor
« Reply #31 on: October 30, 2010, 17:51:26 »

When he thought that would be the last patch.
Logged

Captain Canuck

  • Forum member
  • Posts: 29
Re: Mission Editor
« Reply #32 on: October 30, 2010, 23:24:25 »

Indeed, but we have not yet seen the last patch, or patches.
Does that make 1.3 the "last patch" then? ;)

It is not possible to predict when all the bugs will be found and fixed
OH OH (wave arms in the air) I know the answer to that one... NEVER! ::) If the programmers at VSTEP can write completely bug free code they need to go work for Microsoft and show them how its done. ;D

However, maybe VSTEP should consider a public beta before release, or better yet do like Bohemia Interactive does with ARMA2 and let anyone that wants download the "nightly build". The real problem isn't writting bug free code, but writing code that works with everyone else's buggy code (graphics/sound drivers, Direct X, Windows etc.). To test that VSTEP needs their code running on as many machines as possible.

Cheers.
Logged

mvsmith

  • Guest
Re: Mission Editor
« Reply #33 on: October 31, 2010, 07:33:40 »

...The real problem isn't writting bug free code, but writing code that works with everyone else's buggy code (graphics/sound drivers, Direct X, Windows etc.). To test that VSTEP needs their code running on as many machines as possible.

Cheers.


Hi Keith,
That is true; it might have saved some trouble if the betas were tested on average systems.
An open beta is not feasible because signed non-disclosure agreements are required of all testers. This restricts the choice to candidates of an age where such agreements are legally binding.
Too much proprietary information is exposed to make it a good idea. Even with the limited number of testers, copies of betas found their way onto the Internet.

Also, the problem was not that there were undiscovered bugs. The problem was a commitment to the publisher to release on a certain date, ready or not.
As one who studies the bug tracker daily, I can assure you that bugs are found. The problem, as you know, is in fixing them without creating new bugs. This requires complete retesting of the entire program, not just spot testing to see if a particular bug was fixed.

Unfortunately, unless the temptation to add features that have been demanded is resisted, the potential for introducing even more bugs is even higher.

Regards,
Marty
Logged

mvsmith

  • Guest
Re: Mission Editor
« Reply #34 on: October 31, 2010, 07:44:59 »

As for 1.3 being the “last patch”: So far as I know, 1.3 will contain the Editor, so that would make 1.3 the “last patch before the editor is released”, but I doubt that it will be the last patch.
Logged

Captain Canuck

  • Forum member
  • Posts: 29
Re: Mission Editor
« Reply #35 on: October 31, 2010, 20:25:06 »

If testers have to sign a NDA then it is not an "open" beta though. By definition an open beta is open to anyone. The biggest problem with open beta tests is people always think it is an opportunity to request features they think should have been included, instead of testing what is already there. The devs just have to ignore this "noise" and concentrate on fixing bugs. Beta testing is NOT the time to add new features.

Quote
The problem, as you know, is in fixing them without creating new bugs. This requires complete retesting of the entire program, not just spot testing to see if a particular bug was fixed.
Exactly, and it can turn into a mind-numbingly boring job as you play Mission X for the umpteenth time. Hence my "the more the merrier" approach when it comes to beta tests. I don't expect VSTEP to do an open beta for 1.3 as it is not just something you decided to do one day and release the next, but I think it would be a good idea to consider in the future.

Cheers.
Logged
Pages: 1 [2]   Go Up
 
 


SMF 2.0.14 | SMF © 2017, Simple Machines