Jump to content

tournamentdan

Members
  • Posts

    712
  • Joined

  • Last visited

Posts posted by tournamentdan

  1. For me, since you can't instance csg's I would only use csg's to block out a level for the concept phase of game creation. And then move on to regular mesh models that can be instanced or use geometry shaders to create or delete models to help cut back on the entity count.

  2. I used to use a flow graph that was pretty good with organizing the clutter. They called them portals. Just a different name for a call script function. Cleans up things pretty well. And as for the arguments. I would make it so that when you click on the argument node a dialog box would pop up for that one argument. In the dialog box you could set true or false, check variables or files, and call script. Maybe if you double clicked on the argument it would zoom you to the associated scripts with that argument.

    post-570-0-78698300-1430523197_thumb.jpg

  3. I dont have any problems with linux or linux users. (Except for the whole me against the world complex) Good things come out of diversity.

     

    But to try and compare different distros to different windows versions is streching it a lot. Windows is a heck of alot backwards compatable than most disros. Which makes it a nightmare to support when the flavor of the month distro changes a library and the others do not.

  4. Just a few reasons I grabbed of the world wide interweb of why I do not use linux.

     

     

     

     

     

    Poor interoperability between the kernel and user space applications. E.g. many kernel features get a decent userspace implementation years after introduction.! Linux security/permissions management is a bloody mess: PAM, SeLinux, Udev, HAL (replaced with udisk/upower/libudev), PolicyKit, ConsoleKit and usual Unix permissions (/etc/passwd, /etc/group) all have their separate incompatible permissions management systems spread all over the file system. Quite often people cannot use their digital devices unless they switch to a super user.No (easy to use) application level sandbox (like e.g. SandBoxie) - Fedora is working hard on it.(This needs to be thoroughly rechecked): observed general slowness: just compare start up times between e.g. OpenOffice and Microsoft Office. If you don't like this example, try launching OpenOffice in Windows and in Linux. In the latter case it will take more time to launch it.! CLI (command line interface) errors for user applications. All GUI applications should have a visible errors representation.! Very poor documentation and absence of good manuals/help system.Questionable services for Desktop installations (Fedora, Suse, Mandriva, Ubuntu) - not really important with the advent of systemd.! No unified widely used system for packages signing and verification (thus it becomes increasingly problematic to verify packages which are not included by your distro). No central body to issue certificates and to sign packages.(Not that serious considering that 4GB of RAM cost $20 nowadays) As of recently Linux distros and desktop environments have become a resource hog, e.g. in Ubuntu KDE 4.8.5 consumes whopping 1390MB of RAM.There are no antiviruses or similar software for Linux. Say, you want to install new software which is not included by your distro - currently there's no way to check if it's malicious or not.!! Linux distributions do not audit included packages which means a rogue evil application or a rogue evil patch can easily make into most distros thus endangering the end user.! A very bad backwards and forward compatibility! Due to unstable and constantly changing kernel APIs/ABIs Linux is a hell for companies which cannot push their drivers upstream into the kernel for various reasons like their closeness (NVIDIA, ATI, Broadcom, etc.), or inability to control development or co-develop (VirtualBox/Oracle, VMWare/Workstation, etc.), or licensing issues (4Front Technologies/OSS).Old applications rarely work in new Linux distros (glibc incompatibilities (double-free errors, memory corruption, etc.), missing libraries, wrong/new libraries versions). Abandoned Linux GUI software generally doesn't work in newer Linux distros. Most well written GUI applications for Windows 95 will work in Windows 7 (15 years of compatibility on binary level).New applications linked only against lib C will refuse to work in old distros. (Even though they are 100% source compatible with old distros).New libraries versions bugs, regressions and incompatibilitiesDistro upgrade can render your system unusable (kernel might not boot, some features may stop working).There's a myth that backwards compatibility is a non-issue in Linux because all the software has sources. However a lot of software just cannot be compiled on newer Linux distros due to 1) outdated, conflicting, no longer available libraries and dependencies 2) every GCC release becoming much stricter about C/C++ syntax 3) Users just won't bother compiling old software because they don't know how to 'compile', nor they should know how to do that.DE developers (KDE/Gnome) routinely cardinally change UI elements, configuration, behaviour, etc.Open Source developers usually don't care about applications behaviour beyond their own usagescenarios. I.e. coreutils developers for no good reasons have broken head/tails functionality which is used by the Loki installer.Quite often you cannot run new applications in LTS distros. Recent examples: GTK3 based software (there's no official way to use it in RHEL6), and Google Chrome (Google decided to abandon LTS ditros).stem will (re)boot successfully after GRUB (bootloader) orkernel updates - sometimes even minor kernel updates break the boot process. For instance Microsoft and Apple regularly update ntoskrnl.exe and mach_kernel respectively for security fixes, but it's unheard of that these updates ever compromised the boot process. GRUB updates have broken the boot process on the PCs around me for at least ten times. (Also see compatibility issues below!! LTS distros are unusable on the desktop because they poorly support or don't support new hardware, specifically GPUs (as well as Wi-Fi adapters, NICs, sound cards, hardware sensors, etc.). Oftentimes you cannot use new software in LTS distros (normally without miscellaneous hacks like backports, PPAs, chroots, etc.), due to outdated libraries. A recent example is Google Chrome on RHEL 6/CentOS 6.!! Linux developers have a tendency to a) suppress news of security holes B) not notify the public when said hole have been fixed c) miscategorize arbitrary code execution bugs as "possible denial of service" (thanks toGullible Jones for reminding me of this practice - I wanted to mention it aeons ago, but I kept forgetting about that).

     

    Here's a full quote by Torvalds himself: "So I personally consider security bugs to be just "normal bugs". I don't cover them up, but I also don't have any reason what-so-ever to think it's a good idea to track them and announce them as something special."

  5.  

    but as to not give Josh any more ammo to shoot down bugs I try to make do. ( Installed a non-standard desktop? well that's properly the cause of the bug *closed* )

     

    Which should be the case. Do you want Josh to waste hours if not days of his time working on a bug only to find the only reason there was a bug was because of a problem with a unsuported distro?

  6.  

    Also, windows users? Why are they so ... ugh? We might never know.

     

    Your right. It is so terrible being a windows user. I just hate it when I down load a application and it just works. No hacking required.

     

    Because you seem to be a big fan of linux you are over looking the real problem at hand. The fact that linux is in alpha stage development.

    Maybe linux should of attached some tags on their site saying that they were in alpha and practically nothing will work on it.

     

    As a linux user, shouldn't you be used to hacking programs to make them work?

    • Upvote 1
  7.  

    thanks for add something relevant to the thread.

     

     

     

    All you have been able to do is complain and bash in every thread you have started or added to. It is unhealthy to the community's progress and it is unhealthy to your progress as a developer. It might be time for you to take the outlook of the glass is half full instead of the glass is half empty mentality. I have had my disagreements and arguments with Josh but, I have never trolled every other thread to basically throw a tantrum. If your having this many problems with the product, move on. If your worried about the money. Write it off as a loss on your taxes.

     

    @everyone else Please excuse me for being truthful. Obviously the truth hurts.

  8. A material and a image based texture are two different things. If you uv unwrapped your model while in cycles render mode and used a image texture format that also works in Leadwerks, it should work.

     

    If you have a model that does not have a image based texture and you instead created materials using cycles nodes. It will not work. Unless you uv unwrap your model and bake a texture of your materials to a image based texture format that Leadwerks supports. Like .png.

     

    I have not been able to use leadwerks or the exporter for a while. Just due to being busy. Something may be wrong with the exporter. Try exporting to fbx and bring it into leadwerks that way.

  9. Can anyone explain how to get a texture out with cycles renderer?

     

    I can get the png files generating if I use Blenders old Render but when I try to use cycles the image file doesn't appear but the mat file does (with no image file reference). I don't know if it is because I don't know how to do it, or if you have to use the old render materials? Materials look fine with cycles in the viewport (as far as I can tell).

     

    Can anyone explain using export with cycles materials?

     

    Thanks,

     

    Michael

     

    Cycles renders light completely different from most other render engines. Especially real time engines. Because of this, the cycles materials can only be used in cycles. However, you can now bake textures in the cycles renderer.

  10.  

    This is what i do and what almost all 3D character artists do, where did i say this was wrong ?

     

     

     

    You deleted parts of your original post. Where you compared to a character from a game that had 150,000 polygons. In which you were implying that a character that has less polygons would be cheaper.

     

    If your going to edit your post. At least show that you edited it. And what correction and or changes you made.

  11. Yougroove, these characters that you posted at one time were much higher in poly count than 150,000. In order to get the detail these models have you have to first create a high poly model and generate all of your texture maps from your high poly to your low poly retopo version. So no matter what. In order to get good game models. You have to create a high detail model.

     

  12.  

     

    Development is no exact thing. You can make estimations, but some times reality is there with surprises.

    I don't see anything strange with that and of course you cant compare tasks like that.

     

     

    I am not the one that has compaired it. Josh has on multple occasions. He is just currently doing his propaganda thing he likes to do.

     

     

     

    I'm confident with what Josh says.

     

    I am actually kind of amazed that people that have been around here a long time have any confidence at all.

×
×
  • Create New...