NO20111454A1 - A system for developing computer games on the Internet - Google Patents

Abstract

The invention comprises a system consisting of a web-based system ("Web OS") in a web browser or web browser plug-in, a desktop application, a client program / window and / or a web browser plug-in for remote play and / or local gaming, and an accessible OS for bind and sighted users.

Description

INTRODUCTION

The invention generally relates to information technology systems, and more specifically to a system for developing high-quality computer games on the Internet.

BACKGROUND

There is a good deal of prior art within the technical area of the invention. Some examples of this are:

o Systems for web-based operating systems on the Internet: YouOS and EyeOS.

o Systems for remote gaming experiences on the Internet: OnLive and GaiKai.

o System for "hosted game development environment" (US patent application number US2004/0106452 Al).

There are many systems for developing computer games. Game engines are used to provide the very core functionality of computer games (e.g. Crytek CryEngine and Unreal Engine). There is one

wide range of tools for creating 3D content in computer games (eg Blender, Autodesk 3D Studio Max, Autodesk Maya, Autodesk Softimage, Poser, DAZ Studio, Bryce and MojoWorld). Furthermore, a wide range of tools are offered for creating music, sound effects, physics effects, character animation, lighting, etc. There are mainly two graphics libraries per today for the visualization of 3D graphics in real time in computer games (ie DirectX and OpenGL). nVidia is experimenting with a new type of real-time ray-tracing visualization called nVidia OptiX. Ray-tracing is an old and well-known method for visualizing 3D graphics, but as ray-tracing is much more processor-intensive than raster-based techniques (which DirectX and OpenGL use), ray-tracing is little used today for real-time computer game 3D graphics visualization. We believe that ray-tracing will become the main method for real-time computer game 3D graphics visualization in the future, because the processing power in computers is getting better and better. There are web-based operating systems (e.g. YouOS and EyeOS) for ordinary business needs (e.g. e-mail, chat/instant messaging, word processing, spreadsheets, file storage, calculator, and the like). There are no web-based operating systems, as far as we know, for game development. There are also a number of services that offer remote playing of computer games over the Internet (eg OnLive and GaiKai). There are also some tools available for students and hobbyist game developers (eg Microsoft XNA).

Existing technology is difficult to use for students and small/medium-sized game development projects. Existing technology is also difficult to use to involve the end users in a user-driven collaborative game development process. Video game resources (eg 3D models, code and media) are often large (often several gigabytes). This becomes a central problem when the developers are geographically dispersed. Installing and upgrading software tools and hardware can also become an obstacle. Digital rights protection is also an issue when sharing resources.

SUMMARY OF THE INVENTION

It is an aim of the present invention to provide a system for solving the above-mentioned problems in prior art.

The features defined in the independent requirements attached characterize this system.

The present invention provides a system consisting of a web-based system ("Web OS") in a web browser or web browser plug-in; a desktop application; a client program/window and/or a web browser plug-in for remote gaming and/or local gaming; and an Accessible OS for blind and visually impaired users.

BRIEF DESCRIPTION OF THE FIGURES

The invention will further be described in detail with reference to the figures, where:

FIG. 1 shows the system architecture of the system.

FIG. 2 shows a user interface for the Web OS in a web browser or web browser plug-in.

FIG. 3 shows a user interface for the Mesh Viewer in the Web OS.

FIG. 4 shows a user interface for the Mesh Viewer in the Web OS.

FIG. 5 shows a user interface for the course catalog in the Web OS.

FIG. 6 shows a user interface for the course display in the Web OS.

FIG. 7 shows a user interface for the remote play client.

FIG. 8 shows a user interface for the remote play client.

FIG. 9 shows a user interface for the desktop application.

FIG. 10 shows the contents of an example source code file for a single computer game.

DETAILED DESCRIPTION

