JPWO1998033145A1 - Graphic data generating device, graphic data generating method and medium - Google Patents

Abstract

(57) [Summary] The attention function provides an image of an object viewed from any viewpoint in an easy-to-understand manner. The user uses the mouse to set the operation mode to "Navigate" and selects the object they wish to observe by clicking the left button of the mouse. In response to the selection operation of attention ON by operating the right button of the mouse, the model editing tool 420 turns the background of the viewpoint position display panel yellow and moves the object to the center of the editing window for display. The model editing tool 420 displays the object from any viewpoint in response to the user's dragging operation with the mouse. The object is observed until attention OFF is commanded by operating the right button of the mouse.

Description

[Detailed Description of the Invention] Graphic data generating device, graphic data generating method and medium thereof Technical field The present invention relates to a graphic data generating device, graphic data generating method and medium thereof, and in particular to a graphic data generating device, graphic data generating method and medium thereof used for comprehensively editing the shape and position of three-dimensional figures used to express objects in a three-dimensional virtual space, and scripts that are activated in response to client (user) operations on a displayed three-dimensional image.

More specifically, the present invention relates to an attention function. The attention function is used to confirm the shapes of objects displayed in the 3D View window. The attention function centers on one of one or more objects selected by the user with the mouse in the 3D View window, and places and displays each object in a three-dimensional virtual space as viewed from any viewpoint specified by the user within the content creation software tool 4.

BACKGROUND ART VRML (Virtual Reality Modeling Language) is known as a description language that can handle three-dimensional information in a unified manner using the framework of the World Wide Web (WWW), which provides a variety of information on the Internet, a global computer network.

First, the historical background leading up to the development of VRML will be explained.

One well-known information system available over the Internet is the World Wide Web (WWW), developed by the Swiss European Center for Nuclear Research (CERN). The WWW allows multimedia (information) such as text, images, and sound to be viewed in hypertext format. Based on a protocol called HTTP (HyperText Transfer Protocol), the WWW asynchronously transfers information stored on a WWW server to terminal devices such as personal computers. The WWW is essentially comprised of a server and a browser.

A WWW server consists of server software called an HTTP daemon and HTML (Hyper Text Makeup Language) files that store hypertext information. A daemon is a program that runs in the background and performs management and processing when working on a UNIX system.

Hypertext information is expressed in a description language called HTML. Hypertext descriptions in HTML express the logical structure of text using formatting specifications called tags, enclosed in "<" and ">". Links to other information are described using link information called anchors. A URL (Uniform Resource Locator) is used to specify the location of information using an anchor.

HTTP is the protocol used to transfer HTML files over a TCP/IP (Transmission Control Protocol/Internet Protocol) network. HTTP transmits information transmission requests from users (clients) to a WWW server and transfers the hypertext information in HTML files to the client.

The most widely used environment for using the WWW is the WWW browser.

The word "browser" means to view, and a browser performs the task of querying a server for information in response to user actions. WWW browsers are client software such as Netscape Navigator (a trademark of Netscape Communications, Inc.). Using a WWW browser, users can browse files on WWW servers on the global Internet that correspond to URLs, known as home pages. Similarly, surfing the web allows users to access a wide variety of WWW information sources by following linked home pages one after another.

In recent years, the WWW has been further expanded to allow for the description of three-dimensional space and the establishment of hypertext links to objects rendered in three-dimensional graphics, and specifications for a three-dimensional graphics description language called VRML have been established, which allows for sequential access to WWW servers by following these links. VRML browsers have also been developed to display three-dimensional space described based on the VRML specifications.

For details on VRML, see, for example, "Understanding VRML: Building and Browsing 3D Cyberspace," by Mark Pesce, translated by Koichi Matsuda, Teruhisa Kamachi, Shoichi Takeuchi, Yasuaki Honda, Junichi Rekimoto, Masayuki Ishikawa, Ken Miyashita, and Kazuhiro Hara, first published March 25, 1996, Prentice-Hall Publishing, ISBN 4-931356-37-0 (original: VRML: Browsing & Building Cyberspace, Mark Pesce, 1995, New Readers Publishing, ISBN 1-56205-498-8), and "The Latest Trends in VRML and CyberPassage," by Koichi Matsuyama and Yasuaki Honda, bit (Kyoritsu Shuppan), 1996, Vol. 28, No. 7, pp. 29-36, No. 8, pp. 57. pp. 109-1106, No. 9 pp. 29-36, No. 10 pp. 49-58.

The official and complete specification of "The Virtual Reality Modeling Language Version 2.0", ISO/IEC CD 147 72, August 4, 1996, is available at the following website address:

http://www.vrml.Org/Specifications/VRML2.0/FINAL/Spec/index.html The Japanese version is available at the following website address:

http://www.webcity.co.jp/info/andoh/vrm12.0/spec-jp/index.html For example, Sony Corporation, the present applicant, has developed and commercialized "Community Place™ Browser/Bureau" as a browser and shared server software for VRML 2.0. A beta version (trial version) of this software is available for download from the following website: http://vs.sony.co.jp.

VRML 2.0 makes it possible to describe and express the autonomous behavior of objects in a three-dimensional virtual space.

When using VRML 2.0 to create VRML content in which objects move dynamically within a three-dimensional virtual space, the following process is typically followed. From here on, a collection of VRML files, script files, etc., used to realize the behavior of a series of objects within a single virtual space will be referred to as VRML content.

VRML Content Creation Procedure The general procedure for creating VRML content is described below.

(1) Model Creation The shape and position of the object (model) to be placed in the virtual space are described based on VRM L 2.0, and a basic VRML file is created.

(2) Sensor Node Description Add sensor node descriptions to the VRML file, such as a TouchSensor, which generates an event when a mouse click (pointing) is performed on an object in the virtual space, or a TimeSensor, which generates an event at a preset time.

(3) Routing Description Add routing descriptions to the VRML file to transmit events that occur in response to pointing operations on objects with attached sensor nodes.

(4) Script Node Description Add a script node description to the VRML file to pass events propagated by routing to an external script.

(5) Creating a Script File Write (program) a script using a language such as Java (Java is a trademark of Sun Microsystems, Inc.) to implement pre-defined behavior for each object in the virtual space based on events transmitted via the script node, and create a script file.

Through the above description steps (1) to (5), the desired VRML content is created.

When creating VRML content based on VRML 2.0 that involves autonomous object behavior in a virtual space, existing authoring software called a modeler, such as 3D Studio Max™, is used to create the object's shape and animation, and then output in VRML 2.0 format. If the modeler does not support the VRML 2.0 format, a converter or similar tool must be used to convert it to VRML 2.0 format.

Furthermore, descriptions of various sensor nodes, etc., as specified by VRML 2.0, are added to the VRML file using a text editor, and furthermore, scripts are created in Java using a text editor, and corresponding script nodes and routes are added, etc., are repeatedly added.

Finally, to check the actual operation, start a VRML 2.0 compatible VRML browser and check the behavior of the objects by clicking with the mouse, etc.

This method of creating VRML content requires a great deal of tedious manual work and is extremely inefficient. For example, adding a field to a script node requires modifying both the script file and the VRML file. Furthermore, consistency between the two must be maintained.

Additionally, when specifying event routing, the event type (data format) must be consistent. If the routing or other description format is incorrect, a syntax error will occur when the file is loaded in a VRML browser, requiring the file to be corrected again. Furthermore, the VRML browser must be reloaded each time a new node is added, resulting in extremely inefficient work.

Furthermore, the conventional method was found to have some shortcomings in its interaction performance. One example of this interaction deficiency is the cumbersome and inefficient confirmation process during world creation. Figure 1 shows a flowchart of the conventional world creation method. World creation is broadly divided into two stages: the first stage is creating the model, and the second stage is creating the interaction. Details of this process will be discussed later in comparison with the embodiment of the present invention. Confirmation is required during world creation, but with the conventional playback method shown in Figure 1, confirmation requires the use of a browser, as illustrated in step 108.

Furthermore, the attention function has traditionally been inadequate. The attention function is used to confirm the shape of objects displayed in the 3D View window. It centers on one of one or more objects selected by the user with the mouse in the 3D View window, and places and displays each object in a 3D virtual space as seen from any viewpoint specified by the user in the content creation software tool.

DISCLOSURE OF THE INVENTION The objective of the present invention is to achieve a desirable attention function.

According to a first aspect of the present invention, there is provided a graphics data generation device comprising: display means for displaying a three-dimensional object within an editing window; instruction means for issuing an operation command for the object displayed by the display means; and attention processing means, wherein the attention processing means enters an attention mode in response to a first predetermined operation command, selects an object selected by the instruction means, moves the selected object to the center of the editing window, and displays the selected object, thereby allowing the selected object to be viewed from any viewpoint.

Preferably, the attention processing means terminates its operation in response to a second predetermined operation command.

Specifically, the attention processing means is executed by an editing means that creates the content.

In accordance with a second aspect of the present invention, there is provided a graphics data generation method which switches to an attention mode in response to a first predetermined operation command, selects an object in response to the selection, moves the selected object to the center of the editing window and displays it, and allows the selected object to be viewed from any viewpoint.

Preferably, the attention mode is terminated in response to a second predetermined operation command.

According to a third aspect of the present invention, a medium is provided that carries a program for executing the above-described graphic data generation method. That is, according to the present invention, a medium is provided that carries a program for creating content in a three-dimensional virtual space through an interactive interaction with a display means that displays three-dimensional objects in an editing window, the medium containing the program switching to an attention mode in response to a first predetermined operation command, selecting an object according to the selection, moving the selected object to the center of the editing window and displaying it, and allowing the selected object to be viewed from any viewpoint.

The program may be executed on a computer system or transmitted over a network including a server device.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects and features of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings.

FIG. 1 is a flowchart showing a conventional method for creating VRML content.

FIG. 2 shows the configuration of a network system that handles a three-dimensional virtual space in an integrated manner, to which the graphic data generating device of the present invention is applied.

FIG. 3 is a diagram showing the configuration of a software tool for creating content according to the present invention.

FIG. 4 is a flowchart showing a method for creating VRML content performed by the content creation software tool illustrated in FIG.

FIG. 5 is a flowchart illustrating the basic verification process in the process of creating the VRML content illustrated in FIG.

FIG. 6 is a flowchart illustrating a preferred verification operation process in the process of creating the VRML content illustrated in FIG.

FIG. 7 is a diagram showing the configuration of a computer system in the network system shown in FIG.

FIG. 8 is a configuration diagram of a content creation software tool as an embodiment of the content creation software tool illustrated in FIG.

FIG. 9 illustrates a menu displayed on a display device in a computer system by the graphical user interface portion of the content creation software tool of FIG. 8.

