You also have to take into account VALVe's priorities are: 1. VALVe 2. Everyone else
The Source SDK is basically just ripped from their *src/* folder which contains the engine, VPhysics, Havok, etc. They aren't going to re-organise the entire code base just to suit 20 people who want to save 1 hour per week with the improvement it results in. Thanks, - Saul. 2009/8/29 Paul Peloski <[email protected]> > The SDK is improving all the time, but only to the extent necessary for > Valve to make awesome games. While an XML-based weapon system might be what > *you* need, or maybe what *you think the community needs*, it's not what > Valve needed. I suggest if that if you have list of massive improvements > that *you get to work on them*, or pick an engine that already has the > features and tools you need. > > Paul > > On Sat, Aug 29, 2009 at 3:37 PM, Joshua Scarsbrook <[email protected] > >wrote: > > > Hi Tony > > > > I think that the source sdk is a bit out dated; I think that with the > > realece of hl2ep3 or just after it, there needs to be a massive > > improvement in the source software development kit. For one there needs > > to be a weapon generator that uses tags and xml to define a weapon a > > basic weapon to speed up development of new weapons. For two there > > needs to be a technical improvement to hammer. Hammer as said by many > > members of the community is out dated and needs to be improved; a simple > > improvement would be to add a progress bar to the run map window, also > > there needs to be a lighting render button to give a preview of the dev. > > In addition, there needs to be profiles added to the engine, say like a > > dev mode, which does not load custom content. Another thing would be to > > add crash tracking in the engine, the report bug system is not > > implicated enough and most map devs will understand technical details. A > > micro-engine in hammer to test whether a player can fit under a league > > is also a importing thing. A defeat visleef system would be a very > > powerful improvement to show things the player would be seeing and only > > that. The hammer editor is treated very much like a cad program and > > should be made easier to understand and with inbuilt documentation to > > help newcomers to mapping, the doc would be placed as tooltips and info > > in the entries window. In addition, it would be important make the > > skeathup plug-in more available though it is hidden in the source sdk > > gcf. In addition, improvements need to be made to the documentation of > > the source sdk, such as a separate wiki that contains a detailed > > expiation of what each coding file does. With all of this said I think > > that the source sdk and Valve Developers Wiki is out of date and both > > need an improvemt considering the amount of people that use them. Also > > worth noting, that it is too hard to change basic game play rules and > > they should be in a collective header file. What I propose is both > > employees of valve and the coumumatiy surrounding them do this as to > > continue communality support for years to come. Though these > > improvements would require a lot of development, I think that they would > > appeal to the entire communality. > > > > Thanks, > > > > Vbitz > > > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