The idea of the invention is mainly to provide a "web operating system" (Web OS), which executes inside a web browser, web browser plug-in or another application with web browsing support, where the Web OS contains web applications for game development . One of the advantages of such a solution is that game development tools, 3D modeling tools, other tools, game engines, 3D models and other media can be stored/installed on a set of server systems, so that the user does not necessarily have to download (and install) all of this in order to develop a computer game, participate in developing a computer game, view/modify 3D models/media, play one or more computer games/computer game fragments, etc. This applies especially in cases where one or more students, designers and/or developers will only participate in a specific task in the computer game and/or for a shorter period of time. This also applies in particular in cases where it is desirable to involve the end users of a computer game in the actual development and/or expansion of a computer game. It will be cumbersome and problematic in such projects to have to download and install many tools, game engines, 3D models and other things just to carry out a short and small project. Server-side storage also improves handling of digital rights protection. The invention can of course be used to create ordinary computer games (ie a "stand-alone" computer program that can be downloaded and installed using an installer). However, we would also like to highlight another important application area: We believe that web content, as we know it today, is facing a paradigm shift. We believe that before too long we will start to see web pages that look and work like computer games do today. Raster-based graphics (e.g. DirectX 11 and/or OpenGL 4, which is the latest version as of today) will be used for visualization of 3D graphic content. Further into the future (possibly in 10 years) ray-tracing techniques will be used. The traditional text-based content will probably persist, but computer game experiences will be used to a greater extent. We believe web browser plug-ins will be used for such computer game content. We also offer a web browser plug-in and/or a desktop application to make such computer game experiences available on the web. Web browsers and "media centers" will probably also be expanded eventually to support this type of computer game experience. One of the ideas with the invention is to make it much easier to develop and design such web-based computer game experiences.

The invention contains a number of tools. "Mesh Viewer" is a tool that makes it possible to display 3D models in the Web OS and elsewhere. The user can, with this tool, open 3D models, "interact" with the 3D model (e.g. move, rotate, edit, play animations, change materials/shaders/colors/lights/camera/visualizations/shadows/environment, with further), and optionally save changes (or share them with others). The course catalog contains a wide range of courses that offer training in important areas related to game development (e.g. DirectX/Shader/game engine programming, and 3D modeling and design for Blender/Bryce), as well as game projects. The library contains a wide range of articles related to game development. We plan for game developers to post articles and references in the library. The invention also contains a code editor and a larger integrated development environment (IDE). It mainly uses the same type of interface as in other IDEs (eg Microsoft Visual Studio). A smaller code editor is used for easier editing of individual files. The invention also has many of the same tools as in other Web OS (e.g. instant messaging, voice, file explorer, file sharing, calendar, project management, word processing, contact list, profile, rss feeds, e-mail, workgroups, spreadsheets, calculator, presentation tools, etc.). We will also be able to expand the invention with support for advanced 3D modelling, animations, etc., in the future.

The invention includes a variety of software applications that are installed on the user's computer. The desktop application is a computer program that can be downloaded and installed on the user's computer. The desktop application has local storage of computer games/game resources, synchronization of files between system servers and end-user computers, remote gaming, instant messaging, configuration of in-game skins, etc. A remote play client and a web browser plug-in can also be installed on the user's computer. The web browser plug-in can be used to display high-quality computer game experiences in a web browser (ie larger computer games). Transferring resource files (3D models, textures, etc.) is an obvious problem. It is also clear that synchronization is a problem. One of the main ideas of the invention is to solve the problems with the transfer and synchronization of resource files by offering users a "desktop application" that executes on the user's machine as a service (ie in the "system tray" or service). When the user is on a (ordinary HTML) website that offers web browser-based computer game experiences, the user can e.g. choose to try the computer game with remote play, or choose to download the computer game to your own computer. If the user chooses to download to their own computer, the web browser plug-in will communicate this to the desktop application, which starts the download process (provided that the user has installed the web browser plug-in component and the desktop application). The desktop application will first retrieve an XML list of all the files to be downloaded and/or synchronized, after which the files will be downloaded. The amount of bandwidth to be used and similar can be configured. The files can of course be compressed (e.g. zip/rar and the like) and encrypted (e.g. RSA and the like). With this solution, the user can close the web browser or navigate to other pages while the computer game content is being downloaded. When the desktop application has finished downloading the files, the user will be notified (e.g. with a pop-up window near the system tray). The user can then start the computer game by returning to the website of the computer game, or open the desktop application from the system tray (or the start menu etc.) and start the computer game from there. The desktop application will contain a list of all user-registered computer game websites, where the user can start local computer games in the web browser (or in a local client), start remote playing of the computer games, as well as manage the computer games (delete, allocate, synchronize, compress, backup, etc.) . The desktop application can also include a number of additional functionalities, such as e.g. "instant messaging, remote desktops, FTP tools, cache, licenses, heads-up display tools," and so on. Remote play will typically take place in the web browser plug-in, in a separate window in the desktop application, or in a separate remote play application.

