The week spent fixing bugs has proved to be very useful and everyone should start to see the benefit with the final release of 5. We started the bug fixing week last Sunday when Lee came to my house sometime after 10pm. We set the computers up and it wasn't long before we were going through the bugs on the bug report forum and from emails we had and splitting things up so we both had our own areas we could work on. Didn't get any bugs fixed on Sunday night but we got the week planned out.
Started off fairly early on Monday morning and got straight into bug fixing. First on the list were some text fixes. I ended up getting bogged down in this when I soon realised that I couldn't get things right without making large changes. Ideally I wanted to use GDI but couldn't get that working the same on all systems for some reason.
Then I ended up experimenting with different approaches to improve text. I could get some things sorted but then this would affect other areas. Improve speed of rendering and I lose quality, do it the other way round and get good quality text and lose speed. It was frustrating and I couldn't find a suitable way of getting things exactly right using the same commands. Looking back on it I should have left this early on and moved onto other areas. Now I realise that the best solution to this is to add in some extra commands and then we can get both good speed and quality using the texturing system.
There were quite a few things to get sorted with sprites and I had plenty of helpful bug reports to look at with source code. Makes a big difference when you have a small project you can run and see the problem instantly.
I can then sort things out much faster. Lots of small things with sprites which weren't too awkward to get fixed. Some animation bugs existed which must have slipped through the net some time back. Didn't take long before I got these sorted. Also some problems with collision, return values and other minor but annoying things.
Later on in the day on Tuesday I moved onto the 3D Maths command set. Someone on the forums had reported a problem with this command set and the way it worked and I agreed with them so decided to change it. Basically you could create a vector2 but then call a vector3 command on it.
This caused a few annoying problems so I went through the commands and made them safer to use. There were also some bugs in there like copy vector now working.
I thought this was an odd one but soon realised what had gone wrong when I looked at the source. Must have been in a trance when writing this command as when I referenced the vectors I used the first parameter both times.
Talk about being thick. To compound matters I had done the same dumb thing in some other functions. Last fixes on Tuesday were related to matrix commands. You could shift matrices left and right but when using non square matrices the whole thing would fall down like a pack of cards. Looked at the source and realised my mistake straight away. I had assumed square sizes all the time. One quick change and that one was sorted. If only all bugs were so simple to sort.
Lots of bug reports on the forums to choose from. Started off with a file DLL problem. The save buffer for strings was too small so changed that one straight away. Then moved onto Q3 BSP and fixed a few simple bugs - things like gamma levels and texture settings.
Both are pretty much the same format so I put those into one DLL. Would like to put all BSP formats into one DLL in the future, something for us to think about with our own world format. Later on in the day sorted out problems with particles. Snow and fire particles finally work: There was some daft conflict between them and the Basic 3D DLL which had screwed things up - no longer the case. Then moved onto some bugs with Basic 2D.
Needed to change some of the drawing commands and alter some render states to avoid conflicts. Other work done on Wednesday included another fix on sprites, sorted out the problems with several sound commands, changed the way perform checklist for display mode works with the setup DLL, adjusted some code in the input DLL, fixed a crash in the system DLL and more fixes in the matrix DLL.
There was a problem with setting the last tile normal so soon had that fixed. And there was a report about matrix up and down needing swapping round so changed those.
Some bugs had been reported with Half Life and Quake 3 levels so I looked into these and started testing examples so I could see what was going wrong. I was able to make a lot of changes which will go some way to resolving problems with BSP. I fixed some loading issues with Half Life BSPs so now I'm pretty confident all BSPs will load right now, although if any don't then post a report on the forums with links to media and I'll try and fix it.
Also realised with Half Life BSPs was that I was rendering the sky box and there was no need too so I disabled this and you can now put in your own sky box which makes more sense. Other fixes for Half Life were related to collision. Some stupid bugs existed which needed fixing - the collision return functions were reporting crazy values which no longer happens, the threshold values were also being ignored, fog could not be used and there was a problem with automatic BSP and object collision which is now fixed.
It was a similar state of affairs with the Quake 3 BSP. Some collision problems with automatic BSP and object collision, some texture settings being incorrect and other things like this. One of the bugs I came across was to do with meshes - I was leaving lighting on and didn't need to do this.
Switching lighting off for meshes made them look right and they fit in now instead of standing out so much like they did previous to upgrade 5. Other fixes on Thursday were for the system DLL. The memory commands were providing wrong return values.
Didn't take long to get these sorted out now and they now return the correct values in mb. Will change this in a future upgrade so you can specify the return amount as bytes, mb or gb. Finished the day around 4 am or so. Not often I'm up till the early hours like that. Then fixed a bug with matrices.
There was a continue in a loop and when the loop did skip an iteration some important code was jumped over. Changing this fixed the ghosting issue and all seems to be working well in this department. Spent an hour or so on the multiplayer DLL to fix some bugs with that. Also added in some extra functionality so you can get the number of players in a game before actually joining. Makes it a little easier when using multiplayer. Went back to the text DLL and ajusted the code.
It's fixed some of the problems but still we have the speed issue when changing size and font. I will come back to this again when we can add in some new commands. Fixed a long standing issue with playing animations. The set volume command would not have any affect at all and it wasn't much use in it's original state.
A quick change to the code in this section soon had this sorted out and working. Other changes on Friday involved modifying some of the code in the display DLL. There were some problems with changing the window settings and after running a few example projects I was able to identify the problem and get the code changed.
Another change I made was to do with the screen fps command. Calling this command multiple times in a frame would make it seem like the frame rate was much faster. Call it twice and you get double the frame rate.
Might make DB Pro look super fast but still needs to be fixed. Apr 07, Jan 31, Upload a Thing! Customize a Thing. Dark Basic Activation Pc Download. Download All Files. Select a Collection. Save to Collection. Tip Designer. Share this thing. Send to Thingiverse user. Remixed from: Select a Collection. Microsoft only keeps a record of product keys if you purchased from the Microsoft online store. You can find out if you purchased from Microsoft in your Microsoft account Order history.
If you upgraded to Windows 10 for free from Windows 7 or Windows 8. If you bought Windows 10 or Windows 11 Pro upgrade in the Microsoft Store app, you'll receive a digital license instead of a product key in the confirmation email that was sent to confirm the purchase. That email address MSA will contain the digital license. You can use the digital license for activation. Your product key is available through the web portal for your program.
For more information, see Volume Activation for Windows A product key is usually required when uninstalling or reinstalling Windows 7 or Windows 8. Generally, if you bought a physical copy of Windows, the product key should be on a label or card inside the box that Windows came in. If Windows came preinstalled on your PC, the product key should appear on a sticker on your device.
To ensure your product key is genuine, see How to tell your software is genuine and How to tell your hardware is genuine. For info about how to tell if your copy of Windows is genuine Microsoft software, see the How to tell page. For more Windows 11 download info, see Download Windows For more Windows 10 download info, see Download Windows If you need installation media to install or reinstall Windows, see Create installation media for Windows to learn how to create your own installation media using either a USB flash drive or a DVD.
If you need more help with activation, see Activate Windows.
0コメント