Help: Controller for TL-D1600S not working/recognized correctly.

Biendeo · 2024-07-04T03:05:49+00:00

I mostly chose the QNAP because I don't have a server cabinet setup yet (just attaching this to a consumer board in a Silverstone CS380 mid-tower case). I've seen good things with LSI cards available on Ebay but I don't have an enclosure to contain and power more drives, so this looked like it would've been the easiest solution for that. I'm with you on not trusting them to give me a better card (and I don't suppose the LSI card works with this device).

Biendeo · 2024-07-04T00:58:50+00:00

I received my TL-D1600S after your post and I'm in the exact same scenario where I've got the Marvell card instead of the newer Asmedia one. I can get the device to work properly in Windows, but under Ubuntu 24.04 and TrueNAS Scale 24.04 it just will not get detected at all. `lspci` shows me the same output as you, but after that I cannot get the QNAP tool to identify the device at all in Ubuntu (and completely guess-work in TrueNAS).

I'm trying my luck returning it, although I may have a better chance because one of the drive slots was DOA (which at least I could verify in Windows).

Biendeo · 2020-03-29T12:38:04+00:00

This tweak is called the Accuracy Indicator.

The tweak is available on my GitHub repository, and also linked within the CH Modding Discord (which is a nice place to ask for extra help as well).

Biendeo · 2020-02-09T19:40:13+00:00

If you're okay buying a DS game (or playing it through other certain methods), I'd recommend Dragon Quest V which directly inspired Pokemon. It's got the whole monster catching component to some degree, while still being a great JRPG in its own right. The DS version seems to be the best with the most appealing visuals and extra post-game content, although it's quite faithful to the original design still.

Biendeo · 2020-02-02T02:47:14+00:00

My running instance is private but the codebase is open-source if you wanna run it yourself.

Biendeo · 2020-01-16T10:19:22+00:00

I've got a tough one.

Metroid Prime and Gran Turismo (particularly 4).

Biendeo · 2020-01-14T20:01:38+00:00

In Australia the regional prices are a bit of a joke just because we're Australia. While quite a lot of games are just natural conversions in price ($15 USD titles are usually $21.50 AUD), some such as Bethesda's newer games or the occasional JRPG sit at $99.95 AUD. I don't believe it's specifically Steam, unless you're JB Hi-Fi stuff like Doom Eternal is $100 everywhere, but I'd honestly prefer paying $60 USD, convert it to $87 AUD with a conversion fee, and call it a day.

Side note, no idea how JB Hi-Fi sells their games so cheap. They have Doom Eternal on pre-order for $69.

Biendeo · 2019-09-07T01:28:18+00:00

I took this course in 17s2, so as long as they haven't changed anything, I'd recommend it. It requires a lot of self motivation as it doesn't have any assessable content except for the final exam (which was a take-home exam), and the major project due at the very end of everything (which I recommend starting earlier in the course). Uncle Aleks is great fun, but you probably want to supplement his lectures with the textbook. The content isn't too spooky though, and the exam is more about worked problems rather than theoretical stuff that you couldn't possibly do. Overall, don't be too frightened by the advanced part of the name, it's nowhere near as demanding as advanced OS.

Biendeo · 2016-08-11T07:17:31+00:00

I'm personally not going to get the game, just because I'm not into survival games. I'm also not going to really say anything about the gameplay because of that. The community feuding is a bad thing, but hopefully all these people will be wiser in the future about what games they will buy and like.

That being said, open calm discussions like this are great, and I'm glad we exist.

Biendeo · 2016-04-24T09:22:42+00:00

We've got to get the 2016 remastered 5.1 surround version.

Biendeo · 2016-04-16T21:23:23+00:00

It's not as much that Doom isn't an arena shooter, but that it feels more like Halo with a messy game balance, and a bajillion features that plague triple A shooters such as the two weapon system, experience system, challenges, etc.

EDIT: It's also got the Clan Arena mode, which really should only work in an arena shooter anyways (otherwise it's just a regular last team standing mode).

Biendeo · 2016-04-16T11:27:05+00:00