Another problem that the desktop application helps to solve is in relation to game development and sharing files. The desktop application can be configured so that it synchronizes the contents of one or more file folders on the end-user computer with file folders on the system servers. The user can also "check files in and out" (eg as in Microsoft Visual SourceSafe and/or SVN), so that they can be edited simultaneously with other users. The Web OS will also show an overview of which files have been checked in and out, version history, logs, etc. It is possible to use source code version control systems (eg Microsoft Visual SourceSafe and SVN). The desktop application will synchronize large files (eg 3D models and textures) in an efficient way, so that only changes to the files are transferred over the network. There are a wide range of techniques for creating, representing and applying such differences in different types of files and content. The invention is not limited to a specific difference method. Synchronizing large files, in this way, makes it much easier for the user to work locally on a set of files that are mainly stored on the system servers.

A problem with existing remote playback techniques (eg OnLive) is that they are limited by the Internet connection (ie transfer speed, "latency," quality of service, etc). Many users of computer games often use high screen resolution (often high definition), multiple screens, and more recently also stereoscopic viewing (eg with 3D glasses with "active snutters" or "polarized" techniques). Real-time transmission of such audiovisual streams over the Internet requires very high bandwidth. Computer games also often have an action that requires a quick reaction from the user. Latency in the network connection will delay this experience, so that many computer games (e.g. Trackmania) will not be usable with remote play. In addition, there are other problems, such as packet loss and the like. Our techniques aim to take advantage of a combination (or a "hybrid solution") of offering computer game website experiences in the web browser with a self-developed web browser plug-in, and offering computer game website experiences in (and outside ) the web browser with remote playback in (and outside) the web browser plug-in. our solution involves using our web browser plug-in, desktop application, and remote gaming client on the end user's computer, as well as having computer games stored and executed on servers. The main idea of our solution is that users with an ordinary Internet connection (by today's standards) can try the computer game with remote play (to see if it is something they are interested in spending more time on). If they are interested, they can also choose to download the computer game to their own computer for better quality. The solution can also easily be used to create "hybrid games" where parts of the computer game are made with remote play (e.g. "game environment, windows, portals, displays," etc.) and other parts are made with locally stored content.

FIG. 1 illustrates the system architecture of the system. The end user's computer (1000) is the computer that the end user uses. "End users" are developers, designers, students,

and/or other users. Naturally, there are many end-user machines that use the system. The end user machine (or "user's machine", or "client") communicates with one or more system servers (1200) via an Internet connection (1100) or other network. We have the possibility of several software and hardware applications installed and/or executing on the user's machine. One or more computer games (1001) may execute on the user's machine. They may contain one or more "in-game heads-up displays" (HUD) and/or stub components

(1002). A HUD is typically a 2D display that appears in a computer game above the other graphics to offer functionalities, such as instant messaging, voice, recording gameplay video, sharing the game desktop (video/audio) with other users over the Internet, controlling computer games, and so on. A HUD can also be implemented as part of the 3D graphics. A stub component is typically used to manage/control a computer game over a network, such as start recording video, inject input data (e.g. mouse, keyboard and gamepad), monitoring, logging, debugging, etc. HUD and stub components can e.g. implemented directly in the computer game, or they can be injected by overriding DLLs and/or runtime "DLL insertion". Corresponding ways in different operating systems can be used. The invention includes "computer games" both in a context where the computer game is "debugged"/developed/tested and/or is finally distributed as a final product.

A web browser (1003) on the user's machine can be used to access the web pages available on one or more system servers via the "portal" (ie one or more "web sites")

(1201). The desktop application (1004) is used to download/manage/manage/edit/etc. computer games and game resources, synchronization of files between the user's machine and the servers, etc. The remote play application (1005) is used to play computer games remotely. The user can connect to a computer game on a server (1206) or a client (1001). Video/audio is sent from the computer game to the remote gaming application (or remote gaming client) and user input (eg mouse, keyboard and gamepad data) is sent from the remote gaming application to the computer game. It is also possible that the desktop application implements remote play. We can also offer a web browser-based solution, where a web browser and/or web browser plug-in shows remote and local playback of computer games from servers or clients. One can e.g. display JPEG and/or PNG images in the HTML/JavaScript code of a web page containing an image sequence of such a remote or local playback session. The new HTML5 elements can further optimize by displaying images, video and sound. A web browser plug-in, such as Adobe Flash, Microsoft Silverlight, Apple QuickTime, or our proprietary web browser plug-in can also be used to display and/or execute remote play or local play sessions. It is also possible to combine remote and local gaming (hybrid gaming), so that parts of the gaming experience are performed in another location (local or remote) and are displayed as images/video/sound in the local gaming session, and where the local gaming session also displays its own 3D graphics and sound mixed together with this. The server systems (or servers) (1200) contain one or more services/applications