10A-10C are enlarged views of the Conductor window illustrated in FIG. 9.

FIG. 11 shows a pop-up menu displayed in the 3D View window shown in FIG.

Figures 12 to 14 show Point of Interest figures.

FIG. 15 is a flowchart showing the process of displaying and setting the area of the sensor node.

Figures 16 and 17 show examples of popups in the Parallel View function.

18 to 22 are diagrams showing display examples using the attention function.

FIG. 23 is a flowchart showing the processing of the attention function.

FIG. 24 is a flowchart of the routing editing process.

25 to 27 are diagrams showing display examples in the routing editing process.

FIG. 28 shows an example of a display of an object for creating VRML contents.

FIG. 29 is a flowchart showing the process of creating the first VRML content.

30 to 34 show examples of windows displayed when creating the first VRML content.

FIG. 35 is a flowchart showing the process of creating the second VRML content.

36 and 37 are diagrams showing examples of the script expert window when creating the second VRML content.

38 to 44 show examples of windows displayed when creating the second VRML content.

FIG. 45 is a flowchart showing the third process for creating VRML content.

46 to 49 show examples of windows displayed when creating the third VRML content.

BEST MODE FOR CARRYING OUT THE INVENTION This section describes embodiments of the graphic data generation device, graphic data generation method, and media carrying a program implementing this graphic data generation method.

Network System FIG. 2 shows the configuration of a network system 1 that handles a three-dimensional virtual space in an integrated manner, as an example to which the graphic data generating device, graphic data generating method and medium of the present invention are applied.

The network system 1 is composed of an internal corporate network 10, the Internet 12, an Internet provider 14, an ISDN (integrated services digital network) 16, and a client (subscriber) system 2, all of which are interconnected.

In reality, the network system 1 may include multiple components, such as an in-house network 10, the Internet 12, an Internet provider 14, and a client system 2. However, for simplicity, only one of each is shown in FIG. 2.

The corporate network 10 consists of a hard disk drive 100, a server device 102, a local area network (LAN) 104, and a gateway server (GWS) 106.

The Internet 12 connected to the corporate network 10 is composed of router devices 120 and 124 and a digital communication line 122.

An internet provider 14 is provided between the internet system 12 and the ISDN 16.

In network system 1 shown in FIG. 2, an intra-company network 10 and a client (subscriber) system 2 are connected via an Internet system 12, an Internet provider 14, and an ISDN 16. In this specification, LAN 104, Internet 12, Internet provider 14, and ISDN 16 are referred to as the network, and this network carries out data communication between server device 102 and client system 2.

The client system 2 connected to the ISDN 16 is a computer system having a personal computer (PC) 20, a display device (DSP) 24, and an input device (IN) 26. A storage device 28 is also connected to the computer system. However, the display device 24, input device 26, and external storage device 28 connected to the personal computer (PC) 20 may be part of the computer system or may be externally located. In this embodiment, the display device 24 and input device 26 are described as part of the computer system, and the external storage device 28 is described as being external to the computer system.

