Results 1 to 40 of 119

Thread: Planet: Invasion

Hybrid View

  1. #1
    Frenzied Member Devion's Avatar
    Join Date
    Sep 2000
    Location
    The Netherlands
    Posts
    1,049

    Re: Planet Invasion

    Might as well start making a milestone checklist.. 2 actually.. one tech, one content. And use K.I.S (Keep it simple)

    Ex.:
    Tech:
    - Render fully textured room with reflections
    - Fully textured room with shadow casting
    - Room with bouncing ball (Physics)
    - Positional Sound
    - Sound reverb
    - EAX Support

    Content:
    - Story
    - Storyboard split in 'acts'
    - Game script (story wise) per 'scene'

    etc.

  2. #2
    Frenzied Member Devion's Avatar
    Join Date
    Sep 2000
    Location
    The Netherlands
    Posts
    1,049

    Re: Planet Invasion

    This is going to be a *****-post with some pointers. Thou are warned :]

    Looking at that test.rar there are few things that bothered me a bit, mostly code layout and type declaration. I know this is a test so I'll ignore the type dims but..

    VB Code:
    1. Public Function Initialise() As Boolean
    2. On Error GoTo ErrHandler:
    3.  
    4. Dim DispMode As D3DDISPLAYMODE '//Describes our Display Mode
    5. Dim D3DWindow As D3DPRESENT_PARAMETERS '//Describes our Viewport
    6.  
    7. Set Dx = New DirectX8  '//Create our Master Object
    8. Set D3D = Dx.Direct3DCreate() '//Make our Master Object create the Direct3D Interface
    9.  
    10. D3D.GetAdapterDisplayMode D3DADAPTER_DEFAULT, DispMode '//Retrieve the current display Mode

    Looks a lot better when
    VB Code:
    1. Public Function fbInitD3D() As Boolean
    2. On Error GoTo ErrHandler
    3.          
    4.       'Describes our Display Mode and Port.
    5.       Dim DispMode As D3DDISPLAYMODE
    6.       Dim D3DWindow As D3DPRESENT_PARAMETERS
    7.  
    8.       'Create our Master Object and D3D Interface.
    9.  
    10.       Set Dx = New DirectX8
    11.       Set D3D = Dx.Direct3DCreate()
    12.  
    13.       D3D.GetAdapterDisplayMode D3DADAPTER_DEFAULT, DispMode

    Which gets me to a few pointers:
    - We need to set a certain rulebase regarding type definitions, function naming, etc.
    - Layout.. use tabs.. use a LOT of tabs if necessary.. having everything splattered against the left makes code look chaotic.
    - Commenting.. Each module/form should have a top comment saying basically who edited it last, what was edited and when. (WWW) - Also place comments above code .. not behind it as it might be obscured by the width of the code window.
    - Option Explicit.... needs no explanation.. if someone is wondering why option explicit I'm going to pull out an IRC trout and slap 'm
    - No Variants without damn good reasons.. The most common mistake:
    VB Code:
    1. Dim A, B as string.
    ^ A is a variant...
    - For I/O matters... no Open "x" for input as #1 or #2.. or #5.. use Freefile.

    My 2 million cents ;]

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width