(1201) to (1207). There will typically be different types of servers, e.g. web servers, live servers, mesh servers, database servers, computer game servers, etc. These servers will typically execute on different physical computers, but they can also execute on the same machine. Live server (1202) is a computer program that allows the user to log in via one or more of the computer programs on the user's machine. Live server manages instant messaging, voice, live desktop (video/audio) sharing and the like. The live servers will typically be implemented as different computer programs for different tasks (eg login/chat and voice/video sharing), which typically execute on different servers. Mesh server (1203) is also a computer program that allows the user to connect via one or more of the computer programs on the user's machine. Mesh server contains functionality to render 3D models (to screen and/or to a buffer). Mesh server creates image and/or video representations of this rendering and makes it available for use in the portal or for the computer programs on the user's machine. Mesh server can also "stream" images/video/sound. The computer programs on the user's machine capture user input (eg mouse, keyboard and gamepad operations) and/or other operations and send these over the network to the Mesh server. Mesh server uses these user inputs to control the "transformation" (eg rotate, scale, move camera/model, change lighting, change materials, change model, play animations, etc.). Web services (1204) are a number of different services that are needed (eg Ajax APIs and the like). Storage (1205) is different types of storage. Computer games (1206) and HUD/Stub (1207) are similar to (1001) and (1002).

FIG. 2 shows the user interface of the "web operating system" (Web OS). The user interface

is displayed inside a web browser (e.g. Microsoft Internet Explorer, Firefox, Google Chome, or others) (2000) or another application that has web browsing support. The user interface is similar to the user interface found in other Web OS (e.g. YouOS and EyeOS). Icons

(2001) and (2002) on the desktop in the Web OS can e.g. clicked (or double-clicked to

launch web applications. The web windows (2008) and (2009) contain the user interface of the web applications. The Start button (2003) can e.g. is clicked to display a menu consisting of links/icons to launch web applications. The user can e.g. click on one of these to launch the web application. "Taskbar representations" (2004) and (2005) of the web windows are displayed on the "taskbar", in a similar way as in other Web OS. The Web OS may also have some areas on/near the taskbar that show "system tray" (2006) and a clock (2007). System tray is typically used to represent web applications that execute, but where you don't always want to have a web window open (in a similar way as in other operating systems). Web OS may also have other layouts that are common and popular in other operating systems (it will probably change over time as new popular designs/layouts arrive). Apple Macintosh OS X has e.g. a different layout/design, where a menu appears at the top, and with a "launchbar" at the bottom of the screen. The invention encompasses all such layouts and designs that are, or will become, common for Web OS (as long as it is perceived by users as a web operating system). The Web OS will typically contain many well-known web applications, such as e.g. "file explorer, web browser, instant messaging, voice (i.e. voice over IP), web camera sharing, profile, contact/friend management," word processing, spreadsheets, project planner, etc. (ref. e.g. YouOS, EyeOS and other Web OS). The Web OS will also contain web applications that are important for game development and design, such as e.g. a larger "integrated development environment" (IDE), a smaller code editor, project management tools, a list of many projects, a home page for each individual project, bug tracking (e.g. similar to Bugzilla), 3D tools (e.g. edit 3D models , generate various types of 3D models, animation of

characters and models, etc.), "Shader editors", music/sound tools, effects tools, physics editor (e.g. the editors/SDK possibilities in nVidia PhysX), ray-tracing setup, level editors for computer game design , mods for computer games, and more. The Web OS will also have web applications for courses and training, such as a course catalogue, course display, library, etc. The Web OS will have one or more file structures ("folders and files") that users can access to upload/download various files. The desktop application (on the user's machine) can be used to synchronize these file structures with a file structure on their own machine, so that it becomes easier to work with the files. The Web OS will also offer version control systems for source code (e.g.

Microsoft Visual SourceSafe, SVN, CVS, and/or others). The Web OS can display many remote desktop views (eg remote gaming, desktop sharing, remote desktop and virtualized OS). The Web OS will have support for digital rights management (DRM) so that the content is encrypted and licenses will be needed for access (eg similar to Microsoft Windows Media Rights Management). Most of these techniques are known to experienced professionals and therefore we will not go into detail. The invention also includes a system called "Accessible OS" (the name can be changed) which makes it possible for blind and partially sighted people to use the system. Accessible OS is mainly audio-based, but can also have a visual hierarchical menu system with large, clear text. We believe that the design and production of music and sound effects is a field that can be opened up to the blind and partially sighted. Accessible OS offers audio-based (ie mainly audio info to the user) tools for creating music and sound effects. Common input devices can be used (e.g. keyboard, mouse/trackpad, gamepad, braille devices, etc.). Accessible OS may also have techniques that enable blind and partially sighted people to experience 3D models and worlds using special input devices (e.g. Sensable Phantom devices and the like).

