Game Komputer

Computer Game


Personal Computer Game (juga dikenal sebagai permainan komputer atau game PC) adalah permainan yang dimainkan di komputer pribadi, bukan pada video game konsol atau mesin arcade. permainan komputer telah berevolusi dari grafis sederhana dan game dari judul awal seperti Spacewar, dengan berbagai judul yang lebih visual canggih.!

game PC yang dibuat oleh pengembang satu atau lebih permainan, biasanya bersama dengan spesialis lainnya (seperti seniman permainan) dan dipublikasikan baik secara mandiri atau melalui penerbit pihak ketiga. Mereka kemudian dapat didistribusikan pada media fisik seperti DVD dan CD, sebagai internet-download, mungkin dapat didistribusikan secara bebas, perangkat lunak, atau melalui jasa pengiriman online seperti Direct2Drive dan Uap. game PC sering membutuhkan hardware khusus di komputer pengguna untuk bermain, seperti generasi spesifik unit pemrosesan grafik atau koneksi internet untuk bermain online, meskipun persyaratan sistem ini bervariasi dari satu pertandingan ke pertandingan.


Pengertian Game Engine

Game Engine adalah system perangkat lunak yang dirancang untuk menciptakan dan pengembangan video game. Ada banyak mesin permainan yang dirancang untuk bekerja pada konsol permainan video dan sistem operasi desktop seperti Microsoft Windows, Linux, dan Mac OS X. fungsionalitas inti biasanya disediakan oleh mesin permainan mencakup mesin render ( “renderer”) untuk 2D atau 3D grafis, mesin fisika atau tabrakan (dan tanggapan tabrakan), suara, script, animasi, kecerdasan buatan, jaringan, streaming, manajemen memori, threading, dukungan lokalisasi, dan adegan grafik. Proses pengembangan permainan sering dihemat oleh sebagian besar menggunakan kembali mesin permainan yang sama untuk menciptakan permainan yang berbeda.


3 Game Engine

Delta3D adalah open-source game / mesin simulasi. Desain modular Delta3D's mengintegrasikan lain terkenal proyek Open Source seperti OpenSceneGraph, Open Dynamics Engine, Cal3D, dan OpenAL, mengintegrasikan mereka dalam sebuah API yang mudah digunakan. Daripada mengubur modul yang mendasari, Delta3D mengintegrasikan mereka bersama-sama, memungkinkan akses ke komponen penting yang mendasari. Ini memberikan tingkat-tinggi API sementara masih memungkinkan pengguna akhir fungsi, opsional tingkat rendah.


Ogre (Object-Oriented Graphics Rendering Engine) adalah sebuah adegan yang berorientasi fleksibel rendering engine 3D (sebagai lawan mesin permainan) ditulis dalam C + + dirancang untuk membuatnya lebih mudah dan intuitif bagi pengembang untuk menghasilkan aplikasi yang menggunakan grafis 3D hardware-accelerated. The abstrak perpustakaan kelas rincian menggunakan sistem perpustakaan yang mendasari seperti Direct3D dan OpenGL dan menyediakan sebuah antarmuka berbasis pada objek lain kelas dunia dan tingkat tinggi.


Irrlicht adalah sebuah mesin 3D open source yang ditulis dalam C + +. Ini adalah cross-platform, secara resmi berjalan pada Windows, Mac OS X, Linux dan Windows CE dan karena open port alam untuk sistem lain termasuk Xbox, PlayStation Portable, SymbianOS dan iPhone yang tersedia . Irrlicht dikenal karena ukurannya yang kecil dan kompatibilitas dengan perangkat keras baru dan tua sama, kurva belajar dangkal dan masyarakat yang ramah besar. Unofficial binding untuk banyak bahasa yang ada termasuk NET,. Jawa, perl, Ruby, Python, FreeBASIC, Lua, Delphi, C + + Builder dan bahkan Game Maker. Irrlicht pembangunan mulai tahun 2003 dengan hanya satu pengembang, Nikolaus Gebhardt. Hanya setelah rilis 1.0 dari Irrlicht pada tahun 2006 tim tumbuh untuk saat ini sepuluh anggota, pengembang kebanyakan dari mereka.


Jenis-jenis Game

Terdapat berbagai macam game, yaitu antara lain:


1. Fun Games


Fun games adalah permainan seperti : skate board, bilyard, catur, puzzle, tetris, golf, Windows Entertainment Pack Games dan semua permainan yang animasinya sedikit dan pembuatannya relatif mudah. Permainan semacam ini terlihat mudah dari segi grafiknya tetapi biasanya sulit dalam algoritma.


2. Arcade Games


Arcade games adalah semua permainan yang mudah dimengerti, menyenangkan dan grafiknya bagus walau biasanya sederhana. Pengertian mudah dimengerti dan menyenangkan dikarenakan permainan ini hanyalah berkisar pada hal-hal yang disenangi umum seperti pukul memukul, tembak menembak, tusuk menusuk, kejar mengejar dan semua yang mudah dan menyenangkan. Yang termasuk kedalam permainan jenis ini adalah Prince of Persia, Street Fighter, Golden Axe, Grand Prix, Robocop.


3. Strategic Games