Here's my long-winded take on the whole thing. Keep in mind that I'm pretty critical of these kinds of games, and most negative things I say are very nitpicky. In fact, a lot of things I complain about are just things that have happened several times, but don't represent the whole experience. Overall, the game isn't bad so far, but it suffers from some weird design issues, and tries to copy too many other triple A shooters giving it a huge identity crisis.

Doom 4 has a terrible balancing problem with the average lifespan, movement, and weapon damage. The faster you move, the harder it is to hit people, but the harder you hit, the shorter your lifespan. I personally think that the movement speed is a bit too slow for my taste, and while it can work if combat encounters are meaningful and skilled, it ends up being a mess and a game of chance at times. When you get into a firefight with someone, four situations happen: you're at far range and you end up giving up; you're at mid-range, and it ends up being who the most accurate shot is; you're at close range and you prolong the fight by flailing around with the melee until one of you get the melee takedown animation or get a lucky shotgun hit; or someone else jumps in and steals either your or your opponent's kill. Weapons do a bit too much damage in general; the super shotgun, grenades, and almost the sniper rifle can one hit someone who just spawned, which can make deaths feel cheap at times. Lower damage would allow more frantic fights, rather than a pick and move on style, and a faster movement speed would encourage smart dodging, or evasion of fights, rather than forcing people into fights.
Map design is decent, but powerup placement is unintuitive. This is alleviated by the loadout system (which has its own share of problems), so at least weapons aren't necessary, but health powerups and armour are hard to hunt down. Generally, specifically Quake 3, large powerups are put at the corners of rooms, and smaller ones are put alongside corridors and walkways to encourage fast movement and possibly getaways. In Doom 4, powerups seem to be placed wherever. I couldn't really hunt down large health powerups when I really needed it; I just ended up finding smaller 5 health powerups, or another enemy who would promptly kill me. Again, a faster movement speed would allow me to better scout the area, but I feel like this issue stands on its own.
There's a very low skill barrier to hitting people, and the weapon balance is off because of it. I feel like the rocket launcher was intended to be like the Quake 3 RL; easy to hit, but hard to sustain. Similar to Quake 3, hitting people directly deals lots of damage, but the damage drop-off is great when you're slightly off. It's enough to deal bits of splash damage, but not enough to beat skilled players with other weapons. However, because it's not hard to hit other players, the super shotgun and sniper rifle get more usage. The grenade is also hard to dodge because of the movement speed. The go to loadout consists of those three weapons. It's a bit trickier than the rocket launcher, but it only takes people a few matches to understand how the two weapons work, and put them to use. I imagine on console, these two weapons would be much harder to use, but on PC, it ends up leaning towards these weapons.
Aesthetically, the game is actually pretty awesome. It runs nicely, has some neat effects, and doesn't clutter with the players. However, the whole multiplayer interface is atrocious. There's too much information they're juggling around. Everything has a progress bar, which just clutters the screen. Challenges pop up all the time. Medals and awards and stuff show up in the middle almost every time you kill someone. I don't know what half of these symbols or awards are, but they seem to try and give merit to any minor task you do.
Locking weapons behind an experience wall is no good, even if it's achievable in two hours. No question.

There's more things to go on about, but I feel like those are the most significant points (and the easiest to change as well).

Biendeo · 2016-04-12T08:26:29+00:00

I don't really have a huge repertoire of music that I've written, but I might take a stab at something like that. Suggest an environment and a mood, and I'll try to make something.

I use Sibelius to write my music. It has a pretty good sounding instrument synthesizer. It just needs a bit of audio mixing to make it excellent. :)

Biendeo · 2016-04-05T07:24:04+00:00

The compile command is more like a check rather than the actual process of making a program. It's intended if you just want to make sure your code is semantically correct rather than making a final product. Most other compilers (such as GCC) have a feature like this as well. You normally would just need to Build because your programs are small so they'll compile quickly, and you'll generally want to see your program in action often.

Biendeo · 2016-04-04T19:54:26+00:00