FIG. 3 and FIG. 4 shows alternative user interfaces for "Mesh Viewer" (3000) and (4000). Mesh Viewer is a web application inside the Web OS that is used to display 3D models to the user. The "(3D Model View)" area displays images or video of the 3D model. User can drag and drop with mouse to rotate/f listen/m. v. camera. User can also use the keyboard to navigate. The images/video are generated in real time by the Mesh server (1203). Mesh Viewer can be easily implemented in HTML 5/4.01 and JavaScript. Mesh Viewer can connect to the Mesh server over the Internet using sockets/pipes/e.l. Mesh server can then open a 3D model, as specified by the user via Mesh Viewer, and render this. The rendering can be saved as a JPEG or PNG image (or other image formats, or video formats) and save the image so that it can be accessed via HTTP/e.l. by Mesh Viewer (or stream it to Mesh Viewer via UDP or similar). The Mesh Viewer can then display the generated image in the "(3D Model View)" area. The Mesh Viewer can forward user input and operations to the Mesh server, which updates the rendering, and generates a new image or video frame that is made available to, or

is sent, to the Mesh Viewer, where this is displayed. In this way, one can then show interactive 3D models to the users. FIG. 3 is a simple solution where you only have a "(3D Model View)".

FIG. 4 shows a more advanced solution where one has menus (4200) to (4202) which contain operations; a navigation area (4001) containing navigation buttons, such as move camera/model (4002), move camera/model up and down (or in and out) (4003), and rotate camera/model (4004); and a "properties bar" (4108) such as contains adjustment of lighting (4100) and colors (4104). "+X" puts a light far down on the positive X-axis

(4101), "-X" puts a light far down on the negative X-axis, and similarly for the other axes (eg (4102)). "Follow camera" (4103) makes the lights follow the camera. If "follow camera" is not checked, the lights will use the coordinate system of the 3D model. If "follow camera" is checked, the lights will use the coordinate system of the camera. Different cameras can be used such as e.g. "arcball" and "walk/navigate" camera. A list of materials (and possibly light) in the 3D model is listed in (4105). Here the user can choose a material/light/e.I. where the properties of this can be changed (eg diffuse colour, specular colour, ambient colour, texture, shader or the like) (eg (4106) and (4107)). Such operations and selections are sent to the Mesh server where they are used. The user interfaces can naturally have a different design/layout in the invention. FIG. 5 and 6 illustrate the user interfaces of the web applications "Course Catalog" (5000) and "Course Viewer" (6000). The course catalog shows a list of courses that are available. The images (image 1 to 3) show a "thumbnail" image for the course. The fields "(Information 1)" to "(Information 3)" contain the title and descriptions of the courses. There will be a longer list of courses. The course view shows the content of a course. The "(View)" area displays a video/presentation/HTML/images etc. The "(Controls)" area contains controls that can be used to control playback. The "(Other)" area contains other things such as "rating" of the content, various operations (see e.g. YouTube), comments, and the like. In the area on the right we have a "course image" which is a "thumbnail" for the course, "(course title)" is the title of the course, "(course info.)" is a short description of the course, "Content" is a link list for access to the various parts of the course, and "Materials/references" is a list of links to various materials and references for the course. A person skilled in the art will be able to see that the user interfaces can have a different design and/or layout, but still be conceptually covered by the invention. FIG. 7 and 8 illustrate the user interface of the remote play client used on the user's computer to remotely play computer games (or specifically web-based computer games) over the Internet. The user interface may, for example, be displayed as a Windows dialog box window as illustrated in FIG. 7 and 8 (title bar, minimize button, close/end button and similar window elements). Other types of user interfaces that are (or will become) common in operating systems, platforms, web browsers, and the like, for the user interface, are also covered by the invention. FIG.