Strategic games biasanya permainan strategi perang atau bisa juga permainan lain tetapi tetap saja memerlukan strategi untuk memenangkannya seperti startegi bisnis dan strategi politik.


4. Adventure Games


Adventure games terbagi atas tiga macam yaitu petualangan biasa (Multi Layered Adventur), Dungeon-Underworld Adventure (3D Adventure) dan Roll Playing Game Adventure. Biasanya algoritma untuk membuat game ini adalah sedang-sedang saja sampai sulit. Tapi grafik jenis permainan ini benar-benar sulit. Contoh beberapa permainan jenis ini adalah Space Quest IV, Labyrinth of Word, War II dan Diablo.



5. Simulation Games


Dari semua jenis permainan yang ada, masing-masing memiliki tingkat kesulitan dan kemudahannya, jika bukan algoritmanya maka akan mudah dalam hal animasinya, akan tetapi games simulasi bisa disebut sebagai jenis permainan yang paling sulit, baik algoritma pembuatannya maupun animasinya. Permainan jenis ini juga yang paling membuat pusing dibandingkan dengan permainan jenis lainnya. Algoritmanya sangat sulit sebab harus memperhitungkan semua kejadian dalam kondisi sebenarnya. Berbagai efek animasi yang dibuat tidak cukup bermodalkan ahli grafik dan algoritma saja, tetapi sedikitnya harus mengerti persoalan matematika, teknik dan fisika. Contoh permainan jenis ini adalah Stellar7, F-15 Strike Eagle, Flight Simulator 98, F-14 Tomcat, F-16 Falcon, Jet Fighter.

Creating Actor

Creating an Actor Tutorial, Part 1 – Overview and Concepts

