Jump to content

dprostock

Members
  • Posts

    661
  • Joined

  • Last visited

Everything posted by dprostock

  1. I'm going to upload some examples. In the first series, I take a series of designs saved in Subassembly with a new VAB editor. The design in question is the "Venusino III" with a number of important pieces. I can bring it without problems, I can re-call another design "Venusino III" without inconvenience and stack them. Now I'm going to perform another stack: "Bus con frenado aerodinamico" (the third one on the list ). At the same time I will stack the pre-design "Spider" to which I must rotate to assemble it. It can be observed that there are no problems beyond that the cap does not add up because it is pre-armed. Please note the piece I have selected in the second image of the next series. New situation. I select the design listed as "Boya FTL". The design is turned over to the editor with the problem, the engine, which is the root, appears separated from the rest of the body of the vehicle. I proceed to correct by unifying the design. I save/re-record it, delete the VAB editor to new, and proceed to select the "Boya FTL" that brings back the same part separation problem. I note that all designs, those that work and those that fail, share pieces of the same mods.
  2. In both situations. I design a vehicle, and I keep it on the VAB list. When I select it in blending mode to add it to a new design, what you have observed happens. Similarly, if I save the design as "subassembly" and select it, the same thing happens. This also happens when I start the design to "new", bring the vehicle with its parts completely separated or stacked in the wrong way. My impression, which at the time of saving, erroneously records the relative position of the pieces. I have just noticed that when at the time of design, I duplicate a set of pieces, the same mishap happens, changes the spatial positions and totally breaking the original design. They obviously have a serious problem.
  3. OMG! About ten days ago when I picked it up I found the same problem. I reinstalled the BSP again and rechecked the last installed mods (last three months) without being able to detect where the error was coming from. Now I confirm that it is obviously another of the problems of Bugs Space Program....
  4. Laythe Thank Mods - DanGerous Systems With Jool and Kerbol on top. All on the ground! Moments before the eclipse. Other
  5. At Eve's highest point. ( 7542 mts. ) Critical location information:
  6. KSP es inestable por naturaleza. Debes preveer tener backup y puntos de control a fin de no perder toda una campaña. Eso te va a desarrollar los músculos necesarios para soportar el KSP2 que está desarrollado en la misma plataforma.
  7. It is clear that the promises to sail in a Trasatlantico have been futile, at most we will have to be content with a raft of tied barrels ...
  8. For that and for youtubers the KSP is great, especially for assembling marvin the Martian type ships, but nothing more than for it.
  9. What do I want from KSP2? Easy: Don't have the burden of errors and horrors that KSP1 has had. Bugs that have not stopped to fix and abandoned in the KSP1.
  10. Want to hear from me? Why? Did they correct all the flaws in the KSP?
  11. Brillante! Es la causa por la cual no soy capaz de hacer videos. Selección de momentos, imágenes, banda de sonido, ajuste de tiempos... simplemente supremo.
  12. thanks for what you did. Too bad you were great.
  13. Si no usas el SAS es suicida.... Más fácil? Anotate estos canales: https://www.youtube.com/channel/UCVBxic53ktUbUCblbFYegDQ https://www.youtube.com/channel/UCq_QMLGDNLbG5QZuKFEMO2g Si te haces una maratón, en 24 horas te vas a Eeloo.
  14. Best regards! I don't know what the implementation of the "surprises" will be and if you're there, but it would be nice if, as it exists in KSP1 the Memorial, a Class F or G asteroid named Collins is located in orbit to Mun. Something similar should be included in a low Kerbin orbit, called Yuri.
  15. Yeeeepppppppppppppppppppp..............................................................................................................................
  16. Yep. Probably looking at the results, there may be a change of course, until the possibility of changes in the marinery... Things that wouldn't reflect well on labor network pages...
  17. Mmmmm.... Should people like NovaSilisko go back to the rodeo?
  18. Relative. It will depend on leadership and design. Despite the change in air and the passage of time, many people continue to behave or have the same ideas. They're called "ticks".
  19. He could also give the example of a developer who was a genius, but followed his life in another company. When a modification had to be made, the new developers were not up to the challenge. Anything can be.
  20. I don't know about that. They may not know how to treat it, because if it is a ticket opened by other users in previous versions and is critical with respect to the use of a control piece acclaimed at the time as fundamental to a DLC, it may also be thought that the person who designed it is no longer on the computer and those who current developers do not know how to read the code.... Anything can be.
  21. That question is for the project leader who defines how action should be taken. Or do developers act on their own at their discretion? Anyway, I have an open ticket, with the reference files for study, which turns out to be the same error indicated in an earlier version ticket, and still has no solution. That is, an error that is moved from version to version with all the information collected from the the same and the files in question... We don't indicate which lines of code the event is raised on?????
  22. That's why I'm right, just because the developers are the same doesn't mean they make the same product. The problem is in the topic of leadership, production and design.... And if you hire the same people, there are doubts as if they don't bring too many "tics", there was something better in the market, or you got into a business that you don't know well.
  23. Yea!!!! = https://bugs.kerbalspaceprogram.com/issues
  24. https://bugs.kerbalspaceprogram.com/issues Simple, check the list and see how many bugs have been fixed and how many still appear version after version.
×
×
  • Create New...