7 shows the user interface that appears at start-up (of the program) and possibly after a remote play session is finished. The user interface contains information, and the user specifies a server (or computer game) in the "combo box" (or other list). The user interface may also contain configuration controls to configure such things as the bitrate used for audio-visual compression, full screen, "3D vision, grab input, in-game cursor," packet size, image scaling, frame rate, network port, username, and

password. This list is an example and can of course be changed for different implementations. The "Connect" button (or similar) is used to start the remote play session (against the server). The Refresh button (or similar) is used to update the list of servers (or similar). The cancel button (or similar) is used to close/exit the user interface/client. The remote play client shows the user interface in FIG. 8 when the remote play session executes (except in full screen mode where the game view covers the screen). Game View displays the decoded video signal from the server (i.e. a compressed audio and video stream of the screen images of a

computer games executing on the server). The video signal can be compressed with any video and audio codec (eg Microsoft WMV2 and WMA). The remote gaming client captures user input (such as keyboard, mouse, gamepad, joystick, Directlnput, or the like) and sends the user input data compressed (or uncompressed) to the server (ie the computer game). The remote play client is relatively straight forward and easy to implement. The remote playback client can also contain a presentation system to visualize 2D, 3D and multimedia content

(with user interfaces) in the game view. The integration of the presentation system into game viewing is relatively straight forward and simple, and the video stream (ie for remote gaming) can e.g. displayed with a Video element in the presentation system. Components are needed on the server

to enable remote play. Program code, i.e. a stub (1002) and/or (1207), is needed in the computer game which accepts the user input (possibly decompressing this) and injects/handles this in the computer game. The computer game must also contain program code (i.e. stub) to manage the start and stop of remote play (with configurations), capture ("capture") of

screenshots and sound in the computer game, compression of audio and video, as well as sending audio/video packets over the network. Different compression techniques can be used. In DirectX, the various Present functions are a natural place for "capture" of the screen image. The invention also covers computer games (and servers) that have such components for enabling remote gaming. The user interfaces of FIG. 7 and 8 can be put together in many ways, e.g. as two dialog boxes/windows, such as Microsoft Remote Desktop, so that the window in FIG. 7 is changed to the window of FIG. 8 when the user presses "Connect", etc. It is also possible that other layouts and names are used in the interfaces.

FIG. 9 illustrates the "desktop application" that is typically available in the "system tray." The desktop application will typically start when the computer starts up (as an icon in the system tray, such as e.g. Skype). The desktop application can also be implemented as a service (eg as an NT Service in Microsoft Windows). For example, the user interface may be displayed as a Windows dialog window as illustrated in FIG. 9 (title line, minimize and maximize button, close/end button and the like). Other types of user interfaces that are (or will be) common in

operating systems, platforms, web browsers, and the like, for the user interface, are also covered by the invention. The menu bar (ie Menu, Menu2, etc.) consists of menu functions. Below the menu bar is the toolbar (ie Button1, Button2, etc.). The toolbar usually contains frequently used functions (which are also found in the menu). Below the toolbar is a "tab" control that displays main categories of functionality (such as "Game Sites" and others). It is applicable that the menu bar and the toolbar differ when the "tab" control is used (ie the main category functionalities have different menu bars and toolbars). "Game Sites" are shown as selected in FIG. 9. The desktop application may also include a number of main category functionalities (eg "instant messaging, remote desktops, FTP tools, cache, licenses, heads-up display tools," etc.). The "Game Sites tab" contains a list of registered video games (local downloadable video games and/or remote play video games). The list in the figure shows 3 examples of computer games in the list. A "scrollbar" (on the right) can be used to "scroll" in the list. Each computer game in the list is shown with a small "thumbnail" image (Image, Image2, and Image3) that shows a small representation of the computer game. Next to the "thumbnail" image, there is an information field (e.g. Information 1) that contains information about the computer game (such as descriptions, publisher, publication date, URL, the number of bytes it takes up on the hard drive, the number of files, usage statistics, etc.). The information field can also contain