So you’ve gotten the hang of STAGE. You’ve made some interesting worlds by placing and arranging static meshes. But, to finish your application, you need something more. After all, a few Static Meshes and a Sky Box doesn't make a game. You need trucks that move, game inventory objects, motion sensitive guards, or maybe even a rocket launcher. In short, you need the ability to make your own custom Actors! This tutorial teaches you all you need to know to make your own Actors. By following this 3 part tutorial, you will learn how to create a waving flag that you can use right in the editor. You will learn how to create a complex tessellated Actor, expose its size, speed, and height properties via an ActorProxy, and even make your flag accessible to the editor. This tutorial assumes you have already worked with STAGE. If not, please see the ‘Getting to Know the Editor’ tutorial. Note - this tutorial uses the word ‘Game’, ‘Simulation’, and ‘Training Application’ interchangeably. Part 1 – Actors and Proxies and Properties, Oh My! Before you can get started building that cool waving flag, there are a few things you need to know about how STAGE was built. The Delta3D Editor sits on top of a very dynamic architecture. In fact, STAGE was designed from the ground up to encourage customization. Since we could never anticipate what types of objects you’d need, we built an architecture that is completely generic and let you build your own game objects! Below are 3 key concepts you need to know. Actor – An Actor is any game object that has properties you want to work with in the Editor. An Actor can truly be anything you can imagine, from flying planes to pulsing lights to droppable guns to scaly green monsters. Actors are the specialized objects that help define your game or simulation. In part 2 of this tutorial, you will create your first Actor called ‘TesselationActor’. ActorProxy – An ActorProxy is a wrapper for an Actor. Proxies are simple, data oriented classes that have two main jobs. First, they provide a common, uniform class that the editor understands. Second, they know everything about the Actor they wrap, especially the properties. In part 2, you will create an ActorProxy for our flag called ‘TesselationActorProxy’. ActorProperties – ActorProperties are the properties of an Actor that show up in the PropertyEditor. Actor properties allow level designers to tweak and change how an object works. The more properties you expose, the more useful your object becomes. When you expose numerous important properties for your object, you allow level designers to take full advantage of your Actors without changing your code. In part 2, you will expose Actor properties for ‘Width’, ‘Height’, ‘Number of Steps’, ‘Period’, ‘Amplitude’, ‘Phase’, and ‘Texture’. By changing the values of these properties, you can change the size of your flag, make it move faster, give it more ripples, or even change the texture. The following picture shows some of the properties in the editor. Figure 1 – Tesselation Actor Properties Now that you know the basics about Actors and ActorProxies, there is one final step to address. Since the editor can’t magically find your ActorProxy classes, we need to tell it about our new object. What you need to do is put your ActorProxy into a library that the editor can find. Once you create this library you will be able to import it directly into the editor. Fortunately, this sounds harder than it is. In fact, as you’ll see in part 3 of this tutorial, it takes about 5 lines of actual code to do this. Plus, you will only need 1 library for ALL of your actors. OK. So, let’s sum up! To create any new Actor for STAGE, you will need to do the following steps: 1) Create your Actor – this is your specialty! 2) Create your Actor Proxy – simple data wrapper 3) Create an Actor Library - ONE time only 4) Add your Proxy to the Library – about 5 lines of code Now, you know enough about the basic architecture of STAGE to get started. Seriously, stop here! If you just want to know how to do something by example, it’s time to move on to Part 2 of the tutorial. However, if you’re the technical type and really want to know what’s going on, then you’ll be happy to know that we’ve got some great information ahead. As it happens, the Dynamic Actor Layer (DAL) was thoroughly designed before we ever wrote a line of code. Below is some of the detailed design material used in the construction of the DAL. 2. Dynamic Actor Layer (DAL) The Dynamic Actor Layer (DAL) provides a flexible, non-intrusive mechanism for generically exposing the properties of game actors in C++. The two primary components of this design are ActorProxies and ActorProperties. The proxy component is a wrapper for the underlying game actor and holds a collection of the individual properties. The property component exposes the data for a single game actor property via a getter and setter function object; similar to the Java bean specification. The proxy knows about its properties and the properties know how to access their data. These two components are used to generically expose all underlying data without ever modifying the original game actor code. Use of these data driven components, instead of the underlying game actor, promotes data encapsulation and code re-usability. Figure 2 - Overview The Dynamic Actor Layer and editor architecture overview is noted in Figure 2. The main purpose of the Editor is to allow for the manipulation of actors in a given scene. To support this, the DAL exposes a generic template allowing STAGE to work with actors as generic objects. The core of this concept is that each actor should be treated generically using only its name, id, and a collection of properties. A detailed description of the components of the DAL follows. 3. ActorProxy As mentioned above, Actors are any objects in your training application that have behavior and need to be manipulated in STAGE. Since the Actor classes can be anything, the editor must be protected from the internal workings of any one object. To make this happen each Actor must have a corresponding Proxy class that allows access to the internal properties. In essence, the ActorProxy is a conduit for actors to communicate their behavior to external applications or to ensure a consistent communications protocol among actors. Figure 3 shows a class diagram of the ActorProxy, Actor (DeltaDrawable), and ActorProperty. Figure 3 - ActorProxy Class Diagram The following is a description of the classes portrayed by the class diagram in Figure 3. DeltaDrawable This is the base class for all Actors in the system. The DeltaDrawable (dtCore::DeltaDrawable) is the base class of all Delta3D objects that are in the scene. In addition, it has tracking information like a tag name and a unique ID. MyTruck This is an example of a user built Actor class. Some of these will be built internally as part of the Editor, but many of these will be built by end developers and may be known only to their own particular application. Actor classes can be pretty much anything. They can have lighting, articulated parts, movement, AI, meshes, sounds, triggers, and anything else that you can do with Delta3D. They can draw themselves in anyway they sit fit within the Delta3D architecture. They can have many or zero properties, can have references to shared resources, and can be anything from a square billboard to a full blown landscape. ActorProxy This is the base class for all Actor Proxies. The Proxy’s main purpose is to expose the attributes of an Actor class as a series of properties. It has interface methods for getting and setting properties, getting its actor, and getting the actor’s type. Each actor must have a Proxy. The editor will periodically ask for properties by name or even change the value of the property using the setValue() method. MyTruckProxy This is an example of an actual user built Actor Proxy. In this case, the truck has a property called speed, so the Truck Proxy might expose a property called ‘speed’ to the editor. Then, Truck proxy could handle a request such as setProperty(“speed”, value) by calling myTruck.setSpeed (value). In this case, the TruckProxy knows the inner workings of the Truck class. It knows that speed is actually a floating point value. Many times the proxy will be a simple pass through for data. However, sometimes, the proxy will need to do manipulation of data. For instance, speed might have been represented by a vector of floats (xspeed, yspeed, and zspeed). In that case the proxy might have exposed 3 properties to the editor where there is only one underlying actual value. It might alternately have used a vec3. In either case, the proxy is responsible for knowing how to handle a setProperty(“xSpeed”, value) request and setting the internal speed value of the truck. 4. ActorProperty As stated above, the ActorProperty class provides a getter/setter mechanism for accessing properties of a class similar to the Java beans programming paradigm. Figure 4 depicts a more detailed view of the ActorProperty class including a subset of the property classes for a particular data type. Figure 4 - ActorProperty Class Diagram The getter and setter portions of the ActorProperty class are Functors (Function Objects) which reference a getter and a setter method on a given property class. Therefore, when an ActorProperty is created, it knows how to store and retrieve the data it represents. The ActorProperty class is also used to pass information about the properties of an Actor up to the Editor. It has a name, a display name, a description, and a type enumeration. The property class may also have a list of enumerations if the property is itself an enumeration. For example, a property of truck may be speed and it may support Slow, Medium, and Fast or a light may have a type property with settings of Directional, Strobe, Pulse, Omni, etc… 5. ActorLibraries Actor libraries are distributable components that serve to package groups of related actors and actor proxies. Actor libraries are dynamic libraries of C++ code that are loaded into the editor or other application. Figure 5 shows an overview class diagram of the Actor Library subsystem. A detailed description of each component is given below. Figure 5 - Dynamic Actor Layer Components LibraryManager This class is the main class in the Library Manager. It has a list of the libraries that are registered with the Manager as well as a list of which Actor Types each of the libraries can create. It is also the main vehicle for creating a new Actor Proxy. The Manager uses the singleton pattern. ActorPluginRegistry This is the base class that developers extend to build their own registry. The most important behavior in the registry is the ability to take an Actor Type and create a new Actor via the Actor Proxy. A registry is responsible for knowing which Actor types it can build. Since the Editor doesn’t know anything about object classes, the registry is responsible for figuring it out. The registry base class also exposes an object factory which provides most, if not all, of the ActorPluginRegistry’s Actor Type to Actor mapping capabilities. MyPluginRegistry This is a 3rd party implementation of the Registry. The developer will need to create and track which Actor Types it understands as well as be able to take an Actor Type and create a new Actor Proxy. This is likely a very simple class which creates and registers its actor types with the factory so that they are available at run-time. ActorType This is a simple data class that has information describing a particular Actor type. There will be one Actor Type for each unique Actor class like ‘BouncyTruck’ or ‘AgressiveSoldier’. For each actor class, there must be an Actor Type with a name, a category, and a description. The category is of particular note because it is used to visually sort classes in the editor. It follows a hierarchical dot notation (ex. “Vehicles.Trucks.NeatTrucks”) used to group related classes in some of the UI panels. It can also be used to search for objects. 6. Project / Map The project context is basically the “home” directory of your map. It is responsible for storing resources imported into the Editor; such as static meshes, particle systems, textures, and sounds. All of the imported actors in a map are stored and referenced relative to the project context of the map. The details of the Project and Map class interactions are beyond the scope of this tutorial; however Figure 6 shows a class diagram which depicts the basic interactions available to the Project and Map classes. Figure 6 - Project - Map Class Diagram