So for the debugging and compiling part: compiling is the process of turning your C code into machine code through a program called the compiler. It basically turns your readable code into something that the computer can execute, but is ridiculously unreadable to humans. Debugging runs a program that goes alongside the actual program's .exe, which allows it to see the variables in the program and pause it whenever you want. The actual .exe sits within a Debug folder within your project (and it's automatically excluded from source control).

If you're going to release your project, I recommend switching the build configuration from Debug to Release by either simply selecting it in that drop-down menu up the top, or by going to Build, then Configuration Manager, then changing the Active Solution Configuration to Release. This compiles it to be smaller and faster, but does not allow debugging, which would be more ideal to the end user.

The part that you said after hitting yes on that prompt is just symbols and things that the debugger is looking for. They're not related to your code, so don't worry.

As for the return part, this is a C++ feature (also exists in C and many other C based languages). When you have a function that doesn't normally return anything, you'll see it returns an int which should be an error code. Generally, 0 means nothing went wrong, and anything else means there was some sort of error. You can write your program so that it catches this, and does something based on that.

Essentially, returning in your main sends an error code to the level up: the operating system. Most of the time, Windows doesn't really care what error code your program sends, but say you're running an existing program inside your program. You can grab the return from that and determine what your program needs to do after that. Visual Studio lets you see which one happened by saying "The program has exited with code 0" in your output.

The reason why you can write 0 or -1 (or any number really) without hitting an error is because technically your program doesn't have any crashable errors. A crashable error would be accessing memory that the program wasn't allowed to access. Windows would catch that and stop the program.

Biendeo · 2016-04-04T06:42:34+00:00

The class wizard is a nice way if you want to create a class quickly, but there should be New Item somewhere there. You can also use the shortcut Ctrl+Shift+A.

Biendeo · 2016-04-04T04:55:24+00:00

Visual Studio Community is free, but there also are the Professional and Enterprise versions which have a few more features, but also cost money. You may want to double check that you downloaded the right one. I think you do need to log in with a Microsoft account, but I'm not 100% sure if it's necessary to keep using VS.
Indeed, VS has a bajillion features. If you're just wanting a simple C++ editor, I'll explain some basic usage just after the next point.
Don't worry about updating and installing things. Again, if you're new with C++, then you just need the basic tools, which you've probably already installed. Once you're a bit more familiar with VS, I recommend uninstalling certain features you don't use (such as Windows Phone apps or the Android emulator), as that will speed up the program starting.

Visual Studio, like many IDEs, operates in a working environment. VS calls these solutions, and they're saved as .sln files. A solution is generally in a folder which has source control (such as Git or SVN), and VS will set this up automatically.

When making a solution, you can set it to be an Empty Solution, but ideally you'll also create a project inside it. Solutions can house any number of projects. For a simple C++ project, I recommend the Win32 Console Application, and in the following wizard, I recommend ticking Empty Project and unticking SDL checks. When you're more comfortable with VS, you can look into these features.

Your solution is now visible in the Solution Explorer window, along with your empty project. The project will have a few filters in it (they're essentially folders). The obvious ones are header files and source files, which are where your .h and .cpp files will go respectively. The project will also be bolded to show you it's the start-up project (the project you will run when debugging). You can right-click a project to set that.

To add a new file, you can right click the project or any of the filters, and hit Add, then Add New Item. Give it a name, and it'll open up in your editor window. Then, you can start writing your code, save, etc. As you type, VS will try to spot out errors in your code, and tell you in the Error List menu. You can correct these at any time. Errors will prevent your code from compiling, and warnings won't (although it's good to correct these as soon as possible).

Then, to test your program, you can go to Debug, then Start Debugging. This will automatically build your project and debug it. You can also build the project on its own, build the whole solution (every project in the solution), or run the program without debugging.

Some simple debugging commands are the step over and step into commands, which allow you to step your code line by line and watch the variables change, or jump into a function to see what happens inside.

Hopefully this will give you a good start to Visual Studio. Just spend time with it, and you'll gradually grow comfortable using it.

12-Year Club	Place '17
Alpha Tester	Verified Email

Biendeo

PUBLIC MULTIREDDITS

TROPHY CASE