controls (such as buttons and the like). Typical functions that can be performed on each individual computer game in the list are starting local computer games in a web browser (or in a local client), starting remote playing of the computer games, as well as managing the computer games (delete, allocate, synchronize, compress, backup, etc.). Computer games can typically be registered in the list from the web browser plug-in, or from the desktop application directly (e.g. "add game" in the menu). If a computer game is registered in from the web browser plug-in, it can e.g. happen via a Windows message (in Microsoft Windows), registry, a file, a "remote procedure" call, or similar. The desktop application will retrieve an XML list of all the files to be downloaded and/or synchronized, after which the files will be downloaded. The amount of bandwidth to be used and similar can be configured. The files can of course be compressed (e.g. zip/rar and the like) and encrypted (e.g. RSA and the like). Any structure can be used for this XML file, and e.g. a list of "file" and "folder" elements (including file/folder name, date, bytes, md5/crc, URL, ageRating, etc.) within a "synch" element. When the desktop application has finished downloading, it can send a message back to the web browser plug-in and/or remote play client (progress messages can also be sent). Furthermore, another central function of the desktop application is to synchronize file structures (ie files and folders) between the user's machine and the servers. This is an important function together with the Web OS because collaborative projects with different users will result in a larger number of files and folders being uploaded to the servers. Synchronization of these, or subsets of these, is an important functionality in the desktop application. Setting up such a synchronization in the desktop application can e.g. is done in the same way as for game resources, i.e. that a "game site" (FIG. 9) is registered in the desktop application. The desktop application will be configured with which file structure on the server is to be used (e.g. for XML data from the server) and where the file structure is to be stored locally. The desktop application can further be configured for what kind of files are to be synchronized (e.g. blend files), when they are to be synchronized (e.g. immediately upon change, once a day, and the like), and so on. It is also possible that the setup of synchronizations with the Web OS is placed under a separate "tab", or in a separate dialog box that is opened from the menu. It is necessary in collaborative projects to be able to lock files and/or folders. This indicates to other users that the file is locked by a user and that this user has exclusive editing options. Other users cannot then edit that file and/or file structure. This is necessary because if it were not possible to lock files, then two or more users would be able to change a file at the same time and the synchronization would overwrite the file

and/or the file structure on the server arbitrarily (depending on the time the users choose "save" in the editor). Locking files can e.g. happen in the Web OS in the file explorer, the local operating system (right-click file and select "lock"/"unlock"), and/or the desktop application. A log (with a copy of old files) can also be stored on the server to preserve the history.

FIG. 10 shows the source code structure for a minimalist computer game (template code) made in Java. This structure (Load/Update/Draw) is a possible starting point for Java-based computer games.

The main idea in relation to industrial exploitation in Norway is mainly in relation to developing and offering "computer game websites," which use our web browser plug-in, desktop application, and

remote gaming techniques to produce and provide websites (on the Internet), which look and function the same way (in terms of user experience) "main title" computer games do today. As of today, text, video and simple multimedia content are mainly used for the development of websites. We believe that computer game-based experiences are a natural next step, in the future, for content on the Internet/Web. Our techniques represent specific procedures for creating computer game websites. We plan to offer products, services, etc., to create such computer game websites for companies, organizations, individuals, etc., in Norway. We also plan to create "serious computer games" with knowledge content and positive values with this system, where students and computer game users are involved in collaborative projects. We will offer courses and education in this system and eventually offer educational programs that will lead to associate's, bachelor's, master's and doctorate degrees in computer game development. Naturally, we have to accredit the education programs before that becomes possible. Furthermore, we believe that a

sometime in the future (both web-based and "stand-alone") computer games will be able to load 3D models, textures, media, etc. directly from "the cloud". It is becoming increasingly possible, as the Internet connection of users continues to improve. The users (of computer games) will often have their own "avatars" (a 3D representation of themselves or another character) on servers at various