Server Device 102 The server device 102 in the intranet 10 is, for example, a server device for Community Place (trademark) (for example, http://vs.sony.co.jp/), which acquires VRML content, that is, VRML content consisting of VRML files that indicate the shapes and positions of three-dimensional objects written by users (clients) in VRML 2.0, and script files that are written by users in a programming language such as Java and are activated in response to user operations on objects, via a network or the like, stores the content in the hard disk drive 100, and manages the storage results.

Hereinafter, a collection of VRML files (extension .wr1) and Java script files (extension .java) will be referred to as VRML content.

The server device 102 also transmits the 3D virtual space VRML content stored on the hard disk drive 100 to the client system 2 via the server device 102, LAN 104, Internet system 12, Internet provider 14, and ISDN 16 (hereinafter, these communication nodes within the network system 1 are collectively referred to as the "network"), and displays it on the display device 24.

Furthermore, in response to a request from the client system 2, the server device 102 transfers, for example, a program, such as a software tool for content creation, stored on the hard disk drive 100 to the client system 2 via the network.

Alternatively, a content creation software tool program may be stored on a floppy disk 280 or an MO disk 282 and distributed to the client system 2.

Description of Program Media: The following describes the configuration and operation of the client system 2 as a medium for carrying the graphics data generation device, graphics data generation method, and program for implementing the method of the present invention. However, the term "medium" as used herein includes not only a recording medium storing a computer program for implementing the graphics data generation method of the present invention, but also refers to not only the client (subscriber) system 2, the details of which will be described in detail in the following embodiments, but also a program transmission medium for downloading a computer program to the client system 2 via the network system 1 of FIG. 2 to implement the graphics data generation method of the present invention. This is because, as will be clear from the following description, the graphics data generation method of the present invention is not subject to centralized implementation constraints and can be implemented at any location. Of course, the present invention can also be implemented locally.

FIG. 3 shows the configuration of the graphic data generation method and device of the present invention, particularly the content creation software tool 3 (Community Place™ Conductor), which is processed in the client (subscriber) system 2 in FIG. 1. The content creation software tool 3 includes a graphical user interface (GUI) 31, an object manager 32, a Java compiler 33, a scene graph manager 34, a Java VM 34B, a parser 34C, an HTML browser 35, and a backup manager 36.

The graphical user interface unit 31 displays various windows.

The Java compiler 33, an external program, compiles Java programs. The scene graph manager 34 is a common part with the browser. The scene graph manager 34A handles the hierarchical structure of VRML nodes. The parser 34C parses VRML files. The Java VM 34B executes scripts written in Java.

The HTML browser 35, an external program, is used to display anchor nodes or help files for VRML nodes written in HTML format.

The section 34, consisting of the scene graph manager 34A, Java VM 34B, and parser 34C, can be used in common with, for example, the Community Place™ browser provided by Sony Corporation.

When the "Play button" on the display screen is pressed with the mouse to enter "Play mode," the backup manager 36 becomes enabled and begins preparing to back up each field value. When the "Stop button" is pressed, the accumulated field values are restored in order, restoring the original screen. In other words, the content creation software tool "Conductor" is designed to allow users to perform everything from world editing to operation verification. When the user presses the "Play button" to enter "Play mode," Conductor begins browser emulation. In this state, the state of each field changes in response to user interaction, such as objects moving. However, when the "Stop button" on the display screen is pressed with the mouse to return to "normal editing mode," everything must return to the state it was in before the "Play button" was pressed. This requires the process of backing up each field value and restoring it.

The Backup Manager 36 operates as follows: When the Backup Manager 36 enters "Play Mode," it becomes enabled and begins preparing to back up each field value. Then, the first time a field value is changed due to a dynamic object change, the original field value is saved. Field values are saved sequentially in a stack (the "Stack" method). When the "Stop" button is pressed, the saved values are restored sequentially (by popping the stack), restoring the original window display state.

Just as a large program can be split into multiple files, it is desirable to split a world into multiple files when it becomes large enough. The object manager 32 is responsible for managing consistency in such cases.

The Route Editor (not shown) is used to define events between fields using route statements. In this invention, nodes are specified using the GUI 31, eliminating the risk of specifying an incorrect name. Even if the user changes the node for the route, the Object Manager 32 manages the DEF for each scope, so there is no error and the route statement can be updated automatically.

Scripts are used to create a more interactive world using languages such as Java, but creating scripts is known to be difficult when creating content, especially when it comes to combining Java with VRML.

In order to overcome this problem, the present invention provides a script expert (not shown), which will be described in detail below.

Figure 4 is a flowchart showing the processing performed by the content creation software tool 3. To address the above-mentioned conventional deficiencies, the present invention eliminates manual operations and allows efficient, automated processing within the entire tool using the GUI 131. An overview of this configuration follows. As noted above, the content creation software tool 3 illustrated in Figure 3 can be implemented in any part of the network system 1. However, for simplicity, the following description will primarily focus on the case where it is implemented in the client system 2.

The processing details of Figure 4 are described below. The processing of the content creation software tool 3 can be broadly divided into (1) initialization, (2) model creation, and (3) interaction creation.

In step 201, model data is downloaded, for example, from hard disk drive 100 to hard disk drive 214 of computer system 20. That is, a model written in VRML 2.0 is loaded into computer system 20 of client system 2. The loading method can be downloading to computer system 20 from any part of network system 1.

In step 202, editing of the model (object) is performed, for example, by rearranging the model, changing its attributes, etc.

Interactions are created in steps 203 to 207. That is, Sensors are added in step 203, script nodes are added in step 204, the Java program is edited in step 205, the Java program is compiled in step 206, and routing is edited in step 207.

In step 208, the user confirms the results of the above processing by clicking the "Play" button in the Conductor window (Figure 10) on the display device screen with the mouse. The confirmation operation described with reference to Figure 1 is performed by launching a browser after the VRML content has been created, but step 208 can be performed at any time without launching a browser. Details will be described later with reference to Figures 5 and 6. According to the method of the present invention, when the user presses the "Play" button on the content creation software 3, the editing screen, i.e., the 3D Perspective View window (editing window) shown in Figure 9, etc., replaces the display screen of the VRML browser and displays the content being created.

In addition, the content creation software tool 3 of this embodiment allows for interactive operations such as adding sensors and editing routing through a graphical user interface (GUI) 31.

The content creation software tool 3 also includes a function called Script Expert, which allows interactive creation of script templates and automatically compiles them when the user checks their operation. Therefore, the content creation software tool 3 of this embodiment includes an automatic compilation function when checking their operation. As a result, the content creation software tool 3 of this embodiment eliminates the need to perform these tasks by inputting command strings (command line). These functions significantly reduce the time required to create 3D virtual space content using User VRML 2.0.

In the present invention, adding a sensor in step 203 can be easily performed by dragging and dropping.

Additionally, in the present invention, the routing editing in step 207 can also be easily performed using a GUI.

Furthermore, the present invention has a function for checking event types when adding routes using the route editor, preventing the user from specifying incorrect routes.

In particular, in this invention, to address the deficiencies described with reference to FIG. 1, as described above as step 208 and illustrated in FIG. 5, the following steps are performed at any time without launching a browser: (1) S211: When the user presses the "Play" button on the display device screen as a predetermined first operation, (2) S212: The emulator is launched and the current operation can be confirmed by the emulator's operation. (3) S213: After confirmation, the user can press the "Stop" button on the display device screen as a predetermined second operation to return to normal editing mode. This allows users to easily check on the spot, by simply pressing the "Play" button, using the browser emulator, when adding nodes or changing the program for a script node while creating normal VRML content. As a result, if a compiler error occurs, the error can be easily detected, immediately corrected, and recompiled.

In the above verification operation, it is even more preferable to operate the backup manager 36 in conjunction with the browser emulator. That is, during the verification operation of step 208, as illustrated in FIG. 6, (1) S221: When the user presses the "Play button" as a first predetermined operation, (2) S222: The browser emulator operates as described above, and the backup manager 36 is enabled, entering a backup-enabled state. (3) S223: In this state, for example, when a dynamic object that starts moving when clicked is clicked, (4) S224: The backup manager 36 sequentially saves field values that define the dynamic behavior of the object.

(5) S225: When the user presses the "Stop" button as a second predetermined operation, the verification operation is completed. (6) S226: The backup manager 36 sequentially restores the saved field values and resets them to their initial state. This restores the object to its original state before the verification operation. These operations require only the "Play" and "Stop" buttons, improving operability and shortening processing time.

Client (Subscriber) System 2 and Computer System 20 Figure 7 shows the configuration of the computer system 20 shown in Figure 2. In Figure 7, the external storage device 28 shown in Figure 2 is specifically illustrated as a floppy disk (FD) 280 and/or a magneto-optical (MO) disk 282, and the input device 26 is specifically illustrated as a keyboard (KB) 260 and/or a mouse (MOUSE) 262.

In implementing the present invention, the display device 24 can be any color display device suitable for interactive information display processing in cooperation with information input means such as a keyboard or mouse, such as a color CRT display or a color LCD display. Hereinafter, when referring to the display device 24 in this specification, we will be referring to a color CRT display or a color LCD display in cooperation with information input means such as a keyboard or mouse.

The computer system 20 is, for example, a multimedia-capable computer with communications capabilities connected to the ISDN network 16, and includes a CPU 202, a ROM 204, an input interface (IN I/F) 208, a display device 24 controller (DSP-C) 210, a video signal recording RAM (VRAM) 212, a hard disk drive (HDD) 214, a floppy disk drive (FDD) 216, an MO disk drive 218, and a line interface 220 connected via a bus 200.

The CPU 202 executes various control programs stored in the ROM 204 and the HDD 214 to perform various operations described below. For example, the CPU 202 displays various image data on the display device 24 via the DSP-C 210, and inputs data from the KB 260 or the mouse 262 via the input interface 208. The CPU 202 also stores data on or reads data from a floppy disk 280 serving as the external storage device 28 via the floppy disk drive device 216, or stores data on or reads data from an MO disk 282 serving as the external storage device 28 via the MO disk drive device 218. The CPU 202 also communicates with the ISDN 16 via the line interface 220.

Computer system 20 displays on display device 24 images of VRML content of a three-dimensional virtual space transmitted from server device 102 via a network including ISDN 16, and shows them to the user (client).

The computer system 20 installs the content creation software tool 3, supplied from the server device 102 via the network or external storage device 28, onto the hard disk drive 214, launches the content creation software tool 3 (program) in response to client operations using the KB 260 or mouse 262, creates VRML content for a three-dimensional virtual space, stores it on the hard disk drive 214, or uploads it to the server device 102 via the network or external storage device 28 (floppy disk 280 and/or MO disk 282).

Furthermore, the computer system 20 responds to a user's pointing operation using the input device 26 by, for example, changing the display color of the pointed object or changing the display content of the object in the three-dimensional virtual space.

Display of three-dimensional virtual space: In this way, the client system 2 having the computer system 20 can interactively change the display content on the display device 24 in response to user operations on objects in the three-dimensional virtual space. Therefore, by using the client system 2, the user can experience a realistic sensation (sense of reality) as if they were actually moving objects in the three-dimensional virtual space, touching and manipulating the objects, and moving and making sounds.

Furthermore, the server device 102, which acquires VRML content of a three-dimensional virtual space from the client system 2 via the network, stores the VRML content on the hard disk device 100, making it available to Internet subscribers over the Internet system 12. When the server device 102 is accessed via the network from the client system 2, it transfers the VRML content to the client system 2 via the network.

The computer system 20 of the client system 2 uses a browser to display on the display device 24 a three-dimensional virtual space based on the VRML content sent from the server device 102.

If VRML content for a closed three-dimensional virtual space is created within the client system 2 and is not to be shared with other users, it is sufficient to display the created VRML content directly on the display device 24 using a browser; there is no need to upload the created VRML content to the server device 102.

Interactive display : The user uses the mouse 262 to point to a desired position on the image displayed on the display device 24, and inputs operation data for moving within the three-dimensional virtual space or for specifying an object within the three-dimensional virtual space. The computer system 20 changes the contents of the three-dimensional virtual space in accordance with the operation data, and displays it on the display device 24 using a VRML browser.

Preferred Embodiments A preferred embodiment of the present invention will now be described.

As mentioned above, in the past, interaction creation tasks such as adding sensors and routing to object graphic data (VMRL files) were performed manually by the user (client) using a text editor, making it prone to simple errors. Furthermore, the accuracy of the interaction creation results could not be determined until confirmation was made using the VRML browser shown in step 108 of Figure 1. This required launching the VRML browser and checking each time an interaction program was changed, resulting in inefficient and time-consuming work. Embodiments of the present invention address the above-mentioned drawbacks. Specifically, by linking model creation operations with the operation of the interaction creation editor, embodiments of the present invention enable these tasks to be performed in an integrated manner, enabling the efficient and time-consuming creation of 3D virtual space content.

Figure 8 shows the configuration of a content creation software tool 4, which is an embodiment of the content creation software tool 3 illustrated in Figure 3. To perform model creation and interaction creation in an integrated manner, the content creation software tool 4 is composed of a graphical user interface (GUI) 40, an editing tool 42, a scene graph database (SGDB) 44, a work tool 46, a script creation unit 47, and a VRML browser 308.

The editing tools 42 consist of a model editing tool 420, a routing editing tool 422, a scene graph editing tool 424, a text editor 426, and a template creation tool 428.

The work tool 46 consists of a browser emulator 460, a file input/output unit 462, a file scope management unit 464, and a backup/restore unit 466.

The script creation unit 47 is composed of a Java emulator 470, a Java debugger 472, and a Java compiler 474.

The content creation software tool 4 is, for example, stored in the hard disk drive 100 and transmitted via the network system 1, or stored in a network or external storage device 28 (floppy disk 280 or MO disk 282) and input from the external storage device 28 to the computer system 20, where it is installed in the hard disk drive 214 and used. In other words, in this embodiment, an example will be described in which the content creation software tool 4 is implemented in the computer system 20.

The components of the content creation software tool 4 will now be described.

Graphical user interface unit (GUI) 40 The graphical user interface unit (GUI) 40 corresponds to the graphical user interface unit (GUI) 31 in FIG. 3, and displays images used for inputting various data used in creating VRML content for a three-dimensional virtual space in window format on the display device 24 via the PC 20.

FIG. 9 shows an example GUI screen displayed by GUI 40 on display device 24. The GUI screen illustrated in FIG. 9 includes a Conductor window, a 3D Perspective View window, a Parallel View window, a Resource Library window, a Scene Graph window, a World Info window, an Appearance window, a Root window, an Attribute window, a Script Explorer window (not shown), and a Script Editor window.

(1) The Conductor window is used to manage the entire Conductor.

(2) The 3D Perspective View window displays a three-dimensional image. Hereinafter, this will be referred to as the 3D View window.

(3) The Parallel View window is the part that displays the image in parallel projection.

(4) The Resource Library window is where you manage your library.

(5) The Scene Graph window displays the hierarchical tree structure of the world.

(6) The World Info window is where you set the world's attributes.

(7) The Appearance window is where you set the color and texture of an object.

(8) The root window is the part where event routing is set.

(9) The Attribute window is where you set the node attributes and node name.

(10) The Script Expert window is where you create script templates.

(11) The Script Editor window is the part of the text editor where you edit Java files.

Figure 10A is an enlarged view of the Conductor window shown in Figure 9, while Figures 10B and 10C are enlarged views of Figure 10A. The Conductor window manages the entire Conductor environment, allowing you to create, load, save, run, and stop worlds, switch mouse modes, and add and delete objects.

(a) You can create a new world by selecting "New" from the File menu.

(b) To load a world from a file, press the Open button or select "Open" from the File menu.

(c) To save the world to a file, press the Save button or select "Save" from the File menu.

(d) To check the movement of the world, press the "Play button."

(e) Pressing the Pause button during playback will pause playback, and pressing the Pause button again or the Play button will resume playback.

Conductor has a mouse mode, which is illustrated in expanded form in Figure 10B.

(f) Navigate (viewpoint movement) is used to move the viewpoint within the 2D/3D View window.

(g) Move is used to move an object.

(h) Rotate is used to rotate an object.

(i) Scale is used to change the scale of an object.

Conductor also has a Primitives bar, shown enlarged in Figure 10C. To add a primitive object such as a Box or Cone, select the object you want to add on the Primitives bar and click in the 3D View window. The Primitives bar also has a "Sensor" button.

The GUI 40 accepts operation input data entered by the user pressing various buttons in a window displayed on the display device 24 using the mouse 262 as the input device 26, or operation data entered using the keyboard 260, and provides the necessary operation data to each tool in the editing tool 42 and to the scene graph database 44. In this way, the GUI 40 provides a GUI environment to the user.

The GUI 40 receives display output data from the editing tool 42 and the scene graph database 44 and displays the received data in a designated window on the display device 24. Each component of the editing tool 42, scene graph database 44, and work tool 46 is activated in response to operation data input to the GUI 40 and performs processing based on the operation data provided by the GUI 40.

VRML Browser 308 The VRML browser 308 performs final confirmation of the VRML content created in the computer system 20, displays VRML content obtained from the server device 102, and also displays help files linked to the operation of each component of the GUI 40 to the work tools 46. The VRML browser 308 can be, for example, the Community Place (trademark) browser provided by Sony Corporation. An example of the Community Place browser is given below.

Editing Tool 42 The editing tool 42 as a whole provides the user with the functions necessary to create graphic data and interaction programs for objects in a three-dimensional virtual space.

Each part of the editing tool 42 will now be described.

Model Editing Tool 420 The processing functions of the model editing tool 420 are listed below.

(1) The model editing tool 420 uses model creation data entered by the user through operation of the model editing window displayed on the display device 24 to create graphic data indicating attributes such as the size, color (shape), position, and movement of an object.

(2) The model editing tool 420 outputs the created graphic data [object attributes] to the scene graph database 44.

(3) The model editing tool 420 displays an object based on the created graphic data in three dimensions via the GUI 40 at a predetermined position in the model editing window on the display device 24.

(4) The model editing tool 420 can also edit the graphic data read from the hard disk drive 214.

(5) The model editing tool 420 can also edit graphic data read from the floppy disk 280 via the floppy disk drive 216 or from the MO disk 282 via the MO disk drive 218.

(6) Model editing tool 420 can also edit graphical data downloaded to computer system 20 from a network.

The model editing tool 420 having the various functions described above performs the characteristic functions of the present invention described below.

a. Object display functions Rotate (using the "Rotate" operation in the Conductor window), move (using the "Move" operation in the Conductor window), navigate (using the "Navigate" operation in the Conductor window), and scale (using the "Scale" operation in the Conductor window) objects for viewing them from different perspectives. b. Object scaling functions Use the "Scale" operation in the Conductor window.

c. Sensor Node Area Display and Configuration Function Collaboration with Browser Emulator 460 d. Parallel View Function f. Attention Function Routing Editing Tool 422 The routing editing tool 422 performs routing editing, associating named object graphic data and script nodes within the current scope (the VRM file being edited). Note that routing requires matching the field value types of the source and destination nodes, such as SFBool (a Boolean value indicating true or false).

Details of the routing editing process using the routing editing tool 422 will be described later as setting the input data type.

Scene Graph Editing Tool 424 In VRML, nodes can be arranged hierarchically. The scene graph editing tool 424 edits the hierarchical structure of objects and invisible nodes (such as script nodes). The node hierarchical structure is, for example, hierarchically organized as follows: child node (VRML file) F1 representing a leaf; child node (VRML file) F2 representing a branch; child node (VRML file) F3 representing a trunk; child node (VRML file) F4 representing a root; and parent node (VRML file) F5 representing the entire tree.

Text Editor 426 The text editor 426 has editor functions for programming languages suitable for creating scripts, such as Java. It creates script source programs and automatically adds, deletes, and modifies variables in conjunction with editing operations on script nodes.

Template Creation Tool 428 The template creation tool 428 is a tool used for user convenience. It works in conjunction with the text editor 426 and interactively creates a script prototype (template) in response to user input in the "Script Expert window" on the display device 24, outputting it to the text editor 426. The user can easily create scripts by using the template creation tool 428 to make necessary modifications to the source program (script template) already provided by the template creation tool 428 and already completed to a certain extent.

Scene Graph Database (SGDB) 44 The SGDB 44 stores data created by each tool in the editing tools 42 in the RAM 206 of the computer system 20, manages the stored data, and provides the stored data immediately in response to requests from each component of the editing tools 42 and the work tools 46.

The work tools 46 provide the client with functions necessary for creating VRML content, such as checking the created content, checking the operation of scripts, and recording and playing back data to the input device 26. Each of the work tools 46 will be described below.

Browser Emulator 460 The browser emulator 460 emulates the operation of the VRML browser 308 and presents the same VRML content to the user as would be presented using the VRML browser 308. Therefore, the browser emulator 460 is used, for example, when a user wants to check the operation of created VRML content.

The browser emulator 460 is activated in response to pressing the "Play button" displayed in the Conductor window of the display device 24, or in response to pressing the "Play" button assigned to the keyboard 260. The results of emulating the VRML content are stored in the scene graph database 44, and the resulting VRML content is displayed on the screen of the display device 24, for example, in a 3D View window (editing window) shown in FIG. 9, and the display content is further changed in response to user operations. The browser emulator 460 stops operating in response to pressing the "Stop button" displayed in the Conductor window. When the browser emulator 460 stops operating, the GUI 40 displays the original VRML content for editing.

When checking operation using the browser emulator 460, it is desirable to sequentially accumulate and save changes in field values resulting from dynamic objects, and then, upon termination of the browser emulator 460 in response to the "Stop" button, restore the original object display state. This is achieved by having the backup manager 466 (described below) operate simultaneously with the browser emulator 460.

File Input/Output Unit 462 The file input/output unit 462 records graphic data [VRML files (extension .wr1)], scripts (extension .java), texture files (extensions .bmp, .jpg, .gif), and sound files (extensions .wav, .mod) of VRML content stored in the scene graph database 44 to the hard disk drive 214, floppy disk 280, or MO disk 282 of the computer system 20. The file input/output unit 462 also outputs various data of the VRML content read from the hard disk drive 214, etc., to the scene graph database 44.

File Scope Management Unit 464 In VRML, each graphics data file (extension .wr1) is assigned one scope (the range in which the names and routings assigned to nodes are valid), and node names and routing are managed on a scope-by-scope basis. The file scope management unit 464 manages node names in the scene graph database 44, automatically creates node names, and searches for nodes. In addition, when a node references the same graphics data file multiple times, it propagates changes to the graphics data file to all referencing nodes.

Backup Manager 466 Backup manager 466 corresponds to backup manager 36 in FIG. 3.

When the browser emulator 460 is activated by pressing the "Play button" during VRML content confirmation and displays an interactive scene, the node states change in response to user operations, causing the field values of each node to change. Without any corrective action, the original scene cannot be displayed. For this reason, the backup manager 466 receives from the scene graph database 44 and stores the initial state (as field values) of each node's field values for the scene (a three-dimensional virtual space generated from a VRML file) first displayed in the 3D View window (editing window) when the browser emulator 460 is activated by pressing the "Play button" in the Conductor window of the display device 24.

When the browser emulator 460 stops operating in response to pressing the "Stop button" in the Conductor window of the display device 24, it outputs the stored field values of each node to the scene graph database 44 and restores the original display state of the object.

As a result, the GUI 40 displays an image of the original three-dimensional virtual space in the 3D View window (editing window) of the display device 24 based on the initial field values of each node entered in the scene graph database 44.

Script Creation Unit 47 The script creation unit 47 has functions for compiling, verifying the operation, and debugging scripts created by the user using the text editor 426. Each part of the script creation unit 47 will be described below.

Java Compiler 474 The Java compiler 474 compiles script source programs written in Java stored in the scene graph database (SGDB) 44 to create object programs and output them to the SGDB 44. In this embodiment, when the "Play" button in the Conductor window is pressed, the Java compiler 474 automatically compiles script source programs (e.g., files with the extension ".java") and automatically generates object programs (e.g., files with the extension ".class").

Java Emulator 470 and Java Debugger 472 The Java emulator 470 and Java debugger 472 operate as interpreters for programs written in the Java language and are used by users to check and debug the operation of script programs. In other words, the Java emulator 470 emulates the operation of the script object program stored in the scene graph database (SGDB) 44, and the Java debugger 472 outputs the status of the Java emulator 470 during emulation operation and any errors that occur to the SGDB 44.

Characteristic Functions of the Content Creation Software Tool 4 The following describes the characteristic processing details (functions) of the content creation tool 4 of this embodiment.

Operation Check Function and Backup Management Function (Browser Emulator 460, Backup Manager 466) As described with reference to Figures 4 to 6, when the user presses the "Play button" displayed in the Conductor window on the screen of the display device 24 with the mouse 262 (Figure 5, S301; Figure 6, S311), the browser emulator 460 interprets the VRML content created up to that point and displays it on the display device 24. Preferably, as illustrated in Figure 6, the backup manager 466 also operates simultaneously to enable backup. When a dynamic object, etc. is clicked (Figure 6, S223), the backup manager 466 sequentially saves the field values of each node representing the dynamic object (S224). Then, when the "Stop button" is pressed (Figure 6, S225), the mode returns to normal editing mode, and the backup manager 466 restores the field values (Figure 6, S226).

In other words, the backup manager 466 saves the state of the VRML content at the start of the operation check, and when the user presses the "Stop button" displayed in the Conductor window on the screen of the display device 24 with the mouse 262 and the browser emulator 460 stops executing the VRML content, the VRML content's field values are restored to those at the start of the operation check, and the display contents of the window's objects (models) are restored to those at the start of the operation check.

This operation check and backup management process eliminates the need to first save the created VRML content to a hard disk drive device 214 or the like and then launch a VRML browser to check its operation, as was done in the conventional method described with reference to Figure 1. Furthermore, the user can check the operation of the content they have created so far at any time during the VRML content creation process.

Automatic file creation function (Java compiler 474) For example, when a user presses the "Play button" on the Conductor window to start up the browser emulator 460 in order to check the contents of VRML content, the Java compiler 474 can automatically compile the script source program, for example, a file with the extension ".java", and automatically generate an object program, for example, a file with the extension ".class".

Script program creation and debugging function (text editor 426) The user can use the text editor 426 to create a script source program in a programming language suitable for creating scripts, such as Java, and then compile the created source program using the Java compiler 474 to create an object program.

This object program is executed not only when VRML content is run by the VRML browser 308 but also when operation is checked by the browser emulator 460.

Furthermore, by adding debug code to the lease program and running it in a Java emulator 470, the Java debugger 472 displays the input and output values of the script, enabling you to debug the script.

Automatic template creation function (text editor 426): When the user interactively sets the input and output values of a script node, the template creation tool 428 creates a template for the script source program that matches these settings. The user can create a script source program that will realize the desired event by making the necessary changes to the template using the text editor 426. This function saves the user the trouble of creating the script source program entirely in an editor from scratch, and also prevents simple coding mistakes.

Object Display Function (Model Editing Tool 420) The model editing tool 420 allows for normal display and display with a different viewpoint.

FIG. 11 is a diagram showing an example of an object displayed by the model editing tool 420 in the 3D View window on the GUI screen of the display device 24.

The model editing tool 420 displays a 3D perspective view of the object represented by the created graphic data in the 3D Perspective View window on the GUI screen (Figure 9). Hereinafter, this window will be referred to as the 3D View window. In this state, the user can click to select an object in the 3D View window, and then click with the mouse 262 one of the "Rotate," "Move," "Navigate," or "Scale" buttons displayed in the Conductor window of the GUI screen shown in FIG. 10A to change the rotation, movement, or viewpoint movement operation mode. If the user then drags or clicks within the 3D View window while holding down the left button of the mouse 262, the model editing tool 420 will display on the display device 24 an image (object) of the selected object rotated or moved, depending on the mouse mode (rotate, move) and the user's operation on the 3D View window. If the user selects the "Navigate" operation mode, the model editing tool 420 sets the point in the 3D View window where the user clicked as the viewpoint and displays an image of the selected object as seen from that viewpoint. Therefore, the above processing of the model editing tool 420 allows the user to view the object from various viewpoints. In other words, using this function, the user can view the object from various viewpoints.

When observing an object from a different viewpoint, it is preferable to position the object in the center of the window for ease of operation.

Therefore, in this embodiment, the model editing tool 420 automatically moves the target object to the center of the window when changing the viewpoint.

Furthermore, the mouse 262 has an operation mode called a point of interest (POI) mode, as shown in FIG. 12. When the user selects an object (a cone) in the 3D View window by pointing with the mouse 262, as shown in FIG. 13, the model editing tool 420 adjusts the viewpoint to the selected object and displays it in the center of the 3D View window, as shown in FIGS. 11 and 14.

Object Scaling Function (Model Editing Tool 420) In the Conductor window shown in Figure 10A, with the operation mode of the mouse 262 set to "scale," for example, the user can move the cursor while pressing a predetermined button on the mouse 262, or can input an instruction to change the size of the object and data indicating the new size from the keyboard 260, and the model editing tool 420 will change and display the dimensions (size) of the object in accordance with the movement of the cursor. When the user releases the button on the mouse 262, the model editing tool 420 will confirm the size of the object and change the contents of the object's graphic data so that the object of the confirmed size is displayed in the three-dimensional virtual space of the display device 24.

By combining mouse mode changes and mouse 262 operations, the user can, for example, rotate and move an object in the routing editing tool 422, and even zoom in (or out) to display an image with a different viewpoint or perspective in the 3D View window on the display device 24. In other words, this process is also effective when observing an object from different viewpoints.

Furthermore, when the user performs an action to instruct a change to the graphic data, such as releasing the predetermined button on the mouse 262, the model editing tool 420 changes the contents of the object's graphic data to match the object displayed on the display device 24.

Sensor node area display and setting function (model editing tool 420, browser emulator 460) A sensor is provided in the primitive bar illustrated in Figures 10A and 10C to generate an event when the user clicks and points to an object in virtual space displayed in a window on the screen of the display device 24. When the sensor generates an event, a script routed to the sensor is executed, and when the cursor is moved outside the area (bounding box) of the sensor node, the execution of the script is stopped.

The sensor node's area display and setting function is a function that confirms and changes the range of the effective area within a three-dimensional virtual space, such as a touch sensor attached to an object that generates an event in response to operation with a mouse 262 or a sound node that outputs sound in response to operation with a mouse 262 or the like.

The area display and setting process of the sensor node will be described with reference to FIG.

S301: The user clicks on an object in the 3D View window of the display device 24 using the mouse 262.

S302: The model editing tool 420 operates in response to the user's action, selects the clicked object, and blinks the bounding box surrounding the selected object.

S303: The user then clicks on the Sensor tab in the Conductor window on the menu screen and specifies, for example, a touch sensor.

S304: In response to the user's action, the model editing tool 420 adds a touch sensor or the like to the object.

At this initial stage, the bounding box indicating the object selection defines the effective area of the touch sensor.

S305: The user then inputs a command to change the range of the sensor's effective area from the keyboard 260, as well as data indicating the range of the changed effective area, or uses the mouse 262 to point to the range of the changed effective area.

S306: In response to the user's action, the model editing tool 420 changes the effective area of the sensor, etc., and displays the changed effective area of the sensor, etc., with a bounding line. Note that in the example embodiment shown below, the effective area is box-shaped (i.e., a bounding box), but in practicing the present invention, the shape of the bounding line is not limited to a box shape.

The display and scaling functions described above are also applicable to bounding lines (bounding boxes), and the user can use the above operations to have the model editing tool 420 rotate, move, and scale the bounding box. The model editing tool 420 then sets the range defined by the bounding box modified by these operations as the effective area of the modified sensor, etc.

S307: To confirm the changes, the user presses the "Play button" displayed in the Conductor window with the mouse 262.

S308: In response to the user's action, the browser emulator 460 operates, and performs content interpretation and display operations. Preferably, as described above in the "Verification Operation" section, the backup manager 466 also operates simultaneously with the browser emulator 460, enabling the saving and restoration of field values resulting from dynamic objects during the verification of the VRML content by the browser emulator 460.

S309, S310: When the browser emulator 460 is running, for example, if the user moves the cursor of the mouse 262 into the bounding box, the sensor generates an event and a script routed to the sensor is executed. When the cursor is moved out of the bounding box, the execution of the script is stopped.

S311: Execution of VRML content by the browser emulator 460 is stopped when the user presses the "Stop" button displayed in the Conductor window, causing the content creation software tool 4 to return to edit mode.

Parallel View Function (Model Editing Tool 420) Figure 16 is a diagram showing a pop-up menu displayed in the 3D View window of the display device 24. Figure 17 is a diagram showing the Parallel View function.

When the user clicks a specific button (the right mouse button) on the mouse 262 in the 3D View window while the browser emulator 460 is stopped, the model editing tool 420 displays a pop-up menu in the 3D View window, as shown in Fig. 16. When the user selects one of the options from the pop-up menu, the model editing tool 420 displays a two-dimensional side view, top view, or wire frame of the object in the Parallel View window on the menu screen of the display device 24, as shown in Fig. 17.

Attention Function (Model Editing Tool 420) The Attention function is used to check the shape of objects displayed in the 3D View window. It is a function that places and displays each object in a three-dimensional virtual space as viewed from a viewpoint specified by the user in the content creation software tool 4, with one or more objects selected by the user in the 3D View window with the mouse 262 as the center.

The model editing tool 420 arranges and displays one or more objects created in the 3D View window in a three-dimensional virtual space.

The menu screens displayed on the display device 24 are shown as examples in Figures 18 and 19. Figures 20-22 are diagrams of objects displayed in the 3D View window as first to third examples demonstrating the attention function. However, while the objects shown in Figures 18-19 are cones, the objects shown in Figures 20-22 have patterns added to them in addition to the cones.

The attention function will now be described with reference to the flow chart of FIG.

S321: As shown in FIG. 18, the user clicks the "Navigate" button in the Conductor window with the mouse 262 to enter the viewpoint movement (Navigate) mode.

S322: In the 3D View window displaying the cone-shaped object shown in FIG. 18, or the cone-shaped object and the patterned cylindrical object shown in FIG. 20, the user clicks and selects the cone-shaped object with the left button of the mouse 262, as shown in FIG. 18 or 20. This causes the model editing tool 420 to enclose the selected cone-shaped object in a bounding box, indicating that it has been selected.

S323, S324: As shown in Figure 18, the user clicks the right button of the mouse 262 and selects "Attention ON" from the pop-up menu. As a result, the model editing tool 420 changes the background of the viewpoint position display panel to yellow, as shown in Figure 19 or Figure 21, and changes the line of sight so that the selected object is at the center of the 3D View window. However, because the viewpoint position does not change, the distance to the object remains the same.

S325: When the user drags the mouse 262 while holding down the left button around the object, the viewpoint and viewing direction of the object change accordingly, as shown in Figure 22, allowing the user to observe the object from various angles. That is, the model editing tool 420 changes the display contents of the 3D View window to images of conical and cylindrical objects as seen from the viewpoint of the specified location in the 3D virtual space, in accordance with the user's specifications. In this way, by using the attention function, the user can rotate and view the entire scene displayed in the 3D View window in the 3D virtual space, rather than rotating the object itself, making it easier to grasp the overall view of the object.

S326: When the user wishes to end the observation, he or she selects "Attention OFF" from the pop-up menu as shown in FIG. 19. This terminates the attention function of the model editing tool 420.

Routing Edit Function: Setting Input Data Type (Routing Edit Tool 42 2 ) In VRML 2.0, the exchange of events between fields of each node can be defined by the ROUTE statement shown below.

ROUTE NODE1.field1 TO NODE2.field2 In this example, an event is defined to be transmitted to a field named field1 (eventOut) in a node named NODE1 (NodeNane). This ROUTE statement requires that the data type (Data Type) predefined for the event output field (eventOut) must match the data type predefined for the event input field (eventOut).

When the user selects a field name for an event input node, the routing editing function displays a drop-down list in the ComboBox containing only field names that match the pre-defined data type for the field name of the selected event output node. This ensures that only routable field names are presented to the user, preventing the user from entering an incorrect route statement and facilitating the user's routing entry process.

The routing edit function is further described with reference to Figures 24 and 25-27.

FIG. 24 is a flowchart showing the processing of the routing edit function.

25-27 are diagrams of the Route window showing examples of the routing editing functions.

The routing editing process, or in other words, the process of setting the inputtable type, will be described below with reference to FIG. 24. The following process is executed by the routing editing tool 422 in an interactive format with the user.

S331: The routing editing tool 422 determines whether the user has opened the route window and used the mouse to display a pull-down list of the node name (NodeName) or field name (EventOut) on the event output side in the upper row.

S332: The routing editing tool 422 extracts the selectable event output node names (NodeName) or their field names (eventOut) and displays them as a pull list (also called a ComboBox).

S333: The routing editing tool 422 displays, for example, TS1 as the event output node name (NodeName) selected by the user using the mouse to select a menu item from the pull-down list displayed as shown in FIG. 25, and displays, for example, "isActive" as its field name (eventOut). The routing editing tool 422 also displays, for reference, the data type (Data Type) preset for the selected field name, for example, SFBoool (a Boolean value indicating true or false, taking either FALSE (0) or TRUE (1)), in the area immediately to the right of the field name (eventOut).

S334: The routing editing tool 422 determines whether the user has performed a mouse operation to display a pull-down list of the node names (NodeName) on the event input side in the lower row.

S335: As shown in FIG. 26, the routing editing tool 422 displays a list of selectable event input node names (Node Name), such as PL1 and TS1, in a pull-down list.

S336: The node name (Node Name) on the event input side selected by the user through a menu selection operation of the mouse 262 from the pull-down list shown in FIG. 26 is displayed by the routing edit tool 422.

S337: The routing editing tool 422 determines whether the user has performed a mouse operation to display a pull-down list of the field name (eventIn) of the node name (NodeName) on the event input side in the lower row.

S338: The routing editing tool 422 displays a pull-down list of only the selectable event input field names (eventOut), as shown in FIG. 27. In this case, the routing editing tool 422 displays only the field name "on," which matches the pre-defined data type (in this case, SFBoool) for the field name of the node that outputs the event already selected by the user.

S339: The field name (eventOut) of the event input node selected by mouse menu selection from the pull-down list shown in Figure 27 is displayed by the routing editing tool 422, and a ROUTE statement corresponding to the node name and field name that receive the selected event is generated in the routing editing tool 422.

In this way, the routing editing feature displays only the node field names that match the data type of the event being exchanged between node fields. The user can then select one of the displayed field names to set the routing type. This simplifies the process of setting routing data types and prevents errors such as mismatched data types between nodes due to simple mistakes.

To delete a routing, select the routing you want to delete and press the Delete button. The routing edit tool 422 will then delete the corresponding routing.

Script Editing Function (Text Editor 426) When the user changes the input/output (eventIn, eventOut) values of a script node, the text editor 426 automatically changes the source program of the script corresponding to the script node to match the changed input/output values.

File scope function (scene graph editing tool 424) When the user selects a VRML file to be edited in the Conductor window or the like on the menu screen of the display device 24, the scene graph editing tool 424 displays the nodes referenced by the selected VRML file to be edited in the scene graph window, for example in the form of a hierarchical tree. This collection of nodes referenced by the VRML file to be edited is also called the "file scope."

The scene graph editing tool 424 limits the nodes that can be edited, such as for routing and script creation, to the file scope displayed in the scene graph window. When the user changes the VRML file being edited, the contents of the file scope and the nodes that can be edited are changed to the nodes referenced by the changed VRML file.

The script editing function is valid for each node within the same VRML file (within the file scope). When the user changes the input/output (eventIn, eventOut) values of a script node within the same VRML file, the text editor 426 automatically modifies the source program of the script corresponding to the script node to match the changed input/output values (inline management function) in order to maintain consistency between the script nodes within the same VRML file (displayed within the same file scope). Furthermore, since node names must be unique within a VRML file, the text editor 426 automatically renames the copied/pasted nodes so that they are unique within the same VRML file when the same node is copied and pasted within the same VRML file (paste naming function) to avoid duplicate node names.

Basic Method for Creating VRML Contents An example of a method for creating VRML contents using the content creation software tool 4 will now be described.

FIG. 28 is a diagram illustrating a cone-shaped object created by the content creation software tool 4.

As a first example of the creation of simple three-dimensional virtual space content (VRML content) using the content creation software tool 4, we will describe the creation of content (first content) in which a sensor is attached to a cone-shaped object shown in FIG. 28, and the cone becomes brighter or darker (a light is turned on or off) depending on how the sensor is pointed.

This VRML content is created using the steps illustrated in Figure 29. Specifically, S401: Create graphic data (place geometric object nodes {Geometry nodes (Cone)}) S402: Add sensors (place Sensor nodes (TouchSensor)) S403: Add light nodes (place VRML-defined nodes {Common nodes (PointLight))) S404: Name the nodes to be routed S405: Set the route S406: Check operation.

The process will be described in detail below.

S401: Creating graphic data [Placing Geometry nodes (Cones)] The user places objects in a three-dimensional virtual space (world) to construct the whole. Objects that can be placed in the three-dimensional virtual space using the content creation software tool 4 are, for example, basic nodes of VRML 2.0 or those provided in the library window.

The content creation software tool 4 can also read object graphic data created with other modeling software by converting it into a file format compatible with VRML 2.0.

When the user launches the content creation software tool 4, the graphical user interface (GUI) 40 displays the GUI menu screen shown in FIG. 9 on the display device 24. When the user selects the "File/New" item in the Conductor window using the mouse 262 or other device, the model editing tool 420 of the content creation software tool 4 creates a new, empty world.

The user places a cone-shaped object (Cone) in the empty world they created. The user selects "Cone" from the Geometry tab in the Conductor window and clicks on the window for creating graphic data (hereinafter referred to as the 3D View window). The model editing tool 420 of the editing tool 42 creates the graphic data for the object (Cone) and displays the cone shown in Figure 28 in the 3D View window. At this time, the user can also use the attention function of the content creation software tool 4 described above to display in the 3D View window an image of what would appear if the user moved around the object (Cone) in the 3D virtual space, allowing them to confirm the shape of the object (Cone).

S402: Adding a sensor [Placing a Sensor Node (Touch Sensor)] In order to give movement to an object in a three-dimensional virtual space or have it respond to user operations, it is necessary to add a sensor to the object, detect certain conditions regarding the client's operations on the object, and communicate those changes as events to other nodes.

The following describes an example of adding a touch sensor that detects a pointing operation on an object using a mouse 262.

To add a sensor to an object, first select the object and then create a sensor (TouchSensor).

(1) First, when the user clicks on an object (Cone) in the 3D View window, the model editing tool 420 selects the clicked object and flashes the bounding box surrounding the selected object.

(2) If the user then clicks the Sensor tab in the Conductor window, selects the TouchSensor at the far right of the Sensor tab (as shown in Figure 10A), and clicks the 3D View window, the model editing tool 420 adds a touch sensor to the object and adds its data to the object's graphic data. At this stage, as described above, the user can also change the effective range of the TouchSensor using the keyboard 260 or mouse 262.

FIG. 30 shows the scene graph window in the menu screen.

In response to the addition of a touch sensor to an object, the scene graph editing tool 424 changes the display contents of the scene graph window on the menu screen as shown in Figure 30. By referring to the scene graph window shown in Figure 30, the user can confirm that a touch sensor has been added to the object, in this example, a cone.

This example illustrates adding a TouchSensor to a simple object called a cone, but the user can also add a TouchSensor to objects more complex than a cone using similar operations.

S403: Adding a Common Node (PointLight) In VRML 2.0, operations are described in such a way that a sensor (Sensor node) transmits a detected event to other nodes, and the nodes that receive the event change their state.

The following explanation will be given using an example where a common node (PointLight) that turns a light on and off is added as a node that receives an event.

Common node (PointLight) lights are located in the Common tab of the Conductor window. However, if you create a light in the same position as the object as shown in the image, it will not be visible, so you will need to move your viewpoint beforehand.

When the user activates the 3D View window and presses, for example, the down arrow key "↓" on the keyboard 260, the model editing tool 420 displays the object in the 3D View window as seen from a slightly more distant viewpoint. In this state, if the user selects a common node (PointLight), the model editing tool 420 displays the object (Cone) brightly, as shown in Figure 31.

S404: Name the node to be routed. Next, the user performs routing between nodes, such as associating a sensor (TouchSensor) with a common node (PointLight).

Routing refers to connecting nodes together, such as from a sensor to a script, to transmit events between them.

To do this, you must first give the sensor a name (DEF name).

32 and 33 show the process of naming a sensor node using the Attribute window.

The Attribute window is used to change the attributes of a selected object. Adding a name (DEF name) to a node is performed through operations in the Attribute window. Here, we will use the example of a user selecting a sensor (TouchSensor) from the Scenegraph window and assigning it a DEF name (TS1, PL1) in the Attribute window.

As shown in FIG. 32, if the user specifies the location of the "DEF name" in the Attribute window, types "TS1" on the keyboard 260, and presses the return key, and then, as shown in FIG. 33, selects the common node (PointLight) from the scene graph window, types "PL1," and presses the return key, the scene graph editing tool 424 assigns the DEF names TS1 and PL1 to the sensor (TouchSensor) and the common node (PointLight), respectively.

For example, when the user double-clicks the on field of a common node (PointLight) in the Attribute window, the text editor 426 sets the initial state of the light to OFF and adds it to the object's graphic data.

S405: Setting a Route FIG. 34 is a diagram showing an example of a route window used to set routing between nodes.

The user configures routing so that events generated by a sensor (TouchSensor; TS1) are transmitted to a common node (PointLight; PL1). The content creation software tool 4 configures routing using the Route window shown in Figure 34.

In the root window shown in Figure 34, the "NodeName" position in the top row is used to set the output node name, and the "NodeName" position in the bottom row is used to set the input node name. The event is to turn a light on/off when the sensor (TouchSensor) is clicked. Therefore, if the user sets the output "NodeName" to TS1 and selects "isActive" for "eventOut," the type "SFBool" will appear on the right. The "SFBool" display on the right indicates that the type of the event passed by "isActive" is SFBool.

For input settings, the user sets "NodeName" to PL1 and "eventIn" to "on."

In response to the above user settings, the routing editing tool 422 changes the display of the route window on the display device 24 as shown in FIG.

Once the above settings are complete and the user presses the Add button, the routing editing tool 422 associates the sensor (TouchSensor) with the common node (PointLight), performs routing, and adds a route between the nodes.

S406: Operation Check When the user presses the "Play button" displayed on the display device 24, the data is input into the graphical user interface (GUI) 40 of the content creation software tool 4, and the operation of the VRML browser 308 is emulated by the browser emulator 460 of the content creation software tool 4. Therefore, it is possible to check the VRML content at any time during the VRML content creation work without starting the VRML browser 308.

When the user presses the "Play" button displayed on the display device 24, the normal content creation process resumes.

The content verification process is described in detail below.

When the "Play" button (the button with a right-pointing triangle) at the bottom left of the Conductor window is pressed with the mouse 262, the content creation software tool 4 transitions from the VRML content creation mode (creation mode) to the simulation mode (simulation mode), in which the browser emulator 460 emulates the operation of the VRML browser 308 and allows the created content to be viewed.

When the system switches to simulation mode, the backup manager 466 saves the state of each node in the VRML content at that time, as well as the user's viewpoint. The browser emulator 460 then executes the VRML content and displays it on the display device 24. While the browser emulator 460 is executing and displaying the VRML content, if the user presses an object (Cone) displayed in the 3D View window with the mouse 262, the object will be displayed brightly while pressed (light ON), and dimly while not pressed (light OFF).

In this way, in simulation mode, when the user clicks on an object (Cone) with the mouse 262, the sensor (TouchSensor) attached to the object detects the click and generates an event. The generated event is transmitted to the common node (PointLight) via the routing settings, and the common node (PointLight) changes its state, turning the object on. When the click ends, a similar event is generated and the common node (PointLight) turns the object off.

Furthermore, when the user presses the "Stop" button (the button marked with a square) in the Conductor window with the mouse 262, the content creation software tool 4 returns to the normal content creation mode.

When returning to VRML content creation mode, the backup manager 466 restores the state of the VRML content to the initial state saved when simulation mode was entered, and also restores the user's viewpoint to the position at the time simulation mode was entered, and the model editing tool 420 displays the initial state graphic data in the 3D View window.

When saving a created VRML content file, the user specifies a file name using the File/Save As menu on the menu screen, and the file input/output unit 462 records the VRML content file stored in the scene graph database 44 in the external storage device 28 via the hard disk drive 214, or the floppy disk drive 216 and MO disk drive 218. The user can also open and view the recorded VRML content file in the VRML browser 308.

As explained above, when creating and verifying simple content that brightens or darkens a cone-shaped object in response to mouse clicks (262), it is clear that interactive operation using the graphical user interface (GUI) unit 40 allows for the addition of object graphic data, sensors, and routing without the need for programming by entering complex string commands.

Creation of Complex Content As a second specific example of creation of three-dimensional virtual space content (VRML content) using the content creation software tool 4, an example of creating VRML content (second content) that changes the color of an object when the mouse cursor is placed over it will be described.

The VRML content described above was configured to transmit events generated by a sensor (TouchSensor) attached to an object to another node (common node (PointLight)). However, in VRML 2.0, scripts can be inserted between the sensor and other nodes to achieve even more complex movements.

For example, to realize the second content mentioned above using VRML 2.0, the color of the object (Cone) is specified using the Material attribute. This Material attribute has multiple fields, and the object's color can be changed by setting the Material attribute "diffuseColor." In such cases, the Material attribute "diffuseColor" must be set depending on the occurrence of an event. In such cases, the diffuseColor can be set by using a script.

The work of creating the second content follows the steps illustrated in Figure 35. That is, S411: Create graphic data [Place Geometry node (Cone)] S412: Add a sensor [Place Sensor node (TouchSensor)] S413: Name the routing target node S414: Create a script S425: Write a program corresponding to the script (debug code only) S416: Set a route to the script S417: Check operation S418: Write a program corresponding to the script (set color) S419: Set a route to the Material node S420: Check operation

Note that, in the second content creation process, the operations of steps 411 and 412 are the same as the operations of steps 201 and 202 described with reference to FIG. 29, and therefore a description thereof will be omitted.

Each step in creating the second content will be described below.

S413: Assigning names to nodes to be routed In VRML 2.0, in order to perform routing, it is first necessary to assign names. In creating the first content, as described above, names (TS1, PL1) were assigned to the sensor (Touch Sensor) and the common node (PointLight). In creating the second content, it is also necessary to assign names to the Material attributes.

FIG. 36 shows the Appearance window in the menu screen.

In VRML 2.0, the Material attribute is included in the Appearance node, which sets attributes such as color and bitmap data to be attached to an object. In the content creation software tool 4, the Appearance window on the menu screen is used to edit the Appearance (including Material, Texture, etc.) of the graphic data of the object selected in the 3D View window.

To assign a name to the Material attribute of an object, the user first selects the object by clicking it with the mouse 262, then selects the Material tab in the Appearance window shown in FIG. 36, and assigns a name, for example, "CONE 1_MAT."

S414: Creating a Script Node VRML 2.0 has a node called a script node for interfacing with a script program. This script node is included in a VRML file, and makes it possible to write complex operations using scripts written in, for example, Java. However, because script nodes have interface functions, they are closely related to the scripts they interface with, and because they allow multiple inputs and outputs to be defined, they can be difficult for users to understand.

For this reason, the content creation software tool 4 is provided with a function called Script Expert that simplifies the writing of scripts.

The Script Expert feature allows you to automatically generate script program templates by defining the script's inputs and outputs. You can also edit the input and output fields using the Attributes window.

Figures 37 and 38 are examples of dialogs for creating a script. Figure 38 shows the dialog when it pops up.

When the user selects "Script/Expert" with the mouse 262 on the menu screen of the content creation software tool 4, the template creation tool 428 opens the dialog box for creating a script shown in Figures 37 and 38.

In this dialog, the top position "DEF" is used to name the script node used to route the script to the VRML file; for example, the user might enter "SC1" in this position as the name of the script node.

The "ClassName" position under "DEF" in the dialog is used to assign a class name to the Java script. For example, the user might assign the script a temporary name of SC1.

The user then defines the input and output of the script node further down in the dialog. In creating the second content, events generated by the sensor (TouchSensor) will be input to the script, so the user sets the "DataType" of the "eventIn" node to "SFBool," which matches the format used when passing events from the sensor (TouchSensor), and the "field name" to "inBool."

The sensor output is passed to the script that controls the Material color, so the user sets the "DataType" of the "eventOut" to "SFColor" and the "field name" to "outColor".

When the user has completed the above settings required to create a script node, the dialog box will look like the one shown in Figure 37.

Furthermore, when the user presses the OK button at the bottom of the dialog shown in FIG. 37 with the mouse 262, the template creation tool 428 creates a Script node and creates a script template (prototype) corresponding to the Script node.

S415: Writing debug code The content creation software tool 4 also has the function of supporting and executing the writing of scripts in the Java language. That is, the template creation tool 428 generates program templates corresponding to script nodes and outputs them to the text editor 426 to support the user in writing scripts. When using the content creation software tool 4, the user can create a script simply by editing and modifying the templates created by the template creation tool 428 using the text editor 426, thereby significantly reducing the effort required to create a script source program.

Furthermore, the user can use the Java compiler 474 to compile script programs created using the template creation tool 428 and text editor 426. As a result, the user does not need to stop the content creation software tool 4 and start a Java compiler to compile each time a script source program is created.

The above steps create a template for the newly defined script, allowing you to edit the script. However, the template created by the template creation tool 428 only defines the basic input and output, and does not include the actual program that will implement the event. Furthermore, the user can use the script writing support and execution function to edit the template using the text editor 426 and immediately create a script that changes the color of an object. However, before doing so, it is recommended that you first check the debug code to see if the created template actually works.

FIG. 39 shows the editor screen displayed by the text editor 426.

In response to user operations, the text editor 426 displays the template created by the template creation tool 428 in a text editing window on the display device 24, as shown in FIG. 39.

As shown in Figure 39, the output field name defined up to this point is defined as a private variable (private SFColor m_outColor), and the code to initialize this variable is embedded in the initialize() method. The _inBoolCB() method is called when an input event occurs, and the program that operates based on input from the sensor (TouchSensor) is written within this method [_inBooICB()].

For example, if you add code to a template that checks sensor input values, add the following debug code to the _inBooICB() method:

After adding this debug code, when the client clicks the right button and selects "Compile" from the pop-up menu, the Java compiler 474 is started and compiles the template (script source program) to which the debug code has been added, and messages during compilation are displayed at the bottom of the editor.

When the user presses the "Play" button on the display device 24 to check the operation, the Java compiler 474 automatically compiles the created script source program to create an object program, and the browser emulator 460 executes the automatically created object program. However, in this case, if an error occurs during compilation, the browser emulator 460 will not execute the VRML content.

If the compilation is successful, the Java compiler 474 displays the word "FiniShed" on the editor screen. If the compilation is unsuccessful, a compilation error is displayed. If a compilation error is displayed, the user can use the text editor 426 again to check for typos, correct the program (template), and then compile again to remove the error.

During debugging using the Java debugger 472, the data indicated by the debug code is displayed in the root window, allowing the user to see the values of the data input from the sensors when the script is executed.

Figure 40 shows an example of the Script Attribute window used to edit the eventIn and eventOut of a script node. The Script Attribute window shown in Figure 40 is used to edit the eventln.cvcntOut of a script node.

When the user selects a script node and clicks eventln or eventOut in the Attribute window on the menu screen, the Script Attribute window shown in Figure 40 opens.

When you set the "Type" and "Name" in the input fields of the Script Attribute window and press the Add button with the mouse 262, the text editor 426 adds the field to the script and updates the script node in the scene graph database 44.

When the user displays a list of input and output attributes of a script in the Script Attribute window, selects a field, and presses the Delete button with the mouse 262, the text editor 426 erases the field description from the script.

Also, if you want to change the "type" and "name" of a script field, you must first delete the script field and then add a new one.

When a script node is changed by the above operations, the text editor 426 automatically changes the source program of the script to match the changed state.

Here is a concrete example of automatic modification of a source program.

For example, in the Script Attribute window shown in FIG. 40, if the user displays the eventOut side, specifies SFBool on the TypeName side, specifies outColor on the EventName side, and presses the Delete button, the text editor 4 26 deletes the 10th line (private SFColor m outColor ;) will be automatically cleared and the changes will be reflected.

S416: Setting a route to a script node FIG. 41 is a diagram showing an example of the contents of the root window.

As mentioned above, routing is required for scripts to work.

In the second script, an event generated by a sensor (TouchSensor) in the root window shown in Figure 41 is routed to a script node, which changes the color of an object (Cone).

FIG. 42 shows the contents of the Java Console window displayed by the browser emulator 460.

When the mouse cursor 262 passes over an object (Cone), the event generated by the sensor (TouchSensor) is set to "isOver." The script node field that receives the event is set to "inBool" using the Script Expert function. Then, the Java debugger 472 displays a message in the Java Console window, such as the one shown in Figure 43.

S417: In the operation check step 415 (S415), the debug code has been added to the script in the process of writing the debug code. Therefore, when the message shown in Figure 43 is displayed in the Java Console window, the user can check whether the script is operating without error. To further check the operation of the second content, the user need only press the "Play button" on the display device 24, as in the case of checking the operation of the first content.

If it is necessary to further display the script output values, the user may select the "View/Java Console" menu on the menu screen, and the browser emulator 460 will display the Java Console window shown in FIG. 43.

When the user presses the "Play" button on the menu of the display device 24, the browser emulator 460 emulates the operation of the VRML browser 308 and displays the object (image) in the three-dimensional virtual space represented by the VRML content in the 3D View window. Furthermore, when the user moves the cursor over the object in the 3D View window with the mouse 262, the Java debugger 472 displays the message "true" in the Java Console window, as shown in FIG. 41. When the user moves the cursor away from the object, the Java debugger 472 displays the message "false."

The Java Console window display shown in Figure 43 indicates that when the mouse cursor 262 comes over an object, the object's attached touch sensor detects this and generates an event, which is transmitted to the script node, indicating that the script node has received the event. The display in the Java Console window is generated by the execution of the System.out.Println() method.

Similarly, when the mouse 262 cursor is removed from the object, an event is transmitted and the operation result is displayed in the Java Console window.

If you want to debug your script, you can add the debug code to your script as described above to check whether events are being delivered to the script correctly.

S418: Writing a program corresponding to the script Figure 44 is a diagram showing an example of a script to which a code for changing the color of an object has been added.

The color of the object can be changed by using the output field (variable name m outColor) and route it to the Material attribute. To add code to your script that changes the color of an object, add the following code to the method inBoolCB()

By adding these codes, when the mouse 262 cursor enters an object during emulation operation by the browser emulator 460, the ev.getValue() in the code becomes "true" and red is output from the script (SC1), and when the cursor leaves the object, the ev.getValue() in the code becomes "false" and green is output from the script.

S419: Setting a route to a Material node To actually change the color of an object, it is necessary to perform routing from the script node to the Material attribute.

Figure 36 shows the root window. The outColor of the script program (SC1) is set to the Material attribute (CONE1 This figure shows the display content when routing to the diffuseColor of MAT.

The user changes the outColor of the script node (SC1) in the root window to CONE1 When routing to MAT's diffuseColor, in conjunction with the routing set up so far, the event is propagated from the sensor (TouchSensor: TS1) to the script (SC1), and then from that script node to the Material attribute (CONE1 The event flow is completed by the event being propagated to MA T).

After completing the above steps, the user presses the "Play" button in the Conductor window and moves the mouse 262 cursor over the object (Cone). The object turns red; when the cursor is moved away from the object, the object turns green.

As with the first content operation check, the backup manager 466 retains the initial state of the content and the user's viewpoint at the start of the operation check. When the user presses the "Stop button" and the browser emulator 460 terminates operation, the model editing tool 420 restores the initial state of the VRML content retained in the backup manager 466 to the state seen from the user's viewpoint at the start of the operation check and displays it in the 3D View window.

For example, if the initial display content of the VRML content at the start of the operation check is as shown in FIG. 28 and the display content of the content at the end of the operation check is as shown in FIG. 31, the model editing tool 420 will return the display of the object (Cone) in the 3D View window to the content shown in FIG. 28 based on the initial state held by the backup manager 466.

The content operations in the operation check described here are as follows.

When the cursor moves over an object, the object's attached sensor (TouchSensor) detects it and generates an event. The generated event is transmitted to the script node via routing, which then executes the method. When the method receives an input event (true), it sets the output field to red. The color written in the output field is then set to the object's (Cone) Material attribute via routing, causing the object's color in the 3D virtual space to turn red. Similarly, when the cursor leaves the object, the sensor (TouchSensor) transmits an event (false) to the script node, which then sets the output field to green, causing the object to turn green.

Example of Clicking an Object (Cone) to Play a Sound As a third specific example of creating three-dimensional virtual space content (VRML content) using the content creation software tool 4, an example of creating VRML content (third content) that plays a sound when an object (Cone) is clicked with the mouse 262 will be described.

The third content creation process will now be described.

In VRML 2.0, sound can be output using sound nodes, and the content creation software tool 4 has the ability to add sound nodes to a world by dragging and dropping them from the sound library.

The process for creating the third content involves the following steps, as illustrated in Figure 45:

S431: Create the shape data for the object (Cone) [Place a Geometry node (Cone)] S432: Add a sensor [Place a Sensor node (TouchSensor)] S433: Place a Sound node S434: Check operation S435: Configure and route an AudioClip node S436: Check operation The operations in steps 431 and 432 are the same as those described above for creating the first and second content, so a detailed explanation is omitted. In this example, the sensor (TouchSensor) is named TS1. Next, we'll check the default operation of the Sound node, then change its attributes and route it, and confirm that clicking the object produces a sound.

S433: Sound Node Arrangement Figure 46 shows the scene graph window and Attribute window when arranging sound nodes.

In VRML, sound output requires the placement of a sound node. The content creation software tool 4 is configured so that the user can add a sound node by clicking the first Sound tab in the Resource Library window shown in FIG. 9 with the mouse 262 to open the sound library and then dropping a sound node from the sound library.

First, the user looks at the 3D View window to make sure that nothing is selected. If any objects are selected, the user selects "Unselect" from the pop-up menu in the scene graph window shown in FIG. 46 to instruct the model editing tool 420 to cancel the selection.

Furthermore, if the user ensures that the object (Cone) is visible in the 3D View window, selects "Classic" from the sound library in the Resource Library window, and drops it into the 3D View window, the model editing tool 420 adds a sound node to the object's graphic data.

When the user clicks on the tree displayed in the scene graph window, the scene graph editing tool 424 displays the content shown in FIG. 47, indicating to the client that a sound node has been added.

In a sound node, you can specify the sound's area using fields such as "maxBack" and "maxFront." By default, when a sound node is dropped from the library, maxBack=maxFront=10 is set, so that sound is emitted when the mouse cursor 262 enters the area.

S434: Operation check The user can check the sound node by pressing the "Play button" on the menu. In the content creation software tool 4, the cursor of the mouse 262 is set to be already within the sound area immediately after the sound node is dropped, so when the user presses the "Play button", the set sound (classical music in this example) is output.

Additionally, in the content creation software tool 4, the spatialize field of the sound node is set to "TRUE" by default, so when you navigate (use the mouse 262) in the 3D View window within the 3D virtual space, the volume and left/right panning of the sound changes depending on the position of the mouse 262 cursor.

Next, if the user presses the "Stop" button on the display device 24 to return to the creation mode and selects "Sound" in the scene graph window, the model editing tool 420 will flash a bounding box around the object (Cone) shown in the 3D View window on the left and the Parallel View window on the right, as shown in Figure 47, indicating the area where the sensor (TouchSensor) will generate an event that will output a sound, allowing the user to visually confirm the sound area.

Furthermore, when the user selects "Parallel View/Tip View" from the pop-up menu in the 3D View window, the model editing tool 420 displays a three-dimensional image of the object (cone) from the front in the 3D View window on the left side of Figure 47, and a two-dimensional image of the object (cone) viewed from above in the Parallel View window on the right side.

If the user moves the viewpoint to view the entire object and bounding box in the Parallel View window shown in FIG. 48, they can press the shift key on the keyboard 260 and the left button (not shown) of the mouse 262 and drag the Parallel View window downward. The model editing tool 420 will then display an image of the object in the Parallel View window as if the viewpoint were moved away.

When the user presses the Play button and then moves the mouse 262 cursor within the 3D View window, a sound is output when the cursor enters the area indicated by the bounding box shown in Figure 46, and the sound stops when the cursor leaves this area.

Figure 48 shows an example of changing the size of the sound output area shown in Figure 47.

In the content creation software tool 4, the bounding box area can be specified numerically in the Attribute window, or by switching mouse mode on the menu screen shown in Figure 9, this area can be moved, rotated, and scaled using the mouse, as shown in Figure 47.

S435: Setting and routing the AudioClip node With the sound node added by the above steps, sound is set to be automatically output when the cursor of the mouse 262 enters the sound area indicated by the bounding box in Figures 34 and 35. This is related to the settings of the AudioClip node attached to the sound node: startTime=0, stopTime=0, loop=TRUE.

In VRML 2.0, the startTime of an AudioClip node represents the start time, and audio is output when startTime > stopTime. You can also set loop=TRUE to output audio repeatedly. Also, in Figures 47 and 48, to silence audio until you click the bounding box with the mouse 262, set startTime=-1. To stop audio output when you click the bounding box, assign the time of the click to StartTime.

FIG. 49 is a diagram illustrating an example of AudioClip node changes and routing from a sensor (TouchSensor) to an AudioClip node.

For example, to set up a setting that stops sound output when the area defined by the bounding box is clicked, the user must select the first AudioClip tab in the ResourceLibrary window, name the AudioClip node AC1, and then route the touchTime of the sensor (TouchSenSor; TS1) in the root window to the startTime of the AudioClip node, as shown in Figure 48.

S436: Checking Operation When the user presses the Play button with the mouse 262 and clicks on the object (Cone) displayed in the 3D View window, the browser emulator 460 starts outputting sound.

The operation of the third content is as follows.

When the user clicks on an object (Cone) in the 3D View window with the mouse 262, the object's attached sensor (TouchSensor) generates a touchTime event. This event passes the click time (in VRML 2.0, this is relative time from 00:00:00 GMT Jan 1 1970) to the AudioClip's startTime, which sets the startTime and starts sound output. In this example, the AudioClip node's loop field is set to TRUE, so the sound continues to play and output repeatedly.

In this state, sound output cannot be stopped unless the user moves out of the sound area. Therefore, to stop sound output, the client must modify the program using a text editor 426 or similar to stop sound output under certain conditions.

In the embodiment, we have explained an example in which graphic data for a cone-shaped object is created, a touch sensor is attached to the graphic data, and a common node (light), color change, or sound is output. However, it goes without saying that the content creation software tool 4 of this embodiment is not limited to this example and can create VRML content using all nodes supported by VRML 2.0.

Furthermore, the content creation software tool 4 can be adapted to support languages for describing three-dimensional virtual spaces other than VRML through appropriate modifications.

According to the present invention, the attention function allows the user to easily view the desired object and observe the object from any viewpoint. The attention function of the present invention has good interaction efficiency and is easy to use.

According to the present invention, the following effects can be obtained.

The graphic data generation device, graphic data generation method, and media according to the present invention enable the integrated creation of graphic data representing the shape of an object in a virtual space and its position in three-dimensional space, the programming of events (scripts) within the virtual space, and the mapping (routing) of pointing to a model and the activation of a script.

Furthermore, the graphic data generation device and the medium therefor according to the present invention allow the results of each operation, such as modeling, scripting, and routing, to be immediately confirmed.

Furthermore, the graphic data generating device and the medium therefor according to the present invention facilitate the creation of software that allows interactive manipulation of three-dimensional virtual space.

Furthermore, the graphic data generation device, graphic data generation method, and medium thereof according to the present invention allow the shape of a three-dimensional object displayed in a virtual space to be accurately grasped on a two-dimensional screen display.

Furthermore, the graphic data generation device, graphic data generation method, and media thereof according to the present invention allow for easy visual setting of the effective area of a sensor that generates an event in response to an operation on an object, and confirmation of the set effective area of the sensor. Furthermore, it is easy to confirm the operation of events generated in response to sensor operations.

INDUSTRIAL APPLICABILITY The graphic data generation device, graphic data generation method, and media of the present invention can be widely used as an authoring tool for content written in a 3D graphics description language to represent objects in a 3D virtual space.

───────────────────────────────────────────────────── (Note) This publication is based on the publication published internationally by the International Bureau of Patents (WIPO). The effect of the international publication of the Japanese patent application (Japanese utility model registration application) related to this publication arises pursuant to Article 184-10, Paragraph 1 of the Patent Act (Article 48-13, Paragraph 2 of the Utility Model Act) and is unrelated to this publication.

Claims (9)

[Claims] 1. A graphics data generation device comprising: means (31, 40) for displaying three-dimensional objects within an editing window; instruction means for issuing operation commands for the objects displayed by the display means; and attention processing means (420), wherein the attention processing means enters an attention mode in response to a first predetermined operation command, selects an object selected by the instruction means, moves the selected object to the center of the editing window, and displays it, allowing the selected object to be viewed from any viewpoint. 2. The graphics data generating device according to claim 1, wherein the attention means terminates operation in response to a second predetermined operation command. 3. The graphics data generating device according to claim 1 or 2, wherein the attention processing means is executed by editing means that creates content. 4. The graphics data generating device according to any one of claims 1 to 3, wherein the objects are arranged using VRML, which is a three-dimensional graphics description language. 5. A graphics data generation method for creating content in a three-dimensional virtual space interactively with a display means that displays three-dimensional objects in an editing window, the method switching to attention mode in response to a first predetermined operation command, selecting an object according to the selection, moving the selected object to the center of the editing window and displaying it, and allowing the selected object to be viewed from any viewpoint. 6. The method for generating graphics data according to claim 5, further comprising terminating the attention mode in response to a second predetermined operation command. 7. A medium carrying a program for creating content in a three-dimensional virtual space interactively with a display means that displays three-dimensional objects in an editing window, the medium containing the program switching to attention mode in response to a first predetermined operation command, selecting an object according to the selection, moving the selected object to the center of the editing window and displaying it, and allowing the selected object to be observed from any viewpoint. 8. The medium storing the program according to claim 7, wherein the program is executed on a computer system. 9. The medium according to claim 7, wherein the program is transmitted via a network including a server device.