Animasi Mobil bergerak 3D

Gambar 1










Gambar 2









Gambar 3










Gambar 4









Gambar 5









Gambar 6










Gambar 7










Gambar 8










Gambar 9









Gambar 10









Gambar 11

Gambar 12










Gambar 13


TUTORIAL ANIMASI MOBIL

Di sini adalah mobil kita akan menghidupkan. Ini dapat yang sederhana seperti kotak untuk chassis, sebuah kotak untuk tubuh mobil, dan empat silinder untuk roda. Membangun mobil Anda dengan membuat kotak di viewport perspektif, seperti menghadap ke kiri, seperti ditunjukkan pada gambar di atas. Alasan untuk ini adalah bahwa ia akan menyelamatkan Anda kesulitan pada rotasi roda nanti. Melakukannya dengan cara ini menjamin roda anda akan berada dalam orientasi yang tepat untuk Y rotasi dengan persamaan. Setelah tubuh dan sasis mobil dibuat, membuat roda kiri depan dengan menggambar sebuah silinder dengan AutoGrid dihidupkan (AutoGrid memungkinkan Anda untuk menggambar 3d geometri pada geometri lain seperti badan mobil). Kemudian salin roda pertama untuk membuat roda belakang, lalu salin kedua roda kiri ke sisi kanan dari mobil.

Berikut adalah hirarki untuk mobil – nama benda-benda sehingga Anda dapat memberitahu apa yang dihubungkan dengan apa. Anda akan perlu menggunakan alat Pilih dan Link pada Standard Toolbar untuk menghubungkan bagian-bagian ini bersama-sama. Semuanya, yaitu, semua empat roda dan badan mobil, semuanya diasuh ke casis. Jika Anda belum pernah menggunakan Schematic Lihat antarmuka, mencobanya. Ini adalah cara terbaik untuk berurusan dengan link hirarkis.

Berikut ini adalah jalan bagi mobil kami – sebuah garis sederhana digambar dengan halus ditetapkan sebagai tipe default. Untuk realistis berubah, kebutuhan mobil kami jalan yang halus.

Pilih mobil chassis dan kemudian pergi ke menu dan pilih Animasi Path Kendala seperti yang ditunjukkan di atas. Kemudian klik pada jalur mobil. Ini akan menempatkan mobil chassis, dengan semua anak-anak, di jalan. The chassis akan pindah ke ketinggian jalan, sehingga Anda mungkin perlu memindahkan jalan yang lebih tinggi sehingga mobil tidak berada di bawah permukaan jalan Anda dengan asumsi Anda memiliki jalan.

Anda akan perlu untuk membuat beberapa penyesuaian dalam Motion Panel. Mengatur chassis untuk Ikuti Jalan di Path Pilihan. Juga, menyesuaikan Axis dan Flip sampai mobil bergerak ke arah yang benar di jalan. Perhatikan di sini bahwa kita menggunakan Timne Slider di bagian bawah Max antarmuka untuk melihat apa yang dilakukan mobil di berbagai bingkai dari animasi.

Ketika mobil berjalan di sepanjang jalan, apakah itu tampaknya memiliki kecepatan yang tepat? Mobilku tampaknya akan sedikit cepat, jadi aku Timne Konfigurasi mengklik tombol di bagian paling bawah layar – terlihat seperti sedikit stopwatch. Dalam kotak dialog Konfigurasi Timne, klik Re-skala Sisa (jangan kamu berharap kami bisa melakukan itu dalam kehidupan nyata?). Dalam skala Re Timne kotak dialog, klik End Time nilai dan mengubahnya ke 150 frame (atau apa pun yang Anda butuhkan). Dengan mengubah jumlah frame 100-150, dan kemudian menekan OK pada kedua kotak dialog, akhirnya aku membuat gerakan mobil di sekitar jalan 50% lebih lambat, hanya apa yang dibutuhkan.

Di sini kita di Top tampilan. Ini adalah perspektif yang baik untuk memutar badan mobil pada chassis untuk menciptakan realistis bersandar ketika mobil menabrak kurva. Di sini, di frame 29, kita mendorong mobil 5 derajat dan kemudian segera kembali lagi ke 0. Mengapa? Untuk membuat bingkai yang membuat mobil dari berputar sampai kita melewati langsung. Kemudian, ketika kita menambahkan ke mobil rotasi tubuh pada frame 35, itu tidak akan memulai aktual mobil rotasi tubuh sampai frame 29. Jadi kecil ini “dorongan” adalah penting. Perhatikan bahwa sudut alat Snap dihidupkan, sehingga kita bisa tepat dalam rotasi. Juga perhatikan di sini bahwa metode rotasi tubuh mobil diatur ke Lokal (lihat Standar Toolbar – ini penting). Jika Anda tidak menetapkan sistem koordinat Anda untuk Lokal, Anda akan berakhir dengan sebuah mobil yang berputar pada sumbu XYZ lain daripada sendiri, dan tidak akan beres.

Sekarang kita berada di jantung belokan kanan pertama kami. Mobil harus bersandar. Mobil memutar badan 15 derajat ke luar jalan. Pergi melalui proses ini, semua jalan di trek. Untuk saat berbelok, memutar badan mobil kiri, dan untuk bergantian kiri, memutar tubuh mobil kanan. Pastikan untuk menggunakan sebuah “dorongan” jika Anda ingin mengontrol ketika mobil berputar.

Selanjutnya kita akan membuat roda berbelok dengan menggunakan suatu persamaan, yang lebih mudah daripada memutar roda dengan tangan dengan Auto Key diaktifkan. Dalam rangka untuk melihat roda berbelok dengan benar, mereka membutuhkan bahan pada mereka. Kami akan menerapkan bahan kotak-kotak ini contoh sederhana. Pilih sebuah roda dan meluncurkan Material Editor dengan menekan tombol M. Pilih bahan gratis slot, dan nama Checkered materi Anda. Klik tombol di sebelah baur parameter, dan ketika anda melihat Material / Map Browser, klik-ganda pada Checker. Ini akan menghasilkan bahan checker untuk Anda.

Ketika menerapkan suatu bahan untuk suatu objek, pastikan objek yang dipilih, dan kemudian tekan tombol Apply Material to Selection tombol untuk menerapkan materi. Pastikan anda juga mengaktifkan tombol yang disebut “Tunjukkan Bahan dalam Viewport”. Perhatikan dalam gambar ini bahwa roda depan tampak cukup bagus, tetapi bahan roda belakang kurang tepat. Itu karena roda Anda memerlukan UVW Map. Screenshot berikutnya akan alamat ini.

Pilih roda belakang, dan dari daftar Modifiers, pilih UVW Map. Peta default jenis planar akan bekerja dengan baik di sini.

Sekarang untuk membuat roda gilirannya, pilih roda, pergi ke Motion Panel, dan klik di bawah Mentransformasi on Y Rotasi seperti yang ditunjukkan di atas. Kemudian klik “?” sebagaimana ditunjukkan. Ketika Tetapkan Controller muncul kotak dialog, pilih Float Expression. Ini seharusnya memunculkan Expression Controller, ditunjukkan di bawah ini.

Dalam Expression Controller di atas, masukkan rumus 360 * sin (S * 5) atau sesuatu yang mirip dengan sesuai dengan kebutuhan anda. Dalam persamaan ini, 360 adalah untuk derajat, dosa adalah untuk ekspresi trigonometri yang disebut sinus, yang kapitol S adalah untuk detik, dan angka 5 atau apa pun yang Anda gunakan untuk putaran tiap detik. Kemudian, tekan tombol Evaluasi pada kotak dialog Expression Controller. Jauhkan kotak terbuka dan menjalankan animasi untuk melihat seberapa baik kerjanya. Apakah anda memerlukan sedikit rotasi? Menurunkan angka 5 ke bawah untuk sesuatu seperti 2. Apakah roda salah jalan? Meletakkan – di depan 5 atau 2. Ketika gerakan satu roda terlihat bagus, salin persamaan dan ulangi proses ini untuk 3 roda yang lain.

Review Game

Sonic Unleashed

Sisa-sisa kejayaan konsol PlayStation2 tampaknya bisa diwakilkan oleh game terbaru keluaran SEGA ini, Sonic Unleashed (atau lebih dikenal Sonic World Adventure untuk versi Jepangnya) sebagai kisah lanjutan dari Sonic the Hedgehog. Dalam game ini, Sonic berusaha mengembalikan keadaan dunia menjadi normal setelah musuh bebuyutannya, Dr. Eggman, membuat dunia terpecah menjadi dua bagian besar menggunakan senjata baru ciptaannya beserta kekuatan Chaos Emerald yang dimilikinya.

Dampak dari dunia yang terbelah dua, Sonic Unleashed pun memiliki dua level yang berlainan, yakni saat siang hari dan malam hari. Suatu kejutan besar yang disisipkan oleh Sonic Team Japan sebagai developer game ini untuk membuat seakan dua game berbeda dibaur dalam satu kemasan apik. Kala siang hari, Sonic seperti biasa melaju kencang ke sana kemari, bahkan kini Sonic diberikan kemampuan untuk bisa mencapai kecepatan 300 mil/jam. Selebihnya mungkin agak berbau seri Sonic and the Secret Rings, dengan beberapa pengecualian, seperti penggunaan Hedgehog Engine untuk pertama kalinya yang memungkinkan tampilan grafis maksimal pada konsol PS3 dan Xbox 360. Meski, versi Wii dan PS2 juga menggunakan engine yang sama, tetap kualitasnya belum sebanding dengan kedua konsol yang disebut pertama. Begitu dengan PC.

Nah di malam hari, Sonic berubah menjadi sesuatu yang berbeda, dikarenakan pengaruh dari emerald yang dimiliki oleh Dr. Eggman maka setiap bulan muncul Sonic akan bertransformasi menjadi Werehog. Dalam bentuk ini, Sonic kehilangan kecepatan yang dia miliki, tapi sebagai gantinya Sonic menjadi super kuat. Jadi di sini kamu tidak lagi beradu cepat di tiap levelnya tapi justru mengandalkan kekuatan fisik untuk mengalahkan musuh-musuhmu. Jadi kesimpulannya, kalau di siang hari kamu bergantung pada kecepatan, maka saat malam hari intinya lebih ke eksplorasi dan unsur petualangan.

Kalau menilik tanggal rilis Sonic Unleashed yang agak beragam di beberapa tempat berdasarkan konsolnya, maka cukup diasumsikan saja game ini bakal rilis akhir tahun ini. Yang pasti game ini pertama kali akan muncul untuk konsol Wii dan PlayStation2 secara resmi mulai tanggal 18 November, kemudian versi Xbox 360 dan PS3 berbarengan rilis di Korea Selatan tanggal 20 November, baru yang paling terakhir di Jepang sekitar bulan Maret 2009.

Pengenalan 3ds Max

Sekilas Tentang 3D studio Max

• Saat ini komputer grafis telah menunjukan kemajuan yang pesat. Komputer grafis telah mampu menghasilkan suatu program yang dapat membuat gambar 3 dimensiyang mampu menyerupai aslinya.
• Software animasi tiga dimensi yang paling populer di Indonesia saat ini adalah 3D Studio Max yang dikeluarkan oleh AutoDesk Inc.

Keunggulan 3D Studio Max

• Mampu membuat objek Virtual secara 3 dimensi. dan bentuk dapat diubah sesuai keinginan.
• Mampu memberikan kesan material mendekati aslinya seperti material kayu, batuan, dan tanah.
• Mampu memberikan efek-efek khusus pada hasil akhir produk seperti efek cahaya dan bayangan, efek atmosfir seperti api, kabut dan lighting.
• Dapat menjalankan proses animasi, gambar dapat digerakan dan dirubah bentuknya serta diatur proses animasinya.

Tampilan ( User Interface ) 3D Studio Max

Pertama kali membuka 3D Studio Max, kita melihat layar dengan 4 kotak dan banyak tombol. kita dapat mengorganisasikan bagian pada tampilan ini sebagai berikut :

• ViewPort
• MenuBar
• Toolbar
• Command Panel
• Status Bar / Viewport Control

1. VIEWPORT
ViewPort adalah tampilan yang memperlihatkan object. Untuk dapat mengaktifkan salah satu ViewPort anda dapat mengkilik ViewPort yang diinginkan.

2. MENUBAR
Standart Bar dari Windows seperti File, Edit, View dan sebagainya

3. TOOLBAR
Tombol - tombol untuk memberi perintah secara cepat.


4. COMMAND PANEL
Tombol - tombol perintah, control dan parameter untuk membuat, memodifikasi dan menunjukan object.


5. STATUS BAR / VIEWPORT CONTROL
ViewPort Control atau Status Bar adalah untuk mengatur cara melihat pada viewport tertentu.

3ds max tutorial's polygon

Modeling

Polygon modeling

Main article: Polygon modeling

Polygon modeling is more common with game design than any other modeling technique as the very specific control over individual polygons allows for extreme optimization. Usually, the modeller begins with one of the 3ds max primitives, and using such tools as bevel and extrude, adds detail to and refines the model. Versions 4 and up feature the Editable Polygon object, which simplifies most mesh editing operations, and provides subdivision smoothing at customizable levels.

Version 7 introduced the edit poly modifier, which allows the use of the tools available in the editable polygon object to be used higher in the modifier stack (i.e., on top of other modifications).

NURBS or Nonuniform rational B-Spline

A more advanced alternative to polygons, it gives a smoothed out surface that eliminates the straight edges of a polygon model. NURBS is a mathematically exact representation of freeform surfaces like those used for car bodies and ship hulls, which can be exactly reproduced at any resolution whenever needed. With NURBS, a smooth sphere can be created with only one face.

The non-uniform property of NURBS brings up an important point. Because they are generated mathematically, NURBS objects have a parameter space in addition to the 3D geometric space in which they are displayed. Specifically, an array of values called knots specifies the extent of influence of each control vertex (CV) on the curve or surface. Knots are invisible in 3D space and you can't manipulate them directly, but occasionally their behavior affects the visible appearance of the NURBS object. This topic mentions those situations. Parameter space is one-dimensional for curves, which have only a single U dimension topologically, even though they exist geometrically in 3D space. Surfaces have two dimensions in parameter space, called U and V.

NURBS curves and surfaces have the important properties of not changing under the standard geometric affine transformations (Transforms), or under perspective projections. The CVs have local control of the object: moving a CV or changing its weight does not affect any part of the object beyond the neighboring CVs. (You can override this property by using the Soft Selection controls.) Also, the control lattice that connects CVs surrounds the surface. This is known as the convex hull property.

Surface tool/Editable patch object

Surface tool was originally a 3rd party plugin, but Kinetix acquired and included this feature since version 3.0. The surface tool is for creating common 3ds max's splines, and then applying a modifier called "surface." This modifier makes a surface from every 3 or 4 vertices in a grid. This is often seen as an alternative to 'Mesh' or 'Nurbs' modeling, as it enables a user to interpolate curved sections with straight geometry (for example a hole through a box shape). Although the surface tool is a useful way to generate parametrically accurate geometry, it lacks the 'surface properties' found in the similar Edit Patch modifier, which enables a user to maintain the original parametric geometry whilst being able to adjust "smoothing groups" between faces.

Predefined primitives

This is a basic method, in which one models something using only boxes, spheres, cones, cylinders and other predefined objects from the list of Predefined Standard Primitives or a list ofPredefined Extended Primitives. One may also apply boolean operations, including subtract, cut and connect. For example, one can make two spheres which will work as blobs that will connect with each other. These are called metaballs.

3ds max cube primitive

3ds max hedron primitive

Predefined Standard Primitives list

• Box — box produces a rectangular prism. An alternative variation of box is available — entitled cube — which proportionally constrains the length, width and height of the box.
• Cylinder — cylinder produces a cylinder.
• Torus — torus produces a torus — or a ring — with a circular cross section, sometimes referred to as a doughnut.
• Teapot — teapot produces the Utah teapot. Since the teapot is a parametric object, the user can choose which parts of the teapot to display after creation. These parts include the body, handle, spout and lid.
• Cone — cone produces round cones — either upright or inverted.
• Sphere — sphere produces a full sphere, hemisphere, or other portion of a sphere.
• Tube — tube can produce both round and prismatic tubes. The tube is similar to the cylinder with a hole in it.
• Pyramid — The pyramid primitive has a square or rectangular base and triangular sides.
• Plane — The plane object is a special type of flat polygon mesh that can be enlarged by any amount at render time. The user can specify factors to magnify the size or number of segments, or both. Modifiers such as displace can be added to a plane to simulate a hilly terrain.
• Geosphere — GeoSphere produces spheres and hemispheres based on three classes of regular polyhedrons.

Predefined Extended Primitives list

• Hedra — produces objects from several families of polyhedra.
• ChamferBox — creates a box with beveled or rounded edges.
• OilTank — creates a cylinder with convex caps.
• Spindle — creates a cylinder with conical caps.
• Gengon — creates an extruded, regular-sided polygon with optionally filleted side edges.
• Prism — Creates a three-sided prism with independently segmented sides.
• Torus knot — creates a complex or knotted torus by drawing 2D curves in the normal planes around a 3D curve. The 3D curve (called the Base Curve) can be either a circle or a torus knot. It can be converted from a torus knot object to a NURBS surface.
• ChamferCyl — creates a cylinder with beveled or rounded cap edges.
• Capsule — creates a cylinder with hemispherical caps.
• L-Ext — creates an extruded L-shaped object.
• C-Ext — creates an extruded C-shaped object.
• Hose — a flexible object, similar to a spring.

Rendering

Scanline rendering

The default rendering method in 3DS Max is scanline rendering. Several advanced features have been added to the scanliner over the years, such as global illumination, radiosity, andray tracing.

mental ray

mental ray is a production quality renderer integrated into the later versions of MAX, and is a powerful rendering tool, with bucket rendering, a technique that distributes the rendering burden between several computers efficiently. The 3ds Max version of mental ray also comes with a set of tools that allow a myriad of effects to be created with relative ease.

RenderMan

A third party connection tool to RenderMan pipelines is also available for those that need to integrate Max into Renderman render farms.

V-Ray

A third-party render engine plug-in for 3D Studio MAX. It is widely used, frequently substituting the standard and mental ray renderers which are included bundled with 3ds Max. V-Ray continues to be compatible with older versions of 3ds Max.

Brazil R/S

A third-party high-quality photorealistic rendering system created by SplutterFish, LLC capable of fast ray tracing and global illumination.

FinalRender

Another third-party raytracing render engine created by Cebas. Capable of simulating a wide range of real-world physical phenomena.

Indigo Renderer

A third-party photorealistic renderer with plugins for 3ds max.

Maxwell Render

A third-party photorealistic rendering system created by Next Limit Technologies providing robust materials and highly accurate unbiased rendering.

BIGrender 3.0

Another third-party rendering plugin. Capable of overcoming 3DS rendering memory limitations with rendering huge pictures.

]Features

MAXScript

MAXScript is a built-in scripting language, and can be used to automate repetitive tasks, combine existing functionality in new ways, develop new tools and user interfaces and much more. Plugin modules can be created entirely in MAXscript.

Character Studio

Character Studio was a plugin which since version 4 of Max is now integrated in 3D Studio Max, helping user to animate virtual characters. The system works using a character rig or "Biped" which is pre-made and allows the user to adjust the rig to fit the character they will be animating. Dedicated curve editors and motion capture data import tools make Character Studio ideal for character animation. "Biped" objects have other useful features that automated the production of walk cycles and movement paths, as well as secondary motion.

Scene Explorer

Scene Explorer, a tool that provides a hierarchical view of scene data and analysis, facilitates working with more complex scenes. Scene Explorer has the ability to sort, filter, and search a scene by any object type or property (including metadata). Added in 3ds Max 2008, it was the first component to facilitate .NET managed code in 3ds Max outside of MAXScript.

DWG Import

3ds Max supports both import and linking of DWG files. Improved memory management in 3ds Max 2008 enables larger scenes to be imported with multiple objects.

Texture Assignment/Editing

3ds Max offers operations for creative texture and planar mapping, including tiling, mirroring, decals, angle, rotate, blur, UV stretching, and relaxation; Remove Distortion; Preserve UV; and UV template image export. The texture workflow includes the ability to combine an unlimited number of textures, a material/map browser with support for drag-and-drop assignment, and hierarchies with thumbnails. UV workflow features include Pelt mapping, which defines custom seams and enables users to unfold UVs according to those seams; copy/paste materials, maps and colors; and access to quick mapping types (box, cylindrical, spherical).

General Keyframing

Two keying modes — set key and auto key — offer support for different keyframing workflows.

Fast and intuitive controls for keyframing — including cut, copy, and paste — let the user create animations with ease. Animation trajectories may be viewed and edited directly in the viewport.

Constrained Animation

Objects can be animated along curves with controls for alignment, banking, velocity, smoothness, and looping, and along surfaces with controls for alignment. Weight path-controlled animation between multiple curves, and animate the weight. Objects can be constrained to animate with other objects in many ways — including look at, orientation in different coordinate spaces, and linking at different points in time. These constraints also support animated weighting between more than one target.

All resulting constrained animation can be collapsed into standard keyframes for further editing.

Skinning

Either the Skin or Physique modifier may be used to achieve precise control of skeletal deformation, so the character deforms smoothly as joints are moved, even in the most challenging areas, such as shoulders. Skin deformation can be controlled using direct vertex weights, volumes of vertices defined by envelopes, or both.

Capabilities such as weight tables, paintable weights, and saving and loading of weights offer easy editing and proximity-based transfer between models, providing the accuracy and flexibility needed for complicated characters.

The rigid bind skinning option is useful for animating low-polygon models or as a diagnostic tool for regular skeleton animation.

Additional modifiers, such as Skin Wrap and Skin Morph, can be used to drive meshes with other meshes and make targeted weighting adjustments in tricky areas.

Skeletons and Inverse Kinematics (IK)

Characters can be rigged with custom skeletons using 3ds Max bones, IK solvers, and rigging tools.

All animation tools — including expressions, scripts, list controllers, and wiring — can be used along with a set of utilities specific to bones to build rigs of any structure and with custom controls, so animators see only the UI necessary to get their characters animated.

Four plug-in IK solvers ship with 3ds Max: history-independent solver, history-dependent solver, limb solver, and spline IK solver. These powerful solvers reduce the time it takes to create high-quality character animation. The history-independent solver delivers smooth blending between IK and FK animation and uses preferred angles to give animators more control over the positioning of affected bones.

The history-dependent solver can solve within joint limits and is used for machine-like animation. IK limb is a lightweight two-bone solver, optimized for real-time interactivity, ideal for working with a character arm or leg. Spline IK solver provides a flexible animation system with nodes that can be moved anywhere in 3D space. It allows for efficient animation of skeletal chains, such as a character’s spine or tail, and includes easy-to-use twist and roll controls.

Integrated Cloth Solver

In addition to reactor’s cloth modifier, 3ds Max software has an integrated cloth-simulation engine that enables the user to turn almost any 3D object into clothing, or build garments from scratch. Collision solving is fast and accurate even in complex simulations.(image.3ds max.jpg)

Local simulation lets artists drape cloth in real time to set up an initial clothing state before setting animation keys.

Cloth simulations can be used in conjunction with other 3ds Max dynamic forces, such as Space Warps. Multiple independent cloth systems can be animated with their own objects and forces. Cloth deformation data can be cached to the hard drive to allow for nondestructive iterations and to improve playback performance.

Integration with Autodesk Vault

Autodesk Vault plug-in, which ships with 3ds Max, consolidates users’ 3ds Max assets in a single location, enabling them to automatically track files and manage work in progress. Users can easily and safely share, find, and reuse 3ds Max (and design) assets in a large-scale production or visualization environment.

This tag from wikipedia.org