suppliers who offer the creation of such "avatars". Users will likely also have a wide variety of "assets" as well (eg car, house, AI friends, clothes, items, spaceships, etc.). We also believe that users will create their own game worlds (e.g. level design, models, story, etc.). There will be a need for many different collaborative services (e.g. avatar authoring,

asset authoring, LOD editors, level designers, world environment designers, building design, landscape design, etc.). Digital rights management (DRM) is important. We propose that 3D models, textures, etc. can be encrypted in the Web OS (and/or other tools). A specific encryption algorithm (e.g. RSA-based) is not specified. The invention covers various encryption algorithms. We envision that we offer licensing program code that can be used to decrypt the content for use on the user's machine. We envision that we will offer a DRM solution architecture similar to Microsoft Windows Media Rights Manager. We believe there will be a great need for many different web-based computer game experiences, such as e.g. "virtual studios, virtual expos, virtual meetingrooms, virtual seminars, virtual classrooms, virtual corporation," and so on, with VR glasses, grid computing, ray-tracing, iPads, etc.

Although the invention has been described with reference to one embodiment, those skilled in the art will realize that variations in form/detail can be made without deviating from the intent in the scope of the invention as defined in the appended claims. The specific details above are intended to be illustrative only and the scope of the invention is defined by the appended claims. For example, the invention can be practiced as remote development and remote gaming in a web browser and the invention can be integrated into operating systems, web browsers, hardware and computer games.

Claims (10)

1. System for developing computer games via the Internet, characterized by a web operating system displayed in a web browser and/or web browser plug-in; the web operating system contains a course catalogue, which contains a list of courses, where each course has a course description with an image; the web operating system contains a course view, which contains a display area, a controller area, course image, course title, content list and other elements; the web operating system contains a Mesh Viewer, which displays a 3D model, where you can change materials and lighting settings for the 3D model, and interactively change the 3D view so that you can see the 3D model from different angles and magnifications; the web operating system contains a library of articles and references; a desktop application is installed on the end user's computer, containing a list of computer games/computer game projects, where computer game resources/file structures are synchronized with system servers/version control systems so that an updated file structure of source code and data files is available on the end user's computer for editing and synchronized uploading to system servers/version control systems ; the desktop application can be used to start the computer game in a context where the computer game is debugged/developed/tested on the end user's local computer, and/or on the system servers in case of remote gaming, so that the end user can contribute to debugging and development of the computer game; the desktop application can be used to configure a HUD in the computer game, where the HUD executes locally (1002) or on system servers (1207), and connects to the system servers; and the desktop application can be used to start the computer game, with local play or with remote play, in a web browser and/or web browser plug-in on the end user's computer. 2. System according to claim 1, characterized by an Accessible OS being offered to blind and partially sighted end users. 3. System according to claim 1, characterized in that the computer game executes both on the end user's computer and on system servers, so that the video stream from the system servers is displayed inside the computer game on the end user's computer. 4. System according to claim 1, characterized in that the web operating system has an interface/layout with icons (2001), web application windows (2008), start menu (2003), taskbar with icons (2004), and clock (2007); and the web applications include a 3D model editor and an IDE. 5. System according to claim 1, characterized in that a remote gaming client can be used to remotely play and/or remotely develop computer games over the Internet. 6. System according to claim 1, characterized in that one or more files use DRM so that these are encrypted. 7. System for developing computer games via the Internet, characterized by a web operating system displayed in a web browser and/or web browser plug-in; the web operating system contains a course catalogue, which contains a list of courses, where each course has a course description with an image; the web operating system contains a course view, which contains a display area, a controller area, course image, course title, content list and other elements; the web operating system contains a Mesh Viewer, which displays a 3D model, where you can change materials and lighting settings for the 3D model, and interactively change the 3D view so that you can see the 3D model from different angles and magnifications; the web operating system contains a library of articles and references; the web applications include a 3D model editor and an IDE; and The IDE allows the user to edit and debug the computer game's source code, so that a debugging remote play view is displayed in the web operating system with a HUD (1207) and/or one or more web applications that display debugging information and control the debugging/computer game. 8. System according to claim 7, characterized in that the computer game executes both on the end user's computer and on system servers, so that the video stream from the system servers is displayed inside the computer game on the end user's computer. 9. System according to claim 7, characterized in that the web operating system has an interface/layout with icons (2001), web application windows (2008), start menu (2003), taskbar with icons (2004), and clock (2007); and an Accessible OS is offered to blind and visually impaired end users. 10. System according to claim 7, characterized in that a desktop application can be used to synchronize and/or download computer games/computer game resources/file structures with/from system servers; and the desktop application can be used to start the computer game, with local play and/or with remote play, in a web browser and/or web browser plug-in on the end